report

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 [2025/06/16 18:01] – team2report [2025/06/25 16:45] (current) – [Glossary] team2
Line 23: Line 23:
 |ISEP|Instituto Superior de Engenharia do Porto| |ISEP|Instituto Superior de Engenharia do Porto|
 |USB |Universal Serial Bus| |USB |Universal Serial Bus|
-|E |Esther| 
-|F |Flavius| 
-|J|Jouke| 
-|M |Mateusz| 
-|T |Tim| 
-|V |Victor| 
 |QR | Quick-Response| |QR | Quick-Response|
 +|RAM | Random Access Memory|
 +|GHz | Gigahertz – billions of cycles per second|
 |Internet | A global computer network providing a variety of information and communication facilities| |Internet | A global computer network providing a variety of information and communication facilities|
 </WRAP> </WRAP>
Line 745: Line 741:
 <WRAP center> <WRAP center>
 ^ Sprint    ^ Start          ^ Finish     ^ Status     ^ ^ Sprint    ^ Start          ^ Finish     ^ Status     ^
-| 1         | 27-02-2025     | 06-03-2025    | Finished   |  +| 1         | 27/02/2025     | 05/03/2025 | Finished   | 
-| 2         | 06-03-2025     | 13-03-2025   | Finished   |  +| 2         | 06/03/2025     | 12/03/2025 | Finished   | 
-| 3         | 13-03-2025     | 20-03-2025   | Finished|       +| 3         | 13/03/2025     | 19/03/2025 | Finished   | 
-| 4         | 20-03-2025     | 27-03-2025   | Finished  | +| 4         | 20/03/2025     | 26/03/2025 | Finished   | 
-| 5         | 27-03-2025     | 03-04-2025   | Finished  | +| 5         | 27/03/2025     | 02/04/2025 | Finished   | 
-| 6         | 03-04-2025     | 10-04-2025   | Started  |  +| 6         | 03/04/2025     | 09/04/2025 | Finished   | 
-| 7         | 10-04-2025     | 17-04-2025   | Not Started  | +| 7         | 10/04/2025     | 16/04/2025 | Finished   | 
-| 8         | 17-04-2025     | 24-04-2025   | Not Started  | +| 8         | 17/04/2025     | 30/04/2025 | Finished   | 
-| 9         | 24-04-2025     | 01-05-2025   | Not Started  | +| 9         | 30/04/2025     | 14/05/2025 | Finished   | 
-| 10         | 01-05-2025     | 08-05-2025   | Not Started  | +| 10        | 15/05/2025     | 21/05/2025 | Finished   | 
-| 11         | 08-05-2025     | 15-05-2025   | Not Started  | +| 11        | 22/05/2025     | 28/05/2025 | Finished   | 
-| 12         | 15-05-2025     | 22-05-2025   | Not Started  | +| 12        | 29/05/2025     | 04/06/2025 | Finished   | 
-| 13         | 22-05-2025     | 29-05-2025   | Not Started  | +| 13        | 05/06/2025     | 11/06/2025 | Finished   | 
-| 14         | 29-05-2025     | 05-06-2025   | Not Started  | +| 14        | 12/06/2025     | 18/06/2025 | Ongoing    |
-| 15         | 05-06-2025     | 12-06-2025   | Not Started  | +
-| 16         | 05-06-2025     | 12-06-2025   | Not Started  | +
-| 17         | 12-06-2025     | 17-06-2025   | Not Started  |+
 </WRAP> </WRAP>
 </table> </table>
 </WRAP> </WRAP>
 +
  
 The following project backlog outlines the key deliverables essential to the successful execution of the EPS project. These tasks have been meticulously structured in a logical sequence to ensure a coherent, efficient, and well-coordinated workflow. By adhering to this order, the project can maintain a seamless progression of work, minimizing disruptions and optimizing productivity throughout the project's lifecycle. The full breakdown of these deliverables can be found in Tabel {{ref>tlabel1}}. The following project backlog outlines the key deliverables essential to the successful execution of the EPS project. These tasks have been meticulously structured in a logical sequence to ensure a coherent, efficient, and well-coordinated workflow. By adhering to this order, the project can maintain a seamless progression of work, minimizing disruptions and optimizing productivity throughout the project's lifecycle. The full breakdown of these deliverables can be found in Tabel {{ref>tlabel1}}.
 +
 <WRAP round box 400px center> <WRAP round box 400px center>
 <table tlabel1> <table tlabel1>
-<caption>Project Backlog</caption>+<caption>Updated Project Backlog</caption>
 <WRAP center> <WRAP center>
