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/06/11 11:42] – [Sprint 1: Foundation & Research] team3report:prm [2026/06/13 19:27] (current) – [Sprint Outcomes] team3
Line 651: Line 651:
  
  
-=== Sprint 2 Cor Development and Reporting ===+=== Sprint 2: Core Development and Reporting ===
  
  
 Period: Thursday, March 12th – Wednesday, March 19th, 2026 Period: Thursday, March 12th – Wednesday, March 19th, 2026
- +Sprint 2 {{ref>fig:sprint2}} followed a Thursday-to-Wednesday cycle. This schedule proved challenging due to a school trip on Friday followed immediately by the weekend, which created an unavoidable "stagnation period" at the very start of the sprint where no points could be burned down. 
-Sprint 2 {{ref>fig:sprint2}} followed a Thursday-to-Wednesday cycle. This schedule proved challenging this week due to a school trip on Friday, followed immediately by the weekend. This resulted in an unavoidable "stagnation period" at the very start of the sprint where no points could be burned down. +The story point total rose to 50 this sprint. This was because we had now chosen our topic and needed to research how and what exactly we wanted to apply, and how we wanted to execute it. 
- +Toward the end of the sprint the chart rises again. This was caused by a misunderstanding about how to close a story when not all of its sub-stories were finished.
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:sprint2> <figure fig:sprint2>
 {{ :report:sprint2taskstraqua.png |}} {{ :report:sprint2taskstraqua.png |}}
-<caption>Sprint 2 ...</caption>+<caption>Sprint 2 topic choosen burndown chart</caption>
 </figure> </figure>
 </WRAP> </WRAP>
- 
- 
- 
 === Sprint 3 Strategic Completiong & Prototyping === === Sprint 3 Strategic Completiong & Prototyping ===
 Period: March 19th, 2026 – March 26th, 2026 Period: March 19th, 2026 – March 26th, 2026
Line 677: Line 673:
 Technical Learning Point Technical Learning Point
 The team identified a discrepancy in how Story points are calculated when sub-tasks remain open. Moving forward, the Definition of Done (DoD) has been updated to ensure all granular tasks are closed before the parent Story is moved to "Done" to maintain burndown accuracy. The team identified a discrepancy in how Story points are calculated when sub-tasks remain open. Moving forward, the Definition of Done (DoD) has been updated to ensure all granular tasks are closed before the parent Story is moved to "Done" to maintain burndown accuracy.
 +
 +Story points went up to 58.5. The team started to incorporate daily meetings each meeting gets 0.5 story points. Also we were able to increase the workload because we had less classes. Our objective is to work more in the beginning and less at the end. Start with full power and then be more relaxed at the end. 
 +This sprint also had a lot of story points, as there were a lot of deliverables to be handed in. 
  
  
Line 682: Line 681:
 <figure fig:sprint3> <figure fig:sprint3>
 {{ :report:sprint_3.png |}} {{ :report:sprint_3.png |}}
-<caption> Sprint 3 chart</caption>+<caption> Sprint 3 first deliverables</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 695: Line 694:
  
 Sprint 4 {{ref>fig:sprint4}} was the final push toward a major project milestone. The team's efforts were almost entirely dedicated to consolidating research and development into the Interim Presentation and finalizing the core technical chapters of the report. This sprint confirmed the total unviability of the "Thursday-start" schedule, as the pressure to deliver high-point items was concentrated entirely into the final two days of the cycle. Sprint 4 {{ref>fig:sprint4}} was the final push toward a major project milestone. The team's efforts were almost entirely dedicated to consolidating research and development into the Interim Presentation and finalizing the core technical chapters of the report. This sprint confirmed the total unviability of the "Thursday-start" schedule, as the pressure to deliver high-point items was concentrated entirely into the final two days of the cycle.
 +
 +Story point stats consistent with 53.5. Nothing major to add here. One thing to point out is that each sprint task gets finished up "later" because we start sprints on Thursday, meaning we have a straight-away weekend on our hands, followed by 3 working days. 
  
 <WRAP centeralign> <WRAP centeralign>
Line 706: Line 707:
 === Sprint 5: Interim Report Hand-in and Presentation Prep === === Sprint 5: Interim Report Hand-in and Presentation Prep ===
 Period: **April 1st, 2026 – April 13th, 2026** Period: **April 1st, 2026 – April 13th, 2026**
- 
 Sprint Goal: Hand in the Interim Report. Sprint Goal: Hand in the Interim Report.
