report:prm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
report:prm [2026/04/12 20:59] – [Project Plan] epsatisepreport:prm [2026/04/21 14:13] (current) – [Cost] team6
Line 37: Line 37:
 ==== Cost ==== ==== Cost ====
  
-We need to clearly separate two different prices: the price of the final product and the budget we have right now. While the final Healing Cocoon will be sold to clinics for about 2000€ to 2500€, our goal right now is just to build a working test model (prototype) to prove our technology works.+We need to clearly separate two different prices: the price of the final product and the budget we have right now. While the final Healing Cocoon will be sold to clinics for about 2000 € to 2500 €, our goal right now is just to build a working test model (prototype) to prove our technology works.
  
-For this first prototype, the EPS program gave us a 100€ budget limit. To make sure we don't spend too much, we are using affordable, easy-to-find materials for the physical frame. For the smart system, we are using low-cost electronic sensors and a basic microcontroller (ESP32).+For this first prototype, the EPS program gave us a 100 € budget limit. To make sure we don't spend too much, we are using affordable, easy-to-find materials for the physical frame. For the smart system, we are using low-cost electronic sensors and a basic microcontroller (ESP32).
  
 <table bill> <table bill>
 <caption>Planned vs. Actual Costs</caption> <caption>Planned vs. Actual Costs</caption>
-^ Required component ^ Description ^ Total Budget (€) ^ Actual Costs (€) ^ +^ Required component ^ Description ^  Total Budget (€) ^  Actual Costs (€) ^ 
-| Smart brain & sensors | ESP32 board, and sensors for light, carbon dioxide and humidity | 25.00 | 23.67 |  +| Smart brain & sensors | ESP32 board, and sensors for light, carbon dioxide and humidity |  25.00 |  3.67 |  
-| Output devices | Scent sprayer, speaker amplifier, and relay switch | 25.00 | 22.98 |  +| Output devices | Scent sprayer, speaker amplifier, and relay switch |  25.00 |  22.98 |  
-| Power supply | 5 V 2 A USB wall plug | 25.00 | 7.26|  +| Power supply | 5 V 2 A USB wall plug |  25.00 |  7.26 |  
-| Building materials | Fiberglass rods, hula hoop, spandex, acoustic foam, PVC | 40.00 | 0.00 (Pending purchase) |  +| Building materials | Fiberglass rods, hula hoop, spandex, acoustic foam, PVC |  40.00 |  (Pending purchase) 0.00 |  
-| Total prototype budget |  | 100.00 | 53.91 | +| Total prototype budget |  |  100.00 |  53.91 | 
 </table> </table>
  
Line 72: Line 72:
   - Hanna Kaczmarek (Industrial Biotechnology): Focuses on ergonomic dimensions, market analysis, and the business SWOT analysis.   - Hanna Kaczmarek (Industrial Biotechnology): Focuses on ergonomic dimensions, market analysis, and the business SWOT analysis.
   - Anouc Goedhart (Industrial Design Engineering): Leads the 3D design models, branding (flyers/leaflets), and the visual identity of the Cocoon.   - Anouc Goedhart (Industrial Design Engineering): Leads the 3D design models, branding (flyers/leaflets), and the visual identity of the Cocoon.
-  - Daniel Aagaard Pérez (Informatics Engineering): Develops the software app, the user interface (UI), and the detailed technical schematics.+  - Daniel Aagaard Pérez (Informatics Engineering): Handles the smart system hardware, projector integration, and the detailed technical schematics.
   - Julie Bonnet (Packaging Engineering): Manages material selection, eco-efficiency research, and building the physical cardboard scale model.   - Julie Bonnet (Packaging Engineering): Manages material selection, eco-efficiency research, and building the physical cardboard scale model.
-  - Kemal Yilmaz (Electronics - ICT): Handles the smart system hardware, projector integration, and database management.+  - Kemal Yilmaz (Electronics - ICT): Develops the software app, the user interface (UI), and database management.
  
 **Key External Stakeholders** **Key External Stakeholders**