-^ PBI       ^ Title          ^ Status     ^ +^ PBI ^ Title                                      ^ Status        ^ 
-| A         | Define Project    | Done      |  +| A   | Define Project                             | Done          | 
-| B         | Black Box Diagram    | Done      |   +| B   | Black Box Diagram                          | Done          | 
-| C         | Structural Drafts    | Done      |   +| C   | Structural Drafts                          | Done          | 
-| D         | Project Backlog    | Done      |       +| D   | Project Backlog                            | Done          | 
-| E         | Global Sprint Plan    | Done      |    +| E   | Global Sprint Plan                         | Done          | 
-| F         | Initial Sprint Plan    | Done      |    +| F   | Initial Sprint Plan                        | Done          | 
-| G         | List of Components and Materials    | Done    |    +| G   | List of Components and Materials           | Done          | 
-| H         | Detailed Schematics    | To do      |   +| H   | Detailed Schematics                        | Done          | 
-| I         | Structural Drawings    | To do      |     +| I   | Structural Drawings                        | Done          | 
-| J         | Cardboard Model    | To do      |   +| J   | Cardboard Model                            | Done          | 
-| K         | Upload Interim Deliverables    | To do      |   +| K   | Upload Interim Deliverables                | Done          | 
-| L         | S&P Assessment    | To do      |    +| L   | S&P Assessment                             | Done          | 
-| M         | 3D Model Video    | To do      |   +| M   | 3D Model Video                             | Done          | 
-| N         | Final List of Materials & Components    | To do      |   +| N   | Final List of Materials & Components       | Done          | 
-| O         | Refined Report    | To do      |   +| O   | Refined Report                             | Done          | 
-| P         | Packaging Solution    | To do      |   +| P   | Packaging Solution                         | Done          | 
-| Q         | Functional Tests    | To do      |   +| Q   | Functional Tests                           | Done          | 
-| R         | Upload Final Deliverables    | To do      |   +| R   | Upload Final Deliverables                  | Done          | 
-| S         | Final Presentation    | To do      |  +| S   | Final Presentation                         | Done          | 
 +| T   | Transfer Scope to Canva                    | Done          | 
 +| U   | Power Budget Analysis                      | Done          | 
 +| V   | Project and Engineering Backlogs Definition| Done          | 
 +| W   | Engineering Ethics Section                 | Done          | 
 +| X   | Sustainability Section                     | Done          | 
 +| Y   | Business Model Canvas                      | Done          | 
 +| Z   | Flyer and Leaflet Design                   | Done          | 
 +| AA  | 3D Model Updates (Tablet, Cabling)         | Done          | 
 +| AB  | UI Design and Application Screens          | Done          | 
 +| AC  | Controller Requirements and Draw Logic     | Done          | 
 +| AD  | Login and Registration Logic               | Done          | 
 +| AE  | App Authentication and API Tests           | Done          | 
 +| AF  | Raspberry Pi Setup                         | Done          | 
 +| AG  | Multi-user Simulation                      | Done          | 
 +| AH  | SWOT Analysis and Strategy Docs            | Done          | 
 +| AI  | User Manual and Assembly Guide             | Done          | 
 +| AJ  | Load and Stress Simulations                | Done          | 
 +| AK  | Risk and Liability Assessment              | Done          | 
 +| AL  | Marketing Programmes and Materials         | Done          | 
 +| AM  | Stakeholder Management                     | Done          | 
 +| AN  | Burnup Charts and Sprint Refinement        | Done          | 
 +| AO  | Communication Plan                         | Done          | 
 +| AP  | Procurement List and Sourcing              | Done          | 
 +| AQ  | Refine UN SDG section                      | Done          | 
 +| AR  | Project Paper and Documentation            | Done          | 
 +| AS  | Final Deliverables Submission              | Done          |
 </WRAP> </WRAP>
 </table> </table>
 </WRAP> </WRAP>
 +
  
  
Line 925: Line 947:
  
 ==== - Sprint Outcomes ==== ==== - Sprint Outcomes ====
 +
 +There is no sprint burn-up charts for these sprints, Which have been further explained in the summary.
 +
  
 === Sprint 1 Outcome === === Sprint 1 Outcome ===
-The first sprint focused on team formation, orientation, and setting up the basic project framework. The team chose the project topic and familiarized themselves with project management tools and introductory coursework.+Sprint 1 focused on topic selection and tool familiarization.
  
-Sprint Backlog:+**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
 | Choose topic | Everyone | | Choose topic | Everyone |
 | Jira's learning | Everyone | | Jira's learning | Everyone |
-| Classes | Everyone | 
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Selected project topic. 
-| Project topic selected | +  * Jira board set up and team onboarded.
-| Jira platform learning completed | +
-| Attendance of introductory classes | +
-| Team-building activities | +
-| Initial documentation of project ideas | +
-| Group Attitude Rules document | +
-| Elevator Pitch and Blackbox Diagram |+
  
-Completion Status: 100 % of tasks completed.+**Completion Status:** 100% of tasks completed.
  
-Planned Capacity vs. Achieved Velocity: +**Planned Capacity vs. Achieved Velocity:** 
-- **Planned**: 3 tasks   +  * **Planned:** 2 tasks 
-- **Achieved**: 3 tasks  +  * **Achieved:** 2 tasks
  
-There is no burn-up chart for sprint 1. 
- 
---- 
  
 === Sprint 2 Outcome === === Sprint 2 Outcome ===
-Sprint 2 focused on refining the project scope, assessing existing solutions, and formalizing core project documents. The project name **DrawYourWay** was chosen, and the Blackbox Diagram was finalized.+Sprint 2 developed the initial conceptual framework and project scope.
  
-Sprint Backlog:+**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
-| Blackbox Diagram | Jouke, Esther | +| Blackbox Diagram | Jouke | 
-| Scope definition | Jouke, Mateusz | +| Scope | Mateusz | 
-| State Of The Art research | Victor |+| State of the art | Victor |
 | Drawings | Tim | | Drawings | Tim |
-| Weekly Report | Flavius | 
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Blackbox Diagram. 
-| Final Blackbox Diagram | +  * Project Scope Document. 
-| Defined project scope | +  * State of the Art Summary. 
-| State of the art research | +  * Initial Concept Drawings.
-| Initial project drawings | +
-| Weekly report | +
-| Official project name selected: DrawYourWay |+
  
