Differences

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

--- report:prm [2026/06/12 22:02] – [Sprint 9] team6
+++ report:prm [2026/06/14 00:05] (current) – [Summary] team6
@@ Line 455: / 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 466: / 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 477: / 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 488: / 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 525: / 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.