- 
 Sprint 5 {{ref>fig:sprint5}} was originally scheduled to end earlier, but the team extended it by two days for two reasons: a vacation period fell near the original end date, and the new end date was aligned with the scheduled meeting with the teachers, giving the team additional time to prepare for the Interim Report presentation. The sprint started with a commitment of 32 story points, which grew to 33.5 after TRAQ-164 ("Table of power budget", 1.5 pts) was added to scope on the first day. The team closed out 21.5 points across 7 work items, including the report hand-in itself (TRAQ-155), the Interim Report (TRAQ-20, 10 pts), Schematics Version 3, the Website, the Application Prototype, and Retrospective 5. TRAQ-88 ("Chapter Project Management", 12 pts) remained in progress and carried over to Sprint 6. The burndown tracked below the ideal guideline through most of the sprint, with the steepest drop between April 8–10 as the interim report deliverables were finalized. Sprint 5 {{ref>fig:sprint5}} was originally scheduled to end earlier, but the team extended it by two days for two reasons: a vacation period fell near the original end date, and the new end date was aligned with the scheduled meeting with the teachers, giving the team additional time to prepare for the Interim Report presentation. The sprint started with a commitment of 32 story points, which grew to 33.5 after TRAQ-164 ("Table of power budget", 1.5 pts) was added to scope on the first day. The team closed out 21.5 points across 7 work items, including the report hand-in itself (TRAQ-155), the Interim Report (TRAQ-20, 10 pts), Schematics Version 3, the Website, the Application Prototype, and Retrospective 5. TRAQ-88 ("Chapter Project Management", 12 pts) remained in progress and carried over to Sprint 6. The burndown tracked below the ideal guideline through most of the sprint, with the steepest drop between April 8–10 as the interim report deliverables were finalized.
 +
 +
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:sprint5> <figure fig:sprint5>
Line 716: Line 717:
 </figure> </figure>
 </WRAP> </WRAP>
- 
 === Sprint 6: Post-Interim Recovery and Final Push Preparation === === Sprint 6: Post-Interim Recovery and Final Push Preparation ===
 Period: **April 16th, 2026 – April 28th, 2026** Period: **April 16th, 2026 – April 28th, 2026**
Line 723: Line 723:
  
 Sprint {{ref>fig:sprint6}} displayed the most extreme "late-crunch" pattern of the project so far. The remaining work stayed flat at the initial commitment of 40 story points until April 20th, with the entire burndown collapsing into a 2-day window between April 22nd and April 24th. The team closed 24.5 points across 9 work items, including the 3D model video (TRAQ-21, 8 pts), the report fixes following interim feedback (TRAQ-168, 8 pts), the leaflet, the poster, the smart system schematics review, the video addition, the lab parts check, three daily meetings, and Retrospective 6. TRAQ-88 ("Chapter Project Management", 12 pts) remained in progress as expected — this item is intentionally kept open across sprints since new content is added to it on every cycle, and it will only be closed at the end of the project. The flat-then-cliff burndown shape reflects the team prioritizing deep work on the larger report and design items before logging completions in a single batch near the end of the sprint, rather than a true delivery delay. Sprint {{ref>fig:sprint6}} displayed the most extreme "late-crunch" pattern of the project so far. The remaining work stayed flat at the initial commitment of 40 story points until April 20th, with the entire burndown collapsing into a 2-day window between April 22nd and April 24th. The team closed 24.5 points across 9 work items, including the 3D model video (TRAQ-21, 8 pts), the report fixes following interim feedback (TRAQ-168, 8 pts), the leaflet, the poster, the smart system schematics review, the video addition, the lab parts check, three daily meetings, and Retrospective 6. TRAQ-88 ("Chapter Project Management", 12 pts) remained in progress as expected — this item is intentionally kept open across sprints since new content is added to it on every cycle, and it will only be closed at the end of the project. The flat-then-cliff burndown shape reflects the team prioritizing deep work on the larger report and design items before logging completions in a single batch near the end of the sprint, rather than a true delivery delay.
 +
 +The burndown opened at roughly 40 story points and stayed flat until April 20. Almost all progress was logged in a single batch around April 23, dropping the remaining work to about 15 points — meaning the team closed roughly 25 points but finished above the ideal guideline, with the rest (chiefly TRAQ-88) carried into the next sprint.
 +
 +
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:sprint6> <figure fig:sprint6>
Line 737: Line 741:
  
 The Sprint that is shown in figure {{ref>fig:sprint7}} was the shortest sprint so far at one week, a tighter cadence following the interim report milestone. The sprint started with a commitment of approximately 23 story points. The burndown once again exhibited the team's characteristic "late-crunch" pattern: remaining work stayed flat from April 23rd through April 27th, dropped by a small amount on April 27th, then plateaued again before the bulk of completions were logged on the final day, April 30th. By the end of the sprint window shown, roughly 9 points had been burned down, leaving approximately 14 points still in progress at the time of capture. As in previous sprints, TRAQ-88 ("Chapter Project Management") is expected to remain open by design, since content continues to be added to it across every sprint and will only close at the end of the project. The Sprint that is shown in figure {{ref>fig:sprint7}} was the shortest sprint so far at one week, a tighter cadence following the interim report milestone. The sprint started with a commitment of approximately 23 story points. The burndown once again exhibited the team's characteristic "late-crunch" pattern: remaining work stayed flat from April 23rd through April 27th, dropped by a small amount on April 27th, then plateaued again before the bulk of completions were logged on the final day, April 30th. By the end of the sprint window shown, roughly 9 points had been burned down, leaving approximately 14 points still in progress at the time of capture. As in previous sprints, TRAQ-88 ("Chapter Project Management") is expected to remain open by design, since content continues to be added to it across every sprint and will only close at the end of the project.
 +
 +With an increase in classes, the team's total workload dropped to 23.5. This is also because the team focused on smaller tasks like Paper etc. 
 +
 +
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:sprint7> <figure fig:sprint7>
Line 747: Line 755:
  
 Sprint 8 in figure {{ref>fig:sprint8}} covered the period from April 30th to May 14th, 2026, with an initial workload of approximately 61 story points. The burndown chart showed a typical late-crunch pattern: after a small reduction at the start of the sprint, progress stayed mostly flat until May 12th, when most tasks were completed. By the end of the sprint, the remaining workload had decreased to around 23 story points, showing significant progress despite work being completed mainly at the end of the sprint. Sprint 8 in figure {{ref>fig:sprint8}} covered the period from April 30th to May 14th, 2026, with an initial workload of approximately 61 story points. The burndown chart showed a typical late-crunch pattern: after a small reduction at the start of the sprint, progress stayed mostly flat until May 12th, when most tasks were completed. By the end of the sprint, the remaining workload had decreased to around 23 story points, showing significant progress despite work being completed mainly at the end of the sprint.
 +
 +Major deadlines this week, so the workload increased to 60. Meet Sprint, a bug came up hence, the chart is going back up.
  
 <WRAP centeralign> <WRAP centeralign>