-Completion Status: 100 % of tasks completed.+**Completion Status:** 100%
  
-Planned Capacity vs. Achieved Velocity: +**Planned vs. Achieved:** 
-- **Planned**: 5 tasks   +  * Planned: 4 
-- **Achieved**: 5 tasks  +  * Achieved: 4
  
-<WRAP centeralign> 
-<figure Burnup2-figure> 
-{{:sprint_burnup_2.png?600|}} 
-<caption>Burn-up chart sprint 2</caption> 
-</figure> 
-</WRAP> 
- 
---- 
  
 === Sprint 3 Outcome === === Sprint 3 Outcome ===
-Sprint 3 advanced the technical foundation of the project, developing the first 3D model, analyzing materials cost, and addressing ethics, sustainability, and marketing concerns.+Focused on technical, marketing, and ethical groundwork.
  
-Sprint Backlog:+**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
 | 3D Model File | Tim | | 3D Model File | Tim |
 | Materials Cost | Everyone | | Materials Cost | Everyone |
-| Ethics - 1,2,3 | Esther | +| Engineering ethics | Esther | 
-| Marketing - 1,2,3 | Mateusz | +| Marketing chapter | Mateusz | 
-| Sustainability - 1,2,3 | Flavius | +| Sustainability | Flavius |
-| State Of The Art - 1,2,3 | Victor | +
-| Weekly Report | Tim |+
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Preliminary 3D Model. 
-| 3D model prototype | +  * Material cost estimates. 
-| Materials cost analysis | +  * Ethics document. 
-| Ethics, sustainability, and marketing reports | +  * Marketing chapter draft. 
-| Updated state of the art review | +  * Sustainability chapter.
-| Weekly report |+
  
-Completion Status: 100 % of tasks completed. +**Completion Status:** 100%
- +
-Planned Capacity vs. Achieved Velocity: +
-- **Planned**: 7 tasks   +
-- **Achieved**: 7 tasks   +
- +
-<WRAP centeralign> +
-<figure Burnup3-figure> +
-{{:sprint_burnup_3.png?600|}} +
-<caption>Burn-up chart sprint 3</caption> +
-</figure> +
-</WRAP>+
  
----+**Planned vs. Achieved:** 
 +  * 5 / 5
  
 === Sprint 4 Outcome === === Sprint 4 Outcome ===
-Sprint 4 emphasized technical documentation, engineering backlog development, Gantt chart updates, and promotional content creation.+Detailed scope, schematics and backlog preparation.
  
-Sprint Backlog:+**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
 | Transfer Scope to Canva | Esther | | Transfer Scope to Canva | Esther |
-| Flyer | Esther | 
 | Detailed Schematics | Tim | | Detailed Schematics | Tim |
-| Fill Sprints On Wiki | Jouke | 
 | Define Engineering Backlog | Mateusz | | Define Engineering Backlog | Mateusz |
-| Improve “Project” Section on Wiki | Jouke | +| Project chapter | Jouke | 
-| Project Development Wiki / Section 1, 2, 3 | Flavius |+| Improve Blackbox | Mateusz | 
 +| Project Development | Flavius |
 | Define Design Backlog | Victor | | Define Design Backlog | Victor |
 | Change report to impersonal form | Flavius | | Change report to impersonal form | Flavius |
 +
 +**Key Deliverables:**
 +  * Updated Scope.
 +  * Schematics.
 +  * Engineering/Design Backlogs.
 +  * Project Chapter.
 +  * Blackbox Revision.
 +  * Report converted to impersonal form.
 +
 +**Completion Status:** 100%
 +
 +**Planned vs. Achieved:** 8/8
 +
 +
 +=== Sprint 5 Outcome ===
 +Technical detailing, Gantt chart and promotional design.
 +
 +**Sprint Backlog:**
 +^ Task ^ Responsible ^
 | Power Budget Analysis | Tim | | Power Budget Analysis | Tim |
-| Add milestones to Gantt Chart | Victor | +| Add milestones and human resources to Gantt Chart | Victor | 
-| Add tablet/cabling system to 3D model | Tim |+| Add tablet and cabling system to 3D Model | Tim |
 | Improve Business Model Canvas | Flavius | | Improve Business Model Canvas | Flavius |
 | Define Engineering Backlog Hardware | Tim | | Define Engineering Backlog Hardware | Tim |
-| Controller Part of List of Materials | Mateusz | +| Selection study for components/materials | Jouke, Mateusz | 
-| User Stories/Cases | Mateusz | +| Flyer | Esther |
-| Weekly Report & Activities | Mateusz | +
-| Component/Materials Selection Study | Jouke | +
-| Improve Blackbox | Mateusz |+
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Power Budget. 
-| Transfer of scope to Canva | +  * Gantt Milestones. 
-| Promotional flyer | +  * Updated 3D Model. 
-| Detailed schematics | +  * Improved BMC. 
-| Completed Wiki updates | +  * Hardware Backlog. 
-| Engineering and Design backlogs | +  * Selection Study. 
-| Power budget analysis | +  * Promotional Flyer.
-| Updated Business Model Canvas | +
-| Controller and materials selection | +
-| Updated Blackbox Diagram | +
-| Weekly Report |+
  
