Differences

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

--- report:prm [2026/06/12 21:39] – [Sprint 10: June 4th - June 11th 2026] team6
+++ report:prm [2026/06/14 00:05] (current) – [Summary] team6
@@ Line 434: / Line 434: @@
 \\
-Looking at Figure {{ref>fig:VelocityReport}}, the
+The velocity report in Figure {{ref>fig:VelocityReport}} shows the number of story points planned and completed for each sprint. It indicates an average of 8.38 completed story points, but this doesn't truly represent our actual story point completion rate. We need to average the last three sprints completed successfully. Our average story points completed is then 18 for the last three sprints. We would need to complete more sprints to obtain an average that accurately reflects our true capacity, and thus be able to properly plan task completion during sprints.
 <WRAP centeralign>
@@ Line 448: / Line 448: @@
 ==== Sprint Evaluations ====
-//Include the summary of all the sprint retrospectives, including any actions implemented as part of the team’s continuous improvement strategy.//
 This section provides a retrospective analysis of each sprint, highlighting successes, challenges, and opportunities for improvement. It examines team performance, project progress, and lessons learned, with the objective of continuously improving future sprint planning and execution.
@@ Line 456: / Line 455: @@
 <WRAP centeralign>
 <figure fig:Sprint5retro>
-{{ :report:sprint_5_retro.png?direct&600 |}}
+{{ :report:sprint_5_retro.png?direct& |}}
 <caption>Sprint 5 retrospective</caption>
 </figure>
@@ Line 467: / Line 466: @@
 <WRAP centeralign>
 <figure fig:Sprint6retro>
-{{ :report:sprint_6_retro.png?direct&600 |}}
+{{ :report:sprint_6_retro.png?direct& |}}
 <caption>Sprint 6 retrospective</caption>
 </figure>
@@ Line 478: / Line 477: @@
 <WRAP centeralign>
 <figure fig:Sprint7retro>
-{{ :report:sprint_7_retro.png?direct&600 |}}
+{{ :report:sprint_7_retro.png?direct& |}}
 <caption>Sprint 7 retrospective</caption>
 </figure>
@@ Line 489: / Line 488: @@
 <WRAP centeralign>
 <figure fig:Sprint8retro>
-{{ :report:sprint_8_retro.png?direct&600 |}}
+{{ :report:sprint_8_retro.png?direct& |}}
 <caption>Sprint 8 retrospective</caption>
 </figure>
@@ Line 501: / Line 500: @@
 <WRAP centeralign>
 <figure fig:Sprint9retro>
+{{ :report:sprint_9_retro.png?direct& |}}
 <caption>Sprint 9 retrospective</caption>
 </figure>
 </WRAP>
 \\
+=== Sprint 10 ===
+Looking at Figure {{ref>fig:Sprint10retro}} the team successfully completed several planned tasks, including designing the 3D part in SolidWorks, improving the quality control section of the Wiki, and finalizing the project video. However, the prototype assembly was delayed because we were waiting for validation of the 3D-printed component. We also observed that adding story points after the sprint had started negatively impacted the burndown chart. For future sprints, we aim to improve our planning by using previous sprint velocity to estimate workloads more accurately while continuing to make progress despite technical constraints.
+<WRAP centeralign>
+<figure fig:Sprint10retro>
+{{ :report:sprint_10_retro.png?direct& |}}
+<caption>Sprint 10 retrospective</caption>
+</figure>
+</WRAP>
+\\
 === Retrospective Summary ===
 Throughout the project, the team demonstrated a strong ability to achieve sprint objectives and continuously improve both technical deliverables and project documentation. Significant progress was made in prototype development, testing, reporting, and communication materials, while the team also showed resilience in overcoming technical challenges and external constraints.
@@ Line 513: / Line 525: @@
 ==== Summary ====
-//Provide here the conclusions of this chapter and make the bridge to the next chapter.//
+This chapter summarised the project management approach used for developing the Healing Cocoon prototype, a proof-of-concept designed to reduce anxiety in children in clinical waiting environments. The project scope focused on research, design, and development, organised using a Work Breakdown Structure (WBS) to structure tasks and responsibilities.
+The project was managed through short, structured development cycles with weekly planning sessions and Jira task tracking, enabling steady progress and flexibility over the 15-week timeline. The project was completed within a €100 budget by prioritising low-cost materials and components while maintaining core functionality.
+Quality was ensured through iterative testing, supervisor feedback, and a focus on safety, hygiene, accessibility, and reliability. Key stakeholders, including healthcare professionals, patients, supervisors, and suppliers, were considered throughout development.
+Communication was maintained using WhatsApp, Microsoft Teams, Outlook, and Jira to support effective collaboration. Risks were continuously identified and mitigated, while procurement decisions balanced cost, performance, and availability.
+Overall, this structured and iterative development process, supported by continuous feedback, allowed the team to deliver a functional prototype within the defined constraints of scope, time, cost, and quality.