Line 758: Line 768:
 Sprint 9 in figure {{ref>fig:sprint9}} covered the period from May 14th to May 21st, 2026, with an initial workload of approximately 55 story points. The burndown chart showed very limited progress during most of the sprint, with only small reductions in remaining work occurring near the end of the sprint period. Sprint 9 in figure {{ref>fig:sprint9}} covered the period from May 14th to May 21st, 2026, with an initial workload of approximately 55 story points. The burndown chart showed very limited progress during most of the sprint, with only small reductions in remaining work occurring near the end of the sprint period.
 By the end of the sprint, the workload had decreased to around 43 story points, indicating that only a small portion of tasks was completed during this sprint. The burndown remained far above the ideal progression line throughout the sprint, suggesting that several tasks were still ongoing at the time of capture. By the end of the sprint, the workload had decreased to around 43 story points, indicating that only a small portion of tasks was completed during this sprint. The burndown remained far above the ideal progression line throughout the sprint, suggesting that several tasks were still ongoing at the time of capture.
 +
 +Back to the regular ~50 sprint points. The task that never gets finished is Project Management, as each week we need to add more to it. The teachers also asked us to add more to the app and paper, which is why there is such a big gap in the sprint backlog
 +
 <WRAP centeralign> <WRAP centeralign>
 <figure fig:sprint9> <figure fig:sprint9>
Line 790: Line 803:
 Sprint 12 in Figure {{ref>fig:sprint12}} covered the period from June 4th to June 11th, 2026, with an initial workload of approximately 31 story points. The burndown chart showed steady progress throughout the sprint, with several small reductions in remaining work occurring at regular intervals rather than being concentrated on the final day. Sprint 12 in Figure {{ref>fig:sprint12}} covered the period from June 4th to June 11th, 2026, with an initial workload of approximately 31 story points. The burndown chart showed steady progress throughout the sprint, with several small reductions in remaining work occurring at regular intervals rather than being concentrated on the final day.
 By the end of the sprint, the remaining workload had decreased to approximately 14 story points. Although the team did not fully reach the ideal burndown line, the sprint demonstrated a more consistent completion of tasks compared to earlier sprints, reflecting a gradual closing of the remaining project activities. By the end of the sprint, the remaining workload had decreased to approximately 14 story points. Although the team did not fully reach the ideal burndown line, the sprint demonstrated a more consistent completion of tasks compared to earlier sprints, reflecting a gradual closing of the remaining project activities.
 +
 +A major drop in time as the team project is coming up to an end. Small tasks are remaining. 
  
 <WRAP centeralign> <WRAP centeralign>
Line 800: Line 815:
  
 ==== Sprint Outcomes ==== ==== Sprint Outcomes ====
-/* 
-//Include the outcomes of all sprint reviews (what was the sprint backlog, completion status, planned capacity vs. achieved velocity).// 
-*/ 
  
 +==== Sprint 1 ====
  
 +This subchapter documents the outcome of sprint 1.
 +
 +The following Table {{ref>tab:sprint1}} shows the outcome of sprint 1.
 +
 +<WRAP centeralign>
 +<table tab:sprint1>
 +<caption>Sprint 1 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **23/02/2026 - 04/03/2026** ||||
 +| 1 | Set up the Scrum environment | | Bernardo Josué Corr. | Everyone |
 +| 1 | Chapter 2 Background and Related Work | | Rieke Platthaus | Everyone |
 +| 1 | Filter analyse 2 | | Bernardo Josué Corr. | Everyone |
 +| 1 | Filter analyse 1 | | Ines Margand | Everyone |
 +| 1 | Level of water analyse 2 | | Maria Włodarczyk | Everyone |
 +| 1 | Level of water analyse 1 | | Guillem Vázquez Rol. | Everyone |
 +| 1 | Structural Draft | | Guillem Vázquez Rol. | Everyone |
 +| 1 | BlackBox Diagram | | Maximilian Salmi | Everyone |
 +| 1 | Level of water | | Maximilian Salmi | Everyone |
 +| 1 | Quality of water research | | Rieke Platthaus | Everyone |
 +| 1 | Research Filters | | Ines Margand | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 1 Summary:**
 +
 +**Main Achievements:**
 +  * Set up the Scrum environment and established the project foundation.
 +  * Completed initial research on water filters, water quality, and water level analysis.
 +  * Produced the Structural Draft and BlackBox Diagram, and drafted the Background/Related Work chapter.
 +
 +**Progress Check:** 100% of the planned work for this sprint is finished.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 11
 +
 +
 +==== Sprint 2 ====
 +
 +This subchapter documents the outcome of sprint 2.
 +
 +The following Table {{ref>tab:sprint2}} shows the outcome of sprint 2.
 +
 +<WRAP centeralign>
 +<table tab:sprint2>
 +<caption>Sprint 2 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **05/03/2026 - 11/03/2026** ||||
 +| 2 | Research possible solutions for UV-C protection | | Bernardo Josué Corr. | Everyone |
 +| 2 | Graphic Design | | Guillem Vázquez Rol. | Everyone |
 +| 2 | Update the report with feedback | | Bernardo Josué Corr. | Everyone |
 +| 2 | Update report | | Rieke Platthaus | Everyone |
 +| 2 | Make a list of materials | | Ines Margand | Everyone |
 +| 2 | Spec table with different information | | Maximilian Salmi | Everyone |
 +| 2 | Retrospectives 2 | | Bernardo Josué Corr. | Everyone |
 +| 2 | Chapter 7 Project Development | | Guillem Vázquez Rol. | Everyone |
 +| 2 | Chapter 6 Ethical and Deontological Concerns | | Rieke Platthaus | Everyone |
 +| 2 | Chapter 5 Eco-efficiency Measures for Sustainability | | Rieke Platthaus | Everyone |
 +| 2 | Chapter 4 Marketing Strategy Development | | Maria Włodarczyk | Everyone |
 +| 2 | Chapter 2 Background and Related Work | | Rieke Platthaus | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 2 Summary:**
 +
 +**Main Achievements:**
 +  * Researched UV-C protection solutions and produced the materials list and specification table.
 +  * Updated the report based on feedback and developed multiple report chapters (Marketing Strategy, Eco-efficiency, Ethical Concerns, Project Development).
 +  * Completed graphic design work and conducted Retrospective 2.
 +
 +**Progress Check:** 100% of the planned work for this
 +
 +==== Sprint 3 ====
 +
 +This subchapter documents the outcome of sprint 3.
 +
 +The following Table {{ref>tab:sprint3}} shows the outcome of sprint 3.
 +
 +<WRAP centeralign>
 +<table tab:sprint3>
 +<caption>Sprint 3 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **12/03/2026 - 18/03/2026** ||||
 +| 3 | Daily meeting 25/03/2026 | | Bernardo Josué Corr. | Everyone |
 +| 3 | Daily meeting 23/03/2026 | | Bernardo Josué Corr. | Everyone |
 +| 3 | Daily meeting 20/03/2026 | | Bernardo Josué Corr. | Everyone |
 +| 3 | Companies research | | Unassigned | Everyone |
 +| 3 | Update background materials research | | Ines Margand | Everyone |
 +| 3 | Cardboard Model | | Ines Margand | Everyone |
 +| 3 | Practical solution for 3d system | | Maximilian Salmi | Everyone |
 +| 3 | QR code to Wiki | | Bernardo Josué Corr. | Everyone |
 +| 3 | Chapter Project Management | | Ines Margand | Everyone |
 +| 3 | Flyer | | Bernardo Josué Corr. | Everyone |
 +| 3 | Retrospective 3 | | Bernardo Josué Corr. | Everyone |
 +| 3 | Chapter 7 Project Development | | Guillem Vázquez Rol. | Everyone |
 +| 3 | Chapter 6 Ethical and Deontological Concerns | | Rieke Platthaus | Everyone |
 +| 3 | Chapter 4 Marketing Strategy Development | | Maria Włodarczyk | Everyone |
 +| 3 | Chapter 2 Background and Related Work | | Rieke Platthaus | Everyone |
 +| 3 | Structural Drawings | | Guillem Vázquez Rol. | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 3 Summary:**
 +
 +**Main Achievements:**
 +  * Built the Cardboard Model and developed the practical solution for the 3D system.
 +  * Conducted companies research, updated background materials research, and produced the Flyer and Structural Drawings.
 +  * Added the QR code to the Wiki, advanced multiple report chapters, and held daily stand-ups and Retrospective 3.
 +
 +**Progress Check:** 100% of the planned work for this sprint is finished.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 16
 +  * **Tasks Finished:** 16
 +
 +==== Sprint 4 ====
 +
 +This subchapter documents the outcome of sprint 4.
 +
 +The following Table {{ref>tab:sprint4}} shows the outcome of sprint 4.
 +
 +<WRAP centeralign>
 +<table tab:sprint4>
 +<caption>Sprint 4 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **19/03/2026 - 25/03/2026** ||||
 +| 4 | Chapter Project Management | 12 | IM | Everyone |
 +| 4 | Interim Report | 10 | RP | Everyone |
 +| 4 | Chapter 7 Project Development | 8 | GR | Everyone |
 +| 4 | Chapter 2 Background and Related Work | 9 | RP | Everyone |
 +| 4 | Retrospective 4 | 0.5 | BA | Everyone |
 +| 4 | Interim Presentation | 10 | BA | Everyone |
 +| 4 | Daily meeting 30/03/2026 | 0.5 | MS | Everyone |
 +| 4 | Daily meeting 31/03/2026 | 0.5 | MW | Everyone |
 +| 4 | Schematics Version 2 | 3 | MS | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 4 Summary:**
 +
 +**Main Achievements:**
 +  * Completed the Interim Report and Interim Presentation, including the Background/Related Work and Project Development chapters.
 +  * Finalized Schematics Version 2 and conducted Retrospective 4.
 +  * Held daily stand-up meetings to track progress.
 +
 +**Progress Check:** ~89% of the planned work for this week is finished; the Chapter Project Management item remains in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 9
 +  * **Tasks Finished:** 8
 +
 +==== Sprint 5 ====
 +
 +This subchapter documents the outcome of sprint 5.
 +
 +The following Table {{ref>tab:sprint5}} shows the outcome of sprint 5.
 +
 +<WRAP centeralign>
 +<table tab:sprint5>
 +<caption>Sprint 5 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **26/03/2026 - 01/04/2026** ||||
 +| 5 | Chapter Project Management | 12 | IM | Everyone |
 +| 5 | Interim Report | 10 | RP | Everyone |
 +| 5 | Schematics Version 3 | 3 | GR | Everyone |
 +| 5 | HAND IN REPORT | 0.5 | BA | Everyone |
 +| 5 | Retrospective 5 | 0.5 | MW | Everyone |
 +| 5 | Website | 3 | BA | Everyone |
 +| 5 | Application Prototype | 3 | BA | Everyone |
 +| 5 | Table of power budget | 1.5 | MS | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 5 Summary:**
 +
 +**Main Achievements:**
 +  * Finalized and handed in the Interim Report and produced Schematics Version 3.
 +  * Built the Website and Application Prototype, and created the power budget table.
 +  * Conducted Retrospective 5; the Chapter Project Management item remains in progress.
 +
 +**Progress Check:** ~89% of the planned work for this sprint is finished; Chapter Project Management is still in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 8
 +  * **Tasks Finished:** 7
 +
 +**Scope Changes:** TRAQ-164 (Table of power budget) was added after sprint start, increasing commitment by 1.5 story points (total 33.5).
 +
 +
 +==== Sprint 6 ====
 +
 +This subchapter documents the outcome of sprint 6.
 +
 +The following Table {{ref>tab:sprint6}} shows the outcome of sprint 6.
 +
 +<WRAP centeralign>
 +<table tab:sprint6>
 +<caption>Sprint 6 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **16/04/2026 - 22/04/2026** ||||
 +| 6 | Chapter Project Management | 12 | IM | Everyone |
 +| 6 | Video add | 2 | MW | Everyone |
 +| 6 | Check lab for pieces | 1 | MS | Everyone |
 +| 6 | 3D model video | 8 | GR | Everyone |
 +| 6 | Retrospective 6 | 0.5 | RP | Everyone |
 +| 6 | Daily Meeting 22/04/2026 | 0.5 | GR | Everyone |
 +| 6 | Daily Meeting 21/04/2026 | 0.5 | MS | Everyone |
 +| 6 | Daily meeting 20/04/2026 | 0.5 | MW | Everyone |
 +| 6 | Fix report after Interm report | 8 | RP | Everyone |
 +| 6 | Leeflet | 3 | MW | Everyone |
 +| 6 | Review Smart system schematics | 2 | MS | Everyone |
 +| 6 | Poster | 2 | IM | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 6 Summary:**
 +
 +**Main Achievements:**
 +  * Produced the 3D model video, Leaflet, and Poster, and fixed the report after the interim feedback.
 +  * Reviewed the Smart System schematics, added the video, and checked the lab for pieces.
 +  * Held daily stand-ups and Retrospective 6; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~92% of the planned work for this sprint is finished; Chapter Project Management is still in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 12
 +  * **Tasks Finished:** 11
 +
 +
 +==== Sprint 7 ====
 +
 +This subchapter documents the outcome of sprint 7.
 +
 +The following Table {{ref>tab:sprint7}} shows the outcome of sprint 7.
 +
 +<WRAP centeralign>
 +<table tab:sprint7>
 +<caption>Sprint 7 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **23/04/2026 - 29/04/2026** ||||
 +| 7 | Chapter Project Management | 3 | IM | Everyone |
 +| 7 | Packing solutions | 6 | IM | Everyone |
 +| 7 | Paper | 5 | RP | Everyone |
 +| 7 | Check lab for pieces | 1 | MS | Everyone |
 +| 7 | Video add | 3 | MW | Everyone |
 +| 7 | Final list of material and components | 2 | MS | Everyone |
 +| 7 | Retrospective 7 | 0.5 | IM | Everyone |
 +| 7 | Daily Meeting 24/04/2026 | 0.5 | IM | Everyone |
 +| 7 | Daily Meeting 28/04/2026 | 0.5 | GR | Everyone |
 +| 7 | Daily Meeting 29/04/2026 | 0.6 | MS | Everyone |
 +| 7 | Add small details for 3d Video | 1 | BA | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 7 Summary:**
 +
 +**Main Achievements:**
 +  * Developed packing solutions and finalized the list of materials and components.
 +  * Advanced the Paper, refined the 3D video with additional details, and completed the video add.
 +  * Held daily stand-ups and Retrospective 7; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~73% of the planned work for this sprint is finished; Chapter Project Management, Packing solutions, and Paper remained open at sprint close.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 8
 +
 +
 +==== Sprint 8 ====
 +
 +This subchapter documents the outcome of sprint 8.
 +
 +The following Table {{ref>tab:sprint8}} shows the outcome of sprint 8.
 +
 +<WRAP centeralign>
 +<table tab:sprint8>
 +<caption>Sprint 8 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **07/05/2026 - 13/05/2026** ||||
 +| 8 | Chapter Project Management | 3 | IM | Everyone |
 +| 8 | Paper | 20 | RP | Everyone |
 +| 8 | Packing solutions | 6 | IM | Everyone |
 +| 8 | Retrospective 8 | - | RP | Everyone |
 +| 8 | Establish the costs for the aluminum bottle and plastic | 8 | BA | Everyone |
 +| 8 | 3D Model | 10 | GR | Everyone |
 +| 8 | Reviews the excel lists | 5 | MS | Everyone |
 +| 8 | Daily meeting 12/05/2026 | 0.5 | MW | Everyone |
 +| 8 | Daily meeting 13/05/2026 | 0.5 | GR | Everyone |
 +| 8 | Daily meeting 11/05/2026 | 0.5 | MS | Everyone |
 +| 8 | Deliver interm report after feedback | 8 | MW | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 8 Summary:**
 +
 +**Main Achievements:**
 +  * Built the 3D Model and established costs for the aluminum bottle and plastic.
 +  * Delivered the interim report after feedback, reviewed the Excel lists, and progressed the Paper and packing solutions.
 +  * Held daily stand-ups and Retrospective 8; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~82% of the planned work for this sprint is finished; Chapter Project Management and Paper remained open at sprint close.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 9
 +
 +==== Sprint 9 ====
 +
 +This subchapter documents the outcome of sprint 9.
 +
 +The following Table {{ref>tab:sprint9}} shows the outcome of sprint 9.
 +
 +<WRAP centeralign>
 +<table tab:sprint9>
 +<caption>Sprint 9 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **14/05/2026 - 20/05/2026** ||||
 +| 9 | Chapter Project Management | 3 | IM | Everyone |
 +| 9 | Paper | 20 | RP | Everyone |
 +| 9 | App | 10 | BA | Everyone |
 +| 9 | Manuel | 4 | MW | Everyone |
 +| 9 | Retrospective 9 | 0.5 | MS | Everyone |
 +| 9 | 3D Printing | 5 | GR | Everyone |
 +| 9 | Fix packing Poster | 1 | IM | Everyone |
 +| 9 | Hardware configuration | 10 | MS | Everyone |
 +| 9 | Daily meetings 15/05/2026 | 0.5 | BA | Everyone |
 +| 9 | Daily meeting 18/05/2026 | 0.5 | RP | Everyone |
 +| 9 | Daily meeting 19/05/2026 | 0.5 | GR | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 9 Summary:**
 +
 +**Main Achievements:**
 +  * Completed 3D printing, hardware configuration, and the user Manual.
 +  * Fixed the packing poster and progressed the Paper and App.
 +  * Held daily stand-ups and Retrospective 9; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~82% of the planned work for this sprint is finished; Chapter Project Management, Paper, and App remained open at sprint close.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 8
 +
 +
 +==== Sprint 10 ====
 +
 +This subchapter documents the outcome of sprint 10.
 +
 +The following Table {{ref>tab:sprint10}} shows the outcome of sprint 10.
 +
 +<WRAP centeralign>
 +<table tab:sprint10>
 +<caption>Sprint 10 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **21/05/2026 - 27/05/2026** ||||
 +| 10 | Chapter Project Management | 3 | IM | Everyone |
 +| 10 | Paper | 20 | RP | Everyone |
 +| 10 | App | 10 | BA | Everyone |
 +| 10 | Retrospective 10 | 1 | IM | Everyone |
 +| 10 | Stress test | 5 | GR | Everyone |
 +| 10 | Test of components | 5 | MS | Everyone |
 +| 10 | Soldering | 1 | MS | Everyone |
 +| 10 | Overview Paper hand in | - | MW | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 10 Summary:**
 +
 +**Main Achievements:**
 +  * Conducted the stress test and test of components, and completed soldering work.
 +  * Handed in the paper overview and finalized the App and Paper.
 +  * Held Retrospective 10; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~88% of the planned work for this sprint is finished; Chapter Project Management is still in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 8
 +  * **Tasks Finished:** 7
 +
 +
 +==== Sprint 11 ====
 +
 +This subchapter documents the outcome of sprint 11.
 +
 +The following Table {{ref>tab:sprint11}} shows the outcome of sprint 11.
 +
 +<WRAP centeralign>
 +<table tab:sprint11>
 +<caption>Sprint 11 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **28/05/2026 - 03/06/2026** ||||
 +| 11 | Chapter Project Management | 3 | IM | Everyone |
 +| 11 | UV-C Light | 5 | BA | Everyone |
 +| 11 | Review the Feedback on the paper | 10 | RP | Everyone |
 +| 11 | Daily meeting 29/05/2026 | 0.5 | GR | Everyone |
 +| 11 | Daily meeting 01/06/2026 | 0.6 | GR | Everyone |
 +| 11 | Daily meeting 02/06/2026 | 0.5 | MW | Everyone |
 +| 11 | Retrospective 11 | 1 | MW | Everyone |
 +| 11 | Simulation | 12 | GR | Everyone |
 +| 11 | Power supply adjustement | 4 | MS | Everyone |
 +| 11 | Polish up report | 10 | MW | Everyone |
 +| 11 | Fix typos in test report and plan | 3 | IM | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 11 Summary:**
 +
 +**Main Achievements:**
 +  * Ran the Simulation and completed the power supply adjustment and UV-C Light work.
 +  * Reviewed paper feedback, polished the report, and fixed typos in the test report and plan.
 +  * Held daily stand-ups and Retrospective 11; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~91% of the planned work for this sprint is finished; Chapter Project Management is still in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 10
 +
 +
 +==== Sprint 12 ====
 +
 +This subchapter documents the outcome of sprint 12.
 +
 +The following Table {{ref>tab:sprint12}} shows the outcome of sprint 12.
 +
 +<WRAP centeralign>
 +<table tab:sprint12>
 +<caption>Sprint 12 Overview</caption>
 +<WRAP box center>
 +| Sprint | Task | Duration | Responsible | Involved |
 +| **04/06/2026 - 10/06/2026** ||||
 +| 12 | Chapter Project Management | 3 | IM | Everyone |
 +| 12 | UV-C Light | 5 | BA | Everyone |
 +| 12 | Final Presentation | 6 | MW | Everyone |
 +| 12 | Summary of report | 2 | MW | Everyone |
 +| 12 | Conclusion of each chapter | 5 | GR | Everyone |
 +| 12 | Work on comments of the report | 5 | RP | Everyone |
 +| 12 | Mount UV-c light assist testing | 5 | MS | Everyone |
 +| 12 | Retrospective | - | BA | Everyone |
 +</WRAP>
 +</table>
 +</WRAP>
 +
 +**Sprint 12 Summary:**
 +
 +**Main Achievements:**
 +  * Prepared the Final Presentation, report summary, and per-chapter conclusions.
 +  * Mounted the UV-C light for assisted testing and addressed report comments.
 +  * Held the Retrospective; Chapter Project Management remains in progress.
 +
 +**Progress Check:** ~88% of the planned work for this sprint is finished; Chapter Project Management is still in progress.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 8
 +  * **Tasks Finished:** 7
 +
 +**Scope Changes:** TRAQ-220 (Retrospective) was added after sprint start.
 ==== Sprint Evaluations ==== ==== Sprint Evaluations ====
 /* /*
Line 815: Line 1308:
  
  
-<figure fig:retro1> 
 <WRAP centeralign> <WRAP centeralign>
 +<figure fig:retro1>
 {{:report:retro_1.png?800|}} {{:report:retro_1.png?800|}}
 {{:report:retro_1bis.png?800|}} {{:report:retro_1bis.png?800|}}
Line 930: Line 1423:
  
 ==== Summary ==== ==== Summary ====
 +
 +
 +
 +This chapter described how the TRAQUA project was planned, organised, and managed from start to finish. Using an agile Scrum framework with weekly sprints, the team structured its work around a Jira backlog, milestone-driven prioritisation, and regular ceremonies — planning, stand-ups, retrospectives, and demos — that kept progress aligned with the deliverable deadlines defined in the project plan.
 +
 +<WRAP centeralign>
 +<figure fig:velocity>
 +{{:report:velocity.png?400|}}
 +<caption>TRAQUA Velocity report</caption>
 +</figure>
 +</WRAP>
 +
 +
 +The twelve sprints reveal a clear evolution in the team's process. Early sprints showed a recurring "late-crunch" pattern, where most work was completed in a short window near the end of each cycle, and commitment regularly exceeded the work actually delivered. As shown in the velocity chart ({{ref>fig:velocity}}), the gap between committed and completed story points was widest in the middle sprints but narrowed considerably toward the end of the project: in the final sprints the completed work closely matched the commitment, indicating that the team's estimation and planning matured over time. The team settled at an average velocity of roughly 29 story points per sprint.
 +
 +The retrospectives were central to this improvement. Recurring issues — uneven workload distribution stemming from the team's mixed technical backgrounds, late absence notices, inconsistent Jira updates, and slow external feedback — were identified and acted upon, including a revised Definition of Done that restored burndown accuracy after Sprint 3. Risk management and procurement were handled proactively, with early ordering and backup suppliers limiting the impact of component delays.
 +
 +Overall, the project was delivered on schedule and met its milestones, and the team finished with a markedly more predictable and disciplined process than it began with. With the product developed and the project successfully managed, the next chapter turns to the marketing plan, examining how TRAQUA could be positioned and brought to market.
 +
  
  • report/prm.1781174523.txt.gz
  • Last modified: 2026/06/11 11:42
  • by team3