-Completion Status: 100 % of tasks completed.+**Completion Status:** 100%
  
-Planned Capacity vs. Achieved Velocity: +**Planned vs. Achieved:** 7/7
-- **Planned**: 19 tasks   +
-- **Achieved**: 19 tasks  +
  
-<WRAP centeralign> 
-<figure Burnup4-figure> 
-{{:sprint_burnup_4.png?600|}} 
-<caption>Burn-up chart sprint 4</caption> 
-</figure> 
-</WRAP> 
  
---- +=== Sprint 6 Outcome === 
- +App foundations, model/flyer refinement, and market analysis.
-=== Sprint 5 Outcome === +
-Sprint 5 focused on backend development, flyer refinement, 3D model improvements, and market analysis.+
  
-Sprint Backlog:+**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
 | Controller Requirements | Mateusz | | Controller Requirements | Mateusz |
-| Authentication Logic on Backend | Mateusz |+| Authentication Logic On Backend | Mateusz |
 | Create Repositories | Flavius | | Create Repositories | Flavius |
 | Install Dependencies | Flavius | | Install Dependencies | Flavius |
-| Refine Flyer | Esther | +| Refine Flyer based on feedback | Esther | 
-| Improve 3D Model | Tim | +| Refine 3D model based on feedback | Tim | 
-| SWOT Analysis | Victor |+| SWOT | Victor |
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Controller/Backend logic. 
-| Backend controller requirements | +  * Repositories & Dependencies. 
-| Authentication backend logic | +  * Updated Flyer and 3D Model. 
-| Project repositories and dependencies | +  * SWOT Analysis.
-| Refined flyer | +
-| Enhanced 3D model | +
-| SWOT market analysis |+
  
-Completion Status: 100 % of tasks completed.+**Completion Status:** 100%
  
-Planned Capacity vs. Achieved Velocity: +**Planned vs. Achieved:** 7/7
-- **Planned**: 7 tasks   +
-- **Achieved**: 7 tasks  +
  
-<WRAP centeralign> 
-<figure Burnup5-figure> 
-{{:sprint_burnup_5.png?600|}} 
-<caption>Burn-up chart sprint 5</caption> 
-</figure> 
-</WRAP> 
  
----+=== Sprint 7 Outcome === 
 +Application UI and report progress.
  
-=== Sprint 6 Outcome === +**Sprint Backlog:**
-Sprint 6 initiated hands-on prototype development, covering backend functionality, UI design, system setup, packaging, and market research. +
- +
-Sprint Backlog:+
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
-| QR Code Logic | Mateusz |+| Drawing Screen | Mateusz | 
 +| Refining of the report | Victor | 
 +| Create 3D model video | Tim |
 | Drawing Logic | Mateusz | | Drawing Logic | Mateusz |
 +| Set Up Raspberry PI | Jouke |
 +| Application Screen Designs | Esther |
 +| Login Screen | Flavius |
 +
 +**Key Deliverables:**
 +  * Drawing Screen.
 +  * Report Refinement.
 +  * 3D Video.
 +  * Raspberry PI.
 +  * Login & App Screens.
 +
 +**Completion Status:** 100%
 +
 +**Planned vs. Achieved:** 7/7
 +
 +
 +=== Sprint 8 Outcome ===
 +Account screens, packaging, and marketing assets.
 +
 +**Sprint Backlog:**
 +^ Task ^ Responsible ^
 +| Register Screen | Flavius |
 +| Forgot Password Screen | Flavius |
 +| Packaging solution | Jouke |
 | Word Breakdown | Mateusz | | Word Breakdown | Mateusz |
 | Marketing Conclusions | Mateusz | | Marketing Conclusions | Mateusz |
-| Drawing Screen Design | Esther | 
-| Forgot Password Screen Design | Esther | 
 | Leaflet | Esther | | Leaflet | Esther |
 | Flyer | Esther | | Flyer | Esther |
-| Login Screen | Flavius | 
-| Drawing Screen | Flavius | 
-| Register Screen | Flavius | 
-| Forgot Password Screen | Flavius | 
-| Set Up Raspberry Pi | Jouke | 
-| Install Ubuntu | Jouke | 
-| Packaging Solution | Tim | 
-| 3D Case | Tim | 
-| Refining Wiki | Victor | 
-| Temu Case Study | Victor | 
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Register/Forgot Screens. 
-| Backend logic for QR Code, Drawing, Word Breakdown | +  * Packaging Proposal. 
-| Marketing conclusions | +  * Word Doc. 
-| UI designs for multiple screens | +  * Marketing Conclusions. 
-| Login, drawing, registration, forgot password screens | +  * Leaflet, Updated Flyer.
-| Raspberry Pi setup and Ubuntu installation | +
-| Packaging solution | +
-| 3D case prototype | +
-| Updated Wiki | +
-| Temu case study |+
  
-Completion Status: 0 % of tasks completed (All In Progress)+**Completion Status:** 100%
  
-Planned Capacity vs. Achieved Velocity: +**Planned vs. Achieved:** 7/7
-- **Planned**: 18 tasks   +
-- **Achieved**: 0 tasks completed (18 In Progress)+
  
-<WRAP centeralign> 
-<figure Burnup6-figure> 
-{{:sprint_burnup_6.png?600|}} 
-<caption>Burn-up chart sprint 6</caption> 
-</figure> 
-</WRAP> 
  
 +=== Sprint 9 Outcome ===
 +Simulations, documentation refinements.
  
 +**Sprint Backlog:**
 +^ Task ^ Responsible ^
 +| Load and stress simulation | Jouke |
 +| Refine PM Chapter | Victor |
 +| Design Chapter | Esther |
 +| Packaging Solution | Jouke |
 +| Project Development | Jouke |
 +| Project Management | Victor |
 +| User manual | Tim |
 +| Improve Power Budget | Tim |
  
-=== Sprint 7 Outcome === +**Key Deliverables:** 
-Sprint 7 focused on finalizing technical components, refining documentation, and integrating feedback. The sprint successfully completed simulation tasks, UI features, project management documents, sustainability improvements, and physical prototype adjustments.+  * Simulations. 
 +  * Refined Chapters. 
 +  * User Manual. 
 +  * Energy Budget.
  
-Sprint Backlog:+**Completion Status:** 100% 
 + 
 +**Planned vs. Achieved:** 8/8 
 + 
 + 
 +=== Sprint 10 Outcome === 
 +Backend logic, marketing programs, paper chapters. 
 + 
 +**Sprint Backlog:**
 ^ Task ^ Responsible ^ ^ Task ^ Responsible ^
-| Load and stress simulation for 3D model | Jouke | +| Marketing Programmes | Victor | 
-| Drawing Screen | Mateusz | +| Stress tests details | Jouke |
-| Rewrite point 3. Project management | Victor | +
-| Design Part On Wiki | Esther | +
-| Drawing Logic | Mateusz | +
-| Packaging Solution | Jouke | +
-| Chapter 7.4.1 | Jouke |+
 | QR Code Logic | Mateusz | | QR Code Logic | Mateusz |
-| Project management Chapter 3.4, 3.5 and 3.6 | Victor | +| Paper PM | Victor | 
-| Choose proper size of projector for metro stations | Jouke | +| UN SDGs | Victor |
-| Explain in more details stress tests and load tests | Jouke | +
-| Wiki 4.7 | Victor | +
-| Paper for project management | Victor | +
-| Improve UN Sustainable Development Goals | Victor |+
 | Paper chapter 2 | Victor | | Paper chapter 2 | Victor |
-| Add panel for creating new place | Mateusz | +| New Place Panel | Mateusz | 
-| User manual for Ipad case | Tim | +| 3D Model Captions | Tim | 
-| Improve Power Budget And Energy Consumption | Tim | +| PM Chapter Refinement | Tim |
-| 3D Models improvements with captions | Tim |+
  
-Key Deliverables: +**Key Deliverables:** 
-^ Deliverable ^ +  * Programmes. 
-| Load and stress simulation results | +  * Test Docs. 
-| Completed drawing screen | +  * QR Logic. 
-| Updated project management documentation | +  * Paper Docs.
-| Wiki design section completed | +
-| Improved drawing and QR code logic | +
-| Finalized packaging solution | +
-| Projector size decision for metro stations | +
-| Stress and load test documentation | +
-| Paper for project management | +
-| UN SDG improvements | +
-| Completed paper chapters 2, 3, 4.7, 7.4.1 | +
-| UI panel for new place creation | +
-| iPad case user manual | +
-| Power and energy budget improvements | +
-| Enhanced 3D models with captions |+
  
-Completion Status: 100 % of tasks completed (All Done)+**Completion Status:** 100%
  
-Planned Capacity vs. Achieved Velocity: +**Planned vs. Achieved:** 9/9
-- **Planned**: 20 tasks   +
-- **Achieved**: 20 tasks completed (100 % Done)+
  
  
-<WRAP centeralign> +=== Sprint 11 Outcome === 
-<figure Burnup7-figure> +Technical testing and report refinement. 
-{{:sprint_burnup_7.png?600|}} + 
-<caption>Burn-up chart sprint 7</caption> +**Sprint Backlog:** 
-</figure> +^ Task ^ Responsible ^ 
-</WRAP>+| Communication & Risk | Mateusz | 
 +| API Call Tests | Mateusz | 
 +| Multi-user Simulation | Mateusz | 
 +| Refine Design Chapter | Esther | 
 +| Jira Burnups | Tim | 
 +| Sprints Refinement | Tim | 
 +| Quality Chapter | Victor | 
 +| Design Structure | Jouke | 
 +| Stress Sim for Packaging | Jouke | 
 +| Engineering Ethics | Flavius | 
 + 
 +**Key Deliverables:** 
 +  * Reports. 
 +  * Tests. 
 +  * Simulations. 
 + 
 +**Completion Status:** 100% 
 + 
 +**Planned vs. Achieved:** 10/10 
 + 
 + 
 +=== Sprint 12 Outcome === 
 +App build completion, final paper and chapters. 
 + 
 +**Sprint Backlog:** 
 +^ Task ^ Responsible ^ 
 +| App Development | Mateusz | 
 +| Functional Tests | Mateusz | 
 +| People Chapter | Esther | 
 +| Structural Drawings | Tim | 
 +| Assembly Manual | Tim, Jouke | 
 +| Paper | Victor | 
 +| Cost Chapter | Jouke | 
 +| SWOT | Jouke | 
 +| Strategy | Jouke | 
 +| Liability | Flavius | 
 + 
 +**Completion Status:** 100% 
 + 
 +**Planned vs. Achieved:** 10/10 
 + 
 + 
 +=== Sprint 13 Outcome === 
 +Finalising documentation and strategy. 
 + 
 +**Sprint Backlog:** 
 +^ Task ^ Responsible ^ 
 +| Marketing Programmes Feedback | Victor | 
 +| Prototype Chapter | Jouke | 
 +| Procurement | Victor | 
 +| Stakeholder Management | Esther | 
 +| Paper Completion | Victor | 
 + 
 +**Completion Status:** 100% 
 + 
 +**Planned vs. Achieved:** 5/5 
 + 
 + 
 +=== Sprint 14 Outcome === 
 +Final deliverables and clean-up. 
 + 
 +**Sprint Backlog:** 
 +^ Task ^ Responsible ^ 
 +| Marketing Analysis | Flavius | 
 +| Scope Refinement | Flavius | 
 +| Test & Results | Jouke | 
 +| Project Management Chapter | Tim | 
 +| Deliverables List | Everyone | 
 + 
 +**Completion Status:** 100% 
 + 
 +**Planned vs. Achieved:** 5/5 
 + 
 +==== - Sprint Evaluations ====
  
-==== Sprint Evaluations ==== 
 === Sprint 1 Evaluation === === Sprint 1 Evaluation ===
-The first sprint set up the project foundation. The team chose a topic, learned how to use Jira, and attended the introduction sessions. All tasks were finished on time, and the team worked well together during brainstorming.+In the first sprint, the team set up the basics of the project. The topic was chosen, the team learned how to use Jira, and took part in introduction sessions. All tasks were finished on time, and the team worked well together during brainstorming.
  
-This sprint helped define team roles, tools, and work routines for the coming sprints.+This sprint helped the team define their roles, tools, and how they would work together in the future.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Strong team engagement and good collaboration. | +| Positive | Good teamwork and high motivation. | 
-| Negative | Could have spent more time exploring other project ideas. |+| Negative | More time could have been spent looking at different project ideas. |
  
 === Sprint 2 Evaluation === === Sprint 2 Evaluation ===
-In Sprint 2, the team built on the early planning by defining the project’s scope and technical direction. The Blackbox Diagram was completed, the project scope was finalized, and helpful research on similar solutions was done. +In Sprint 2, the team built on the first sprint by defining the project’s scope and technical direction. The Blackbox Diagram was created, the scope was finalized, and research on similar projects was done. The project name was also chosen.
-All planned tasks were completed on time, and choosing the project name helped create a clear identity.+
  
-This sprint showed better task responsibility and communication within the team.+This sprint showed better communication and clearer task responsibilities.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Good teamwork on defining concepts and improving documentation. | +| Positive | Good teamwork on defining the project and updating documents. | 
-| Negative | Should have spent more time on deeper research into existing solutions. |+| Negative | Research into existing solutions could have been more detailed. |
  
 === Sprint 3 Evaluation === === Sprint 3 Evaluation ===
-Sprint 3 focused on technical tasks and research. A 3D model was created, and important research on sustainability, ethics, and marketing was finished. The materials cost analysis and updated research review added useful details to the project.+Sprint 3 focused on both technical work and research. A first 3D model was made, and important topics like sustainability, ethics, and marketing were covered. Material costs were also reviewed.
  
-The team completed all tasks and successfully balanced technical work with research.+The team handled both technical and research tasks well.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Reliable task completion and a good balance between technical and research work. | +| Positive | Reliable task completion and a good mix of technical and research work. | 
-| Negative | Sustainability and marketing reports lacked enough detail. |+| Negative | Some reports lacked enough detail, especially in sustainability and marketing. |
  
 === Sprint 4 Evaluation === === Sprint 4 Evaluation ===
-This sprint was important for project structure and documentation. Key deliverables like schematics, engineering backlogs, and updated project documents were completed. Promotional materials, including a flyer and Gantt chart updates, were handled effectively.+In this sprint, the team worked on organizing important project documents and deliverables. Tasks included creating schematics, engineering backlogs, updating the project scope, and making promotional materials.
  
-The team was highly productive, and tasks were divided well, although the number of deliverables risked putting too much pressure on some members.+The sprint was productive, but some team members had too many tasks.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Fast task delivery and improved project documents. | +| Positive | Fast task completion and better organized documents. | 
-| Negative | Should improve task prioritization and streamline chart updates. |+| Negative | Task planning could be improved to avoid overloading some team members. |
  
 === Sprint 5 Evaluation === === Sprint 5 Evaluation ===
-Sprint 5 focused on improving existing work and getting ready for implementation. The final Blackbox design, materials list, and software/hardware backlogs were completed. User interaction documents were also finished. +Sprint 5 focused on improving previous work and preparing for implementation. The final Blackbox design, materials list, and software/hardware plans were completed. User interaction documents were also finished.
-Once again, 100% of tasks were completed, showing strong organization and teamwork.+
  
-This sprint successfully moved the project toward the implementation stage.+The team was well-organized and completed all tasks on time.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Good preparation for technical prototyping and clear, updated documentation. | +| Positive | Good preparation for technical development and clear documentation. | 
-| Negative | Hardware choices took longer than planned. |+| Negative | Deciding on hardware options took longer than expected. |
  
 === Sprint 6 Evaluation === === Sprint 6 Evaluation ===
-The team began prototype development with login and registration logic, UI design, and hardware setup. Tasks remained “In Progress,” showing a slight drop in task closure compared to earlier sprints.+In this sprint, the team started prototype development. Login and registration logic, UI designs, and hardware setup began. Some tasks stayed “In Progress,” and the team noticed a drop in the number of finished tasks compared to earlier sprints.
  
-This sprint revealed growing technical challenges and highlighted areas that need closer attention going forward.+This sprint showed where technical challenges were starting to appear.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Promising start to technical implementation. | +| Positive | Good start on technical implementation. | 
-| Negative | Sprint was too ambitious, too many tasks at once and underestimated effort. |+| Negative | The sprint was too ambitious with too many tasks at once. |
  
 === Sprint 7 Evaluation === === Sprint 7 Evaluation ===
-This sprint marked a productive milestone with the successful closure of all planned tasks, addressing earlier technical challenges and documentation gaps.+This sprint was a positive step forward. All planned tasks were completed, including UI development, flyer adjustments, and prototype improvements. 
 + 
 +The team managed to solve earlier technical problems and improve documentation.
  
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| Positive | Full completion of planned tasks and notable progress in documentation, technical refinement, and prototype enhancement. | +| Positive | All tasks finished and visible technical progress. | 
-| Negative | Some tasks required extra iterations to meet quality expectations, highlighting a need for early validation. | +| Negative | Some tasks needed extra adjustments before meeting the expected quality. |
-==== - Summary ====+
  
-This chapter gave an overview of how the DrawYourWay project is organized and managed. It covered all important aspects of project management, including the scope, timeline, cost estimation, quality control, team roles, communication tools, and risk management. Weekly sprints and evaluations helped the team stay aligned, adjust when needed, and make sure tasks are completed on time.+=== Sprint 8 Evaluation === 
 +Sprint 8 focused on refining the software, packaging ideas, and promotional materials. New app screens were created, and work on the leaflet and flyer continued.
  
-Stakeholders were also identified and the necessary resources and tools for both hardware and software development were outlined. By following a clear project plan and using agile methods, the team made steady progress toward a working and sustainable prototype.+Task management improved, and team communication was clear. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Balanced progress in software, packaging, and marketing work. | 
 +| Negative | Packaging ideas needed clearer technical descriptions. | 
 + 
 +=== Sprint 9 Evaluation === 
 +This sprint involved technical improvements with simulations, testing, and packaging trials. The team also worked on the user manual and energy optimization. 
 + 
 +Most tasks were completed, though some needed extra time. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Steady technical progress and improved reports. | 
 +| Negative | A few tasks were delayed because of unexpected challenges. | 
 + 
 +=== Sprint 10 Evaluation === 
 +In Sprint 10, the team focused on final technical documentation, software improvements, and stress test explanations. Updates to the 3D model and paper writing also took place. 
 + 
 +Even with a heavy workload, the team kept up good productivity. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Strong task completion and good final improvements. | 
 +| Negative | Some paper sections needed extra changes after feedback. | 
 + 
 +=== Sprint 11 Evaluation === 
 +Sprint 11 was about final tests and fixing documents based on feedback. API testing, multi-user tests, risk management updates, and chapter revisions were done. 
 + 
 +Task tracking improved, and work was completed smoothly. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Quick issue-solving and helpful report updates. | 
 +| Negative | Several documents required last-minute adjustments. | 
 + 
 +=== Sprint 12 Evaluation === 
 +This sprint finalized app development, testing, and user guidelines. Cost review and strategic documents were also finished. 
 + 
 +The team worked well together, and nearly all tasks were completed on time. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Good balance between technical work and reporting. | 
 +| Negative | Some documents, like SWOT and liability analysis, took more time than planned. | 
 + 
 +=== Sprint 13 Evaluation === 
 +Sprint 13 focused on polishing marketing materials, project management, and prototype documents. Tasks included procurement, stakeholder review, and final paper improvements. 
 + 
 +Though the workload was high, it was handled efficiently. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | Good updates to reports and promotional materials. | 
 +| Negative | Some project management tasks extended beyond deadlines. | 
 + 
 +=== Sprint 14 Evaluation === 
 +The final sprint completed marketing analysis, final paper edits, test result reviews, and deliverable packaging. The team made sure everything was ready for final submission. 
 + 
 +It was a strong and organized finish to the project. 
 + 
 +^ Aspect ^ Reflection ^ 
 +| Positive | All tasks finished and final deliverables well prepared. | 
 +| Negative | A few tasks could have been completed earlier with better scheduling. | 
 + 
 +==== - Summary ==== 
 +This chapter explained how the DrawYourWay project was organized and managed. It covered the main project management topics like scope, scheduling, cost estimates, quality checks, team roles, tools, and risk management. Weekly sprints and evaluations helped the team stay organized, make adjustments when needed, and complete tasks on time.
  
-With the technical planning and organization now well-structured, the next step is to focus on how DrawYourWay will reach the public. In the next chapter, the Marketing Plan will explore how to promote the project to both users and potential buyers.+Stakeholders were identified, and the necessary tools and resources for hardware and software development were planned. By following an agile method and a clear project plan, the team made steady progress and reached a working, sustainable prototype.
  
 +With the technical planning and organization now finished, the next chapter will focus on how DrawYourWay will be introduced to the public through the Marketing Plan.
  
  
Line 1553: Line 1665:
  
 **Price** **Price**
-Participation in DrawYourWay is free. The choice was made to make participation free so that it is and remains attractive for users. For the financing of the project and the rewards, we will work together with companies. Companies can promote their brand on the platform. In exchange for promoting their brand, they sponsor the rewards or the necessary hardware.+Participation in DrawYourWay is free. It was decided to make participation free, so that it is and remains attractive for users. To finance the project, DrawYourWay will be sold for 5999.99 euros to waiting station for public transport. This price was created by doing the price of the Component/Material about 5 times. In this way, the labor cost can also be recovered in the long term. We work together with companies for the rewards. Companies can promote their brand on the platform. In exchange for promoting their brand, they sponsor the rewards for the daily/weekly winners.
  
 **Place** **Place**
Line 2258: Line 2370:
 {{:step_up_box.png?800|}} {{:step_up_box.png?800|}}
 <caption>step up box.</caption> <caption>step up box.</caption>
 +</figure>
 +</WRAP>
 +
 +<WRAP centeralign>
 +<figure fig-ss>
 +{{ ::childonstepupbox.png?600 |}}
 +<caption>Visualization of a child standing on a step up box.</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 2374: Line 2493:
  
 === - Tests & Results === === - Tests & Results ===
 +
 +** Test environment **
 +
 +The tests were conducted on a computer located in the ISEP classroom. This machine simultaneously served as both the frontend and backend server for the users. Its specifications were as follows: a 3.2 GHz Intel Pentium G3250 processor, 4 GB of RAM, and Windows 10 as the operating system.
  
 === Hardware tests === === Hardware tests ===
Line 2449: Line 2572:
        
 ==== - Summary ==== ==== - Summary ====
-The DrawYourWay project is an interactive public art platform aimed at transforming idle commuter time in metro stations into moments of creativity and engagement. It enables users to create digital drawings using their own mobile devices or tablets and project them onto large public walls in real-time, encouraging public participation and community interaction. The idea stemmed from the team’s shared interest in digital art and was developed through collaborative brainstorming and design thinking sessions.+During the development of the prototype, several adjustments were made compared to the original design to simplify the process and stay within the available budget, while still ensuring that the core functionalities could be demonstrated. 
 + 
 +Regarding the structure, some practical decisions were taken. The protective case for the projector was not produced, as it was not essential for showing the system’s operation during testing. Additionally, modifications were made to the tablet’s protective case: instead of using ABS, PLA was used. While PLA has lower mechanical and chemical resistance, it was a good alternative for the prototyping phase. Furthermore, the prototype version of the tablet case excluded holes for wall and table mounting, cable openings, and clamps since these were unnecessary for this stage. To speed up production, the case was printed in two parts and then glued together, which slightly reduced the quality of the finish but made the process more efficient.
  
-Technologically, the platform integrates QR code interaction, drawing tools, and a projection system managed by a backend built with Django and React, forming a Progressive Web App (PWA) accessible on both desktop and mobile. The hardware setup includes second-hand tablets and energy-efficient laser projectors, ensuring cost-effectiveness and sustainability. A Raspberry Pi manages user input, connectivity, and projection, with a total power consumption of 123W and estimated annual cost of €160.+In terms of hardware, two main changes were implemented to remain within the €100 budget. An old projector was repurposed instead of acquiring a new one, and an old PC was used in place of the originally planned Raspberry Pi. These substitutions did not affect the testing of the main functionalities but did limit the scope of some hardware-specific tests.
  
-Sustainability plays a major role in the project. Environmentally, recycled and biodegradable material as plywood are used, economically, second-hand and locally sourced equipment keeps costs low and socially, the project promotes inclusivity, creativity, and community well-being. Ethical and deontological principles guide decisions around honest communication, environmental care, and content moderation.+The software for the prototype was built using Django for the backend and React for the frontend, resulting in a Progressive Web App (PWA). which makes the system accessible via both web browsers and mobile devices. The prototype’s software features included user login and registration, the ability to draw drawings, a drawing interface, and QR code scanning functionality to link specific locations with relevant drawings.
  
-The packaging was designed with dual functionality: a sturdy plywood step-up box for transporting and then supporting tablet use, and a stainless steel projector case that ensures durability and reusability. During prototyping, budget-friendly changes were made, including using PLA instead of ABS and repurposing old hardware.+Both hardware and software underwent a series of tests to evaluate the performance. Hardware tests were conducted in a metro station environment to assess real-world functionality. Of the nine tests, the prototype successfully passed Functionality Testing, Real-Time Display Test, User Experience Testing, Connectivity Test, and Hardware Durability Test. Theme Rotation and Moderation Tests were not completed due to time constraints and development priorities. Energy Consumption and Maintenance & Support Tests could not be performed effectively because the alternative hardware used in the prototype would not have provided representative results for the final product.
  
-Testing validated several key features such as functionality, user experience, connectivity, and hardware durability. However, limitations in time and equipment meant that theme rotation, content moderation, energy use monitoring, and long-term maintenance were not fully realized. Nonetheless, the project presents a promising, scalable, and socially engaging solution for urban environments.+Software testing included a detailed analysis of system request statistics and response times, confirming stable and reliable performance for the implemented functionalities. A full report detailing these results was compiled and made available for reference.
  
 +In conclusion, the prototype successfully demonstrated the core concept and main functions of the DrawYourWay system, providing valuable insights for future iterations and development phases.
  
 ===== - Conclusions ===== ===== - Conclusions =====
  • report.1750093262.txt.gz
  • Last modified: 2025/06/16 18:01
  • by team2