Line 98: Line 98:
  
 **__1. Description of the project schedule and its key phases using a Gantt chart__** **__1. Description of the project schedule and its key phases using a Gantt chart__**
 +/*
 //<color #c3c3c3>Document the project schedule, and the key project phases, using a Gantt Chart. Highlight the key project phases and milestones</color>.//  //<color #c3c3c3>Document the project schedule, and the key project phases, using a Gantt Chart. Highlight the key project phases and milestones</color>.// 
 +*/
  
 We decided to organize the tasks according to whether they belong to: We decided to organize the tasks according to whether they belong to:
Line 108: Line 109:
  
  
 +<WRAP centeralign>
 <figure fig:ganttv1.1> <figure fig:ganttv1.1>
-{{ :report:initiation_phase_gantt_before_update_v1.png |}}+{{ :report:initiation_phase_gantt_before_update_v1.png?direct&1100 |}}
 <caption>Tasks from the project initiation phase</caption> <caption>Tasks from the project initiation phase</caption>
 </figure> </figure>
 +</WRAP>
        
 +<WRAP centeralign>
 <figure fig:ganttv1.2> <figure fig:ganttv1.2>
-{{ :report:development_phase_gantt_before_update_v1.png |}}+{{ :report:development_phase_gantt_before_update_v1.png?direct&1100 |}}
 <caption>Tasks from the development phase</caption> <caption>Tasks from the development phase</caption>
 </figure> </figure>
 +</WRAP>
  
 +
 +<WRAP centeralign>
 <figure fig:ganttv1.3> <figure fig:ganttv1.3>
-{{ :report:wiki_and_deliverables_gantt_before_update_v1.png |}}+{{ :report:wiki_and_deliverables_gantt_before_update_v1.png?direct&1100 |}}
 <caption>Deliverables and Tasks related to the Wiki</caption> <caption>Deliverables and Tasks related to the Wiki</caption>
 </figure> </figure>
 +</WRAP>
 +
  
 We divided the tasks according to our strengths and areas of expertise, but some compromises had to be made to meet the needs of the project's progress. For example, marketing tasks are primarily managed by Hanna and Ronja, even though their fields of study are unrelated to this topic. We divided the tasks according to our strengths and areas of expertise, but some compromises had to be made to meet the needs of the project's progress. For example, marketing tasks are primarily managed by Hanna and Ronja, even though their fields of study are unrelated to this topic.
  
 Figure {{ref>fig:ganttv2}} presents the updated Gantt Chart. Figure {{ref>fig:ganttv2}} presents the updated Gantt Chart.
- 
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:ganttv2> <figure fig:ganttv2>
-{{ :report:healing_cocoon_gantt_chart_updated_v2_.pdf |}} +{{:report:healing_cocoon_gantt_chart_updated_v2_-1.png |}} 
-<caption><color #ed1c24>Add caption</color></caption>+<caption>Updated Gantt Chart</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 145: Line 152:
 </figure> </figure>
 </WRAP> </WRAP>
-\\+
  
 **__2. Sprint backlog and sprints created in Planner on Jira:__**\\ **__2. Sprint backlog and sprints created in Planner on Jira:__**\\
 +
 +/*
 //<color #c3c3c3>Describe how your plan was mapped to multiple iterative sprints.</color>//  //<color #c3c3c3>Describe how your plan was mapped to multiple iterative sprints.</color>// 
 //<color #c3c3c3>Document how the sprint backlog was planned and managed for each of the sprints you have created in Planner.</color>//  //<color #c3c3c3>Document how the sprint backlog was planned and managed for each of the sprints you have created in Planner.</color>// 
 +*/
  
-First of all, discovering and using Jira was not easy. Despite the explanations that we thought we understood, some parameters and steps were not completed sucessfully on time, notably the timely launch of certain sprints.+First of all, discovering and using Jira was not easy for our team. Despite the explanations that we thought we understood, some parameters and steps were not completed successfully on time, notably the timely launch of certain sprints. 
 + 
 +Figure {{ref>fig:Sprint2}} is one of the first sprint we organized (but forgot to launch it on time).
  
-Figure {{ref>fig:Sprint2}} is one of the first sprint we organized (but forgot to launch it on time).\\ 
 Figure {{ref>fig:Sprint3}} is the last sprint we launched, which takes place from April 7th to 14th.  Figure {{ref>fig:Sprint3}} is the last sprint we launched, which takes place from April 7th to 14th. 
-\\+
  
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:Sprint2> <figure fig:Sprint2>
-{{ :report:screen_shot_scrum_sprint_2_jira.png |}}+{{ :report:screen_shot_scrum_sprint_2_jira.png?direct&1100 |}}
 <caption>Scrum Sprint 2</caption> <caption>Scrum Sprint 2</caption>
 </figure> </figure>
 </WRAP> </WRAP>
-\\+
  
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:Sprint3> <figure fig:Sprint3>
-{{ :report:scrum_sprint3_7to14_april.png |}}+{{ :report:scrum_sprint3_7to14_april.png?direct&1100 |}}
 <caption>Scrum Sprint 3</caption> <caption>Scrum Sprint 3</caption>
 </figure> </figure>
 </WRAP> </WRAP>
-\\+
  
 Figure {{ref>fig:LastBacklog}} is the curent backlog (edited on April 9th) with tasks that still need to be completed. Figure {{ref>fig:LastBacklog}} is the curent backlog (edited on April 9th) with tasks that still need to be completed.
Line 177: Line 188:
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:LastBacklog> <figure fig:LastBacklog>
-{{ :report:last_backlog_april_9th.png |}}+{{ :report:last_backlog_april_9th.png?direct&1100 |}}
 <caption>Last backlog edited on April 9th</caption> <caption>Last backlog edited on April 9th</caption>
 </figure> </figure>
 </WRAP> </WRAP>
-\\ 
  
 Finally, {{ref>fig:PlannerJira}} is the Jira planner in which we created the Epics, Stories, and corresponding tasks. Finally, {{ref>fig:PlannerJira}} is the Jira planner in which we created the Epics, Stories, and corresponding tasks.
Line 187: Line 197:
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:PlannerJira> <figure fig:PlannerJira>
-{{ :report:jira_planner_epics_stories_sprints.png |}}+{{ :report:jira_planner_epics_stories_sprints.png?direct&1100 |}}
 <caption>Jira Planner</caption> <caption>Jira Planner</caption>
 </figure> </figure>
 </WRAP> </WRAP>
-\\ 
  
-**__3. Prioritization, estimation process and underlying challenges__**\\+**__3. Prioritization, estimation process and underlying challenges__** 
 +/*
 //<color #c3c3c3>Describe how prioritization was done.</color>// //<color #c3c3c3>Describe how prioritization was done.</color>//
 //<color #c3c3c3>Document how the estimation process was implemented, and any underlying challenges.</color>// //<color #c3c3c3>Document how the estimation process was implemented, and any underlying challenges.</color>//
-\\ We tried to prioritize tasks based on the deadlines and deliverables to respect, but it was also based on our estimated workload and the time it would take. \\+*/ 
 + 
 +We tried to prioritize tasks based on the deadlines and deliverables to respect, but it was also based on our estimated workload and the time it would take. \\
  
 The tricky part was finding compromises based on each person's areas of expertise and the time the tasks could take. The tricky part was finding compromises based on each person's areas of expertise and the time the tasks could take.
- 
- 
- 
  
  
  • report/prm.1776023951.txt.gz
  • Last modified: 2026/04/12 20:59
  • by epsatisep