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/03 11:43] – [Sprint Evaluations] team2report:prm [2026/06/14 22:40] (current) – [Sprint 5] team2
Line 15: Line 15:
 **3.2 Time** **3.2 Time**
  
-In this section, we lay out the schedule and all the major deadlines we have to hit throughout the semester. this is shown in Table {{ref>tab:milestones}}. Tracking these milestones is really important because it keeps the whole team accountable and makes sure we're actually making steady progress on Bloem. It also helps us see if we're falling behind early on, so we can fix things before they become a real problem.+In this section, we lay out the schedule and all the major deadlines we have to hit throughout the semester. This is shown in Table {{ref>tab:milestones}}. Tracking these milestones is really important because it keeps the whole team accountable and makes sure we're actually making steady progress on Bloem. It also helps us see if we're falling behind early on, so we can fix things before they become a real problem.
  
 <WRAP 80%> <WRAP 80%>
Line 94: Line 94:
 ==== Quality ==== ==== Quality ====
  
-For the Bloem project, quality is about more than just building a nice-looking capsule. It is divided into two main areas: how well the physical product performs and how clear and professional our documentation is.+For the Bloem project, quality management ensures that both the final deliverable meets high engineering standards and the development process itself is efficient and reliable. Therefore, we define and monitor quality across two primary domains: the physical product and the project execution.
  
-**Bloem Product Quality**+**Product Quality (Physical Performance & Specifications)**
  
-The quality metrics for the physical prototype are focused on three main points:+The physical prototype of the Bloem capsule must adhere to strict technical and structural specifications to ensure a safe and relaxing user experience. Quality in this domain is evaluated based on the following explicit material and functional requirements:
  
-  * **Durability and Materials:** The structure must pass load and stress simulations to ensure the egg-shaped design is stable. We are using sustainable materials like cork and hemp, which need to be high quality to ensure the capsule lasts. +  * **Resilience and Durability:** The structure must withstand daily entry, exit, and usage. The sustainable materials selected (cork and hemp insulation) must not easily degrade, warp, or tear under normal indoor environmental conditions. 
-  * **Functionality:** Every feature we planned, like the sensor integration and the tablet interface, must work perfectly. The user needs to have a smooth experience when controlling the environment inside. +
-  * **Environmental Impact:** To keep our footprint low, we are sourcing materials as locally as possible and focusing on a "circular" design that uses bio-based components.+
  
 +  * **Weight Load Capacity:** The structural frame and base must safely hold specified weight loads. The seating area is designed to support a user weighing up to 150 kg without any structural deformation or stress fractures.
 +  * **Dimensional Tolerance:** Precision in assembly is critical to maintaining the egg-shaped geometry. The overall structural dimensions have an acceptable tolerance of ±2.0 cm. For connecting joints and the sliding door track, the tolerance is restricted to ±0.5 cm to ensure smooth, friction-less operation.
 +  * **System Functionality:** Every smart feature—including the ESP32 sensor integration, lighting, and tablet interface—must operate seamlessly. The user must experience low-latency responses when controlling the internal environment.
 +  * **Environmental Impact:** The product must utilize locally sourced, bio-based materials to maintain a low carbon footprint and adhere to a circular design philosophy.
  
-**Documentation Quality** 
  
-To make sure our report and wiki are easy for the supervisors and other students to follow, we follow these rules:+**Project Quality (Process Quality & Delivery Reliability)**
  
-  * **Consistency:** All sections use the same font styles, sizes, and structure. Whether it's the IT part or the Marketing part, it should feel like one single project. +To guarantee a successful and professional outcome, we apply strict quality standards to our teamwork, workflow, and documentation.
-  * **Clarity:** We avoid over-complicating the language. We use technical terms when necessary, but we try to keep the explanations direct and easy to read. +
-  * **Visual Appeal:** Every page and document must include the ISEP logo and our Bloem project logo following the color scheme we chose for the brand.+
  
 +  * **Process Quality:** High process quality means accurately estimating our effort breakdowns, completing planned sprint tasks with carrying them over only rarely and ensuring clear communication across our team.
 +  * **Delivery Reliability:** All project milestones—such as the Interim Report, Final Presentation, and Prototype Assembly—must be delivered fully complete and strictly on time. 
  
 +  * **Documentation Standards:** All reports and wiki pages must maintain consistent formatting. Explanations must be direct and easy to read and all documents must feature the ISEP and Bloem brand logos using the established color palette.
  
-==== People & Stakeholder Management ==== 
-**3.5 People** 
  
-At the start of the project, we talked about our different backgrounds and what each of us is good at. This helped us figure out who would take the lead on things like the technical system or the structural design. However, we decided right away that these roles wouldn't be fixed. Since Bloem is a project where everything—from the sensors to the physical shell—has to work together, we stay flexible. If one person has a huge workload or gets stuck on a specific task, the rest of the team jumps in to help, regardless of our "official" focus.+**Quality Control Table**
  
-We meet every week for our sprint planning to go over what we’ve done and what’s coming up next. These meetings are key for us to stay aligned and to move people around to different tasks depending on what needs the most attention that week. It keeps the project moving forward and makes sure no one is overwhelmed.+To systematically verify these requirements during the assembly and testing phases, we use the following quality control matrix.
  
-The supervising teachers also play a huge role in the project. They don't just grade us; they act as guides who give us feedback when our ideas get too complicated or when we're not sure how to solve a technical problem. Their input helps us keep the "big picture" in mind and ensures that Bloem is actually realistic and buildable.+<WRAP 100%> 
 +<table tab:quality_control> 
 +<caption>Bloem Quality Control Matrix</caption> 
 +^ What is observed/checked ^ Acceptance Criterion ^ Allowed Deviation Range ^ 
 +| **Overall Structure Dimensions** | Matches the 3D CAD model specifications | ± 2.0 cm | 
 +| **Joint / Door Alignment** | Sliding door opens and closes smoothly | ± 0.5 cm | 
 +| **Structural Load / Weight** | Base and seating safely support a user | Max 150 kg (No lower deviation allowed for safety) | 
 +| **Material Finish** | Cork and hemp panels are securely glued; no peeling | ± 2.0 mm gap tolerance | 
 +| **App-to-Hardware Latency** | LEDs and music change state upon app input | < 100 ms | 
 +</table> 
 +</WRAP>
  
-Even though we don't have strict individual roles, we still track our main stakeholders to understand who is involved in the project's success. An overview is seen in Table {{ref>tab:stakeholders}}.  +**3.5 People and Stakeholder Management** 
-  + 
-<WRAP 80%> +At the beginning of the project the team assessed its academic backgrounds to establish initial leads for technical and structural domains. However, recognizing the highly integrated nature of the Bloem capsule, the team adopted a flexible operational model. Resource allocation is adjusted during weekly sprint planning and meetings to ensure a balanced workload.  
-<table tab:stakeholders> + 
-<caption>Project Stakeholders</caption> +Beyond the internal team, external stakeholders play a crucial role in the project's viability. To manage these relationships effectively, a structured stakeholder classification model is used, analyzing the following dimensions: 
-^ Stakeholder ^ Role ^ Description ^ +  * **Power vs. Influence:** It is vital to distinguish between decision authority and the ability to affect outcomes. **Power** refers to formal authority (e.g., grading, funding approval, administrative sign-off), whereas **Influence** dictates how much a stakeholder can steer the project's success through technical advice, resources, or feedback.  
-| **Team Bloem** | Owners | The core group responsible for the design, build, and management. | +  * **Type of Influence and Impact:** Each stakeholder is evaluated on their level of influence (Low, Medium, or High) and their impact—meaning how strongly they are personally or professionally affected by the project's outcome. 
-| **Benedita Malheiro** | EPS Coordinator | Overall management and organization of the EPS program. | +  * **Level of Support:** Stakeholders are categorized by their stance: **Supporter** (actively aids the project), **Neutral** (neither helps nor hinders), **Blocker** (potential source of delay, such as supply chain bottlenecks), or **Decision-Maker** (holds the ultimate authority on project progression). 
-| **Project Supervisors** | Advisors | Providing technical advice and feedback to guide the development. | + 
-| **ISEP** | Main Sponsor | Providing the tools, workspace, and funding for the prototype. | +Table {{ref>tab:stakeholder_classification}} outlines this classification for the Bloem project. 
-| **Office Workers** | Target Group | The end-users who provide the need and feedback for the capsule. | + 
-| **Suppliers** | Partners | External providers for our cork, hemp, and electronics. |+<WRAP 100%> 
 +<table tab:stakeholder_classification> 
 +<caption>Stakeholder Classification Matrix</caption> 
 +^ Stakeholder ^ Description ^ Power ^ Influence ^ Impact ^ Level of Support ^ 
 +| **Team Bloem** | Core group responsible for the design and build. | Medium | High | High | Supporter | 
 +| **Project Supervisors** | Advisors providing technical and academic guidance. | High | High | Medium | Decision-Maker / Supporter | 
 +| **Benedita Malheiro** | EPS Coordinator managing the program structure. | High | Medium | Low | Decision-Maker | 
 +| **ISEP** | Main sponsor providing workspace and funding. | High | High | Low | Supporter | 
 +| **Office Workers** | End-users providing needs and UX feedback. | Low | Medium | High | Neutral / Supporter | 
 +| **Suppliers** | External providers for cork, hemp, and electronics. | Low | Medium | Low | Neutral / Blocker (if delayed) |
 </table> </table>
 </WRAP> </WRAP>
-==== Communications ====+ 
 +**Stakeholder Communication Strategy** 
 + 
 +To ensure each stakeholder receives the appropriate information without being overwhelmed, communication is tailored based on their classification: 
 + 
 +  * **Internal Team (Team Bloem):**  
 +    * *How:* WhatsApp for rapid alignment, MS Teams for documentation. 
 +    * *Frequency:* Daily. 
 +    * *Detail Level:* Extremely detailed and highly technical. 
 + 
 +  * **Project Supervisors & EPS Coordinator:** 
 +    * *How:* In-person meetings, MS Teams and email. 
 +    * *Frequency:* Weekly. 
 +    * *Detail Level:* Medium to high. Focuses on progress overviews, milestone achievements, and specific technical or ethical obstacles. 
 + 
 +  * **Target Group (Office Workers):** 
 +    * *How:* Surveys, interviews, and prototype testing sessions. 
 +    * *Frequency:* Phase-based (Research and Testing phases). 
 +    * *Detail Level:* High-level, focusing entirely on user experience, ergonomics, and functional feedback rather than technical mechanics. 
 + 
 +  * **Suppliers:** 
 +    * *How:* Email and direct phone calls. 
 +    * *Frequency:* As needed during the procurement phase. 
 +    * *Detail Level:* Highly specific regarding material specifications, dimensional tolerances, quantities, and delivery timelines. 
 + 
 **3.6 Communications** **3.6 Communications**
  
-Staying in sync is the only way we can manage all the different parts of Bloem. To keep things moving, we use a few specific tools to stay connected. Daily talk happens on **WhatsApp**, where we coordinate quickly or ask for help if someone gets stuck. For the official side, we use **Microsoft Teams** to store our report drafts and all project files. We also rely on **Jira** to manage our weekly sprints, which helps everyone see exactly what needs to be done and who is working on what.+Effective synchronization is essential to manage all components of the Bloem project. To maintain progress, the team utilizes specific tools to stay connected. Daily communication occurs via **WhatsApp**, facilitating quick coordination and immediate problem-solving when issues arise. For formal documentation, **Microsoft Teams** serves as the central repository for report drafts and all project files. Additionally, the team relies on **Jira** to manage weekly sprints, providing clear visibility into task assignments and current project status.
  
-We meet in person during class hours several times a week.+**Information Flow** 
 +To ensure organized and professional communication, project information is distributed strictly according to stakeholder relevance: 
 +  * **Internal Team:** Receives raw data, design drafts, daily task updates, and internal meeting minutes. 
 +  * **Project Supervisors & EPS coordinator** Receive weekly progress summaries, milestone deliverables and formal technical/academic questions.
  
-Table {{ref>tab:communication}} shows the actual communication channels we use for the project.+Table {{ref>tab:communication}} shows the general communication channels established for interactions with these stakeholders.
  
 <WRAP 80%> <WRAP 80%>
 <table tab:communication> <table tab:communication>
-<caption>Communication Channels and Purpose</caption>+<caption>Communication Channels and Stakeholders</caption>
 ^ Stakeholder ^ Channel ^ Frequency ^ Purpose ^ ^ Stakeholder ^ Channel ^ Frequency ^ Purpose ^
-| **Team Bloem** | WhatsApp, Teams & In-person | Daily / Whenever necessary | Quick updates, file sharing, and sprint planning. | +| **Team Bloem** | WhatsApp, Teams & In-person | Daily / As needed | Quick updates, file sharing, and internal coordination. | 
-| **Project Supervisors & EPS Coordinator** | MS Teams & In-person | Weekly | Presenting our progress and getting feedback on the work. | +| **Project Supervisors** | MS Teams & In-person | Weekly | Presenting progress and receiving feedback on the work. |
-| **ISEP** | Email & MS Teams | As needed | Official university updates and program management. | +
-| **Suppliers / Customers** | - | - | N/A (Internal university project). |+
 </table> </table>
 </WRAP> </WRAP>
  
-By sticking to these channels, we make sure we don't lose any information and that everyone stays on the same page as we move toward the final build.+To structure the workflow, specific recurring meetings have been established. Table {{ref>tab:meetings}} outlines the formal meeting schedule.
  
 +<WRAP 100%>
 +<table tab:meetings>
 +<caption>Project Meetings Overview</caption>
 +^ Type of Meeting ^ Who (Participants) ^ What (Purpose) ^ When / Frequency ^ Communication Channel ^
 +| **Daily Sync** | Team Bloem | Quick status updates, identifying immediate blockers. | Daily | WhatsApp |
 +| **Sprint Planning** | Team Bloem | Reviewing completed work and assigning Jira tasks. | Weekly | In-person |
 +| **Supervisor Meeting** | Team Bloem & Supervisor Panel | Presenting weekly progress, discussing milestones, and addressing specific technical or ethical domain questions. | Weekly | In-person / MS Teams |
 +| **Working Sessions** | Team Bloem | Active physical prototype development and software integration. | Multiple times a week | In-person |
 +</table>
 +</WRAP>
 +
 +**Issue Escalation Protocol**
 +When challenges or technical blockers arise, the team follows a defined escalation path to resolve issues efficiently and prevent project delays:
 +  - **Level 1 (Internal Resolution):** The issue is first raised via WhatsApp or during a daily working session. The multidisciplinary team attempts to troubleshoot and resolve it internally within 24 to 48 hours.
 +  - **Level 2 (Supervisor Escalation):** If the issue persists, requires specific academic guidance, or impacts the budget, it is documented and formally brought to the relevant Project Supervisor (e.g., addressing structural questions to the mechanics supervisor or UI questions to the IT supervisor) during the weekly meeting.
 ==== Risk ==== ==== Risk ====
 **3.7 Risk Management** **3.7 Risk Management**
Line 224: Line 284:
 For the user interface, the team selected a commercial tablet that offers sufficient performance for session booking and environmental control without requiring advanced specifications. This avoids overspending on hardware while still ensuring that the interface can be demonstrated under realistic conditions. For the user interface, the team selected a commercial tablet that offers sufficient performance for session booking and environmental control without requiring advanced specifications. This avoids overspending on hardware while still ensuring that the interface can be demonstrated under realistic conditions.
  
-Overall, the procurement strategy for Bloem is based on using reliable suppliers for large structural materials, specialized vendors for electronics, and alternative sources whenever delivery or stock issues may arise. This mixed approach provides flexibility during implementation and supports both the physical construction of the capsule and the integration of its interactive features.+Overall, the procurement strategy for Bloem is based on using reliable suppliers for large structural materials, specialized vendors for electronics and alternative sources whenever delivery or stock issues may arise. This mixed approach provides flexibility during implementation and supports both the physical construction of the capsule and the integration of its interactive features.
  
 <WRAP 80%> <WRAP 80%>
 <table tab:procurement> <table tab:procurement>
-<caption>Procurement Plan </caption>+<caption>Procurement Plan</caption> 
 + 
 +^ Item ^ Primary Supplier ^ Primary Price ^ Primary Shipping (Days) ^ Backup Supplier ^ Backup Price ^ Shipping Time (Days) ^ Notes ^ 
 +| Cork insulation GO4CORK | Leroy Merlin | 317.79 € | 1–3 | Casa Peixoto | 362.70 € | 1–3 | Main acoustic and thermal insulation material | 
 +| Planed wooden slat WHITE CASQUINHA | Leroy Merlin | 65.44 € | 1–3 | Casa Peixoto | 95.85 € | 0–2 | Used for internal wooden framing | 
 +| SPAX Screws | KuantoKusta | 5.69 € | 1–3 | Leroy Merlin | 18.99 € | 0–2 | Fastening elements | 
 +| Hemp Granules 15 | Datapixel | 255.69 € | 2–5 | Leroy Merlin | 279.72 € | 1–3 | Complementary insulation material | 
 +| Plywood Interior Poplar B/BB | ToSize | 291.30 € | 3–7 | Maderterraneo | 390.00 € | 2–5 | Main shell material | 
 +| Wide Square k2 L-brackets | Leroy Merlin | 2.58 € | 1–3 | Macovex | 6.00 € | 0–2 | Structural reinforcement | 
 +| Pattex Wood Glue | Worten | 6.96 € | 0–2 | Leroy Merlin | 36.85 € | 0–2 | Wood adhesive | 
 +| Birch plywood board (floor) | Madeiras Leiria | 117.62 € | 1–3 | Madeiras Leiria | 235.24 € | 1–3 | Flooring base | 
 +| Plywood Poplar (door) | Maderterraneo | 90.00 € | 2–5 | ToSize | 97.10 € | 2–5 | Sliding door panel | 
 +| Birch plywood board (seat frame) | Madeiras Leiria | 117.62 € | 1–3 | Leroy Merlin | 429.00 € | 1–3 | Seating structure | 
 +| Tablet holder | Worten | 88.71 € | 0–2 | Manutan | 114.08 € | — | Mounting system | 
 +| Soft seating pillowcase | Texland | 80.16 € | 1–3 | Loja Tecidos | 117.00 € | 1–3 | Upholstery fabric | 
 +| Cushion filling material | 100metros | 116.16 € | 1–3 | Feira dos Tecidos | 83.40 € | — | Foam filling | 
 +| Hinges Door | Leroy Merlin | 65.94 € | 1–3 | Fruugo | 179.70 € | 1–3 | Door hinges | 
 +| Outside panels (PLA) | Evolt | 209.55 € | 2–5 | Reprap | 240.00 € | — | Exterior panels | 
 +| Galaxy Tab A9 | Worten | 159.00 € | 0–2 | Staples | 200.00 € | 0–2 | Interface device | 
 +| ESP32-S3 board | Mauser | 13.90 € | 5–10 | Mauser | 10.14 € | 5–10 | Controller | 
 +| RGB LED strip | Worten | 16.00 € | 1–3 | Botnroll | 12.50 € | 1–3 | Lighting | 
 +| MOSFET transistor | Worten | 17.90 € | 1–3 | Mauser | 11.40 € | 1–3 | Switching | 
 +| Resistor set | Worten | 11.85 € | 1–3 | Mauser | 50.00 € | 1–3 | Electrical support | 
 +| Red/Black Column Wire | Mauser | 3.51 € | 2–5 | DigiKey | 3.50 € | 5–10 | Electrical support | 
 +| BH1750 sensor | DigiKey | 4.00 € | 5–10 | Mauser | 5.50 € | 5–10 | Light sensing | 
 +| LM2596 converter | Mauser | 5.72 € | 5–10 | DigiKey | 20.22 € | 5–10 | Power regulation | 
 +| 12V power supply | Mauser | 10.50 € | 5–10 | Thomann | 20.90 € | 5–10 | Power supply | 
 +| Speaker GAT-801 | Mauser | 28.91 € | 2–5 | KuantoKusta | 39.67 € | 1–3 | Audio output | 
 +|**Total Estimated Cost** | | **2539.99 €** | | | **2786.73 €** |
  
-^ Item ^ Primary Supplier ^ Backup Supplier ^  Estimated Cost ^ Lead Time (Days) ^ Shipping Time (Days) ^ Notes ^ 
-| Cork insulation GO4CORK | Leroy Merlin | Casa Peixoto |  362.70 € | 2–5 | 1–3 | Main acoustic and thermal insulation material | 
-| Planed wooden slat WHITE CASQUINHA | Leroy Merlin | Casa Peixoto |  95,85 € | 1–3 | 0–2 | Used for internal wooden framing | 
-| SPAX Screws | KuantoKusta | Leroy Merlin |  18.99 € | 1–3 | 0–2 | Fastening elements | 
-| Hemp Granules 15 | Datapixel | Leroy Merlin |  279.72 € | 2–5 | 1–3 | Complementary insulation material | 
-| Plywood Interior Poplar B/BB | ToSize | Maderterraneo |  390.00 € | 3–7 | 2–5 | Main shell material | 
-| Wide Square k2 L-brackets | Leroy Merlin | Macovex |  6.00 € | 1–3 | 0–2 | Structural reinforcement | 
-| Pattex Wood Glue | Worten | Leroy Merlin |  36.85 € | 1–3 | 0–2 | Wood adhesive | 
-| Birch plywood board (floor) | Madeiras Leiria | Madeiras Leiria |  235.24 € | 2–5 | 1–3 | Flooring base | 
-| Plywood Poplar (door) | Maderterraneo | ToSize |  97.10 € | 3–7 | 2–5 | Sliding door panel | 
-| Birch plywood board (seat frame) | Madeiras Leiria | Leroy Merlin |  429.00€ | 2–5 | 1–3 | Seating structure | 
-| Tablet holder | Worten | Manutan |  114.08 € | — | — | Mounting system | 
-| Soft seating pillowcase | Texland | Loja Tecidos |  117.00 € | 1–3 | 1–3 | Upholstery fabric | 
-| Cushion filling material | 100metros | Feira dos Tecidos |  83.40 € | — | — | Foam filling | 
-| Hinges Door | Leroy Merlin | Fruugo |  179.70 € | 1–3 | 1–3 | Door hinges | 
-| Outside panels (PLA) | Evolt | Reprap |  240.00 € | — | — | Exterior panels | 
-| Galaxy Tab A9 | Worten | Staples |  200.00 € | 1–2 | 0–2 | Interface device | 
-| ESP32-S3 board | Mauser | Mauser |  10.14 € | 2–5 | 5–10 | Controller | 
-| RGB LED strip | Worten | Botnroll |  12.50 € | 1–3 | 1–3 | Lighting | 
-| MOSFET transistor | Worten | Mauser |  11.40 € | 1–3 | 1–3 | Switching | 
-| Resistor set | Worten | Mauser |  50.00 € | 1–3 | 1–3 | Electrical support | 
-| Red/Black Column Wire | Mauser | DigiKey |  3.50 € | 2–5 | 5–10 | Electrical support | 
-| BH1750 sensor | DigiKey | Mauser |  5.50 € | 2–5 | 5–10 | Light sensing | 
-| LM2596 converter | Mauser | DigiKey |  20.22 € | 2–5 | 5–10 | Power regulation | 
-| 12V power supply | Mauser | Thomann |  20.90 € | 2–5 | 5–10 | Power supply | 
-| Speaker GAT-801 | Mauser | KuantoKusta | 39.67 € | 1–3 | 1–3 | Audio output | 
-|**Total Estimated Cost** | | |  **2786.73 €** |  
 </table> </table>
 </WRAP> </WRAP>
 +
 +Procurement presents significant risks in three areas: price fluctuations, delivery times, and supplier dependencies. There are sometimes substantial price differences between primary and backup suppliers that cannot be explained solely by market variations but are usually attributable to differences in packaging sizes, quality grades, or distribution channels (retail vs. B2B). Particularly notable are wood and fastening materials such as wood glue, hinges, screw sets, and individual wood panels, where prices vary by a factor of approximately 2 to 5 depending on the supplier. This creates a procurement risk, as actual unit costs depend heavily on the chosen supplier and are not consistently comparable across all sources.
 +
 +In terms of time, the system is clearly segmented: local retailers such as Leroy Merlin or Worten typically deliver within 0–3 days, while specialized dealers for wood or material products tend to require 2–5 days. Electronics components sourced through distributors like Mauser or DigiKey, on the other hand, have the longest shipping times of up to 5–10 days. This creates a critical path in project planning, as microcontrollers, sensors and power components in particular can delay the entire system integration if they are not available on time.
 +
 +Another risk stems from de facto single-supplier structures. Some components either have identical primary and backup suppliers or have only very limited interchangeable alternatives. This increases dependence on individual distributors and makes the system vulnerable to stockouts or delivery delays, particularly in the electronics sector.
 +
 +This results in a clear procurement strategy with two modes: Under normal circumstances, the cheapest supplier is selected to minimize total costs. In time-critical phases or when bottlenecks are imminent, however, the system deliberately switches to the fastest available supplier, even if this results in higher costs. This dual strategy strikes a balance between budget efficiency and project security while reducing the risk of delays on the critical path.
  
  
Line 325: Line 394:
 | 2 | "Black box" System Diagrams | 3 | Everyone | Everyone | | 2 | "Black box" System Diagrams | 3 | Everyone | Everyone |
 | 2 | Structural Drafts | 4 | Carlota | Everyone | | 2 | Structural Drafts | 4 | Carlota | Everyone |
-| 2 | Write Background and Related Work chapters | 3 | Amelia & Timon | Everyone |+| 2 | Write Background and Related Work chapters | 3 | Amalie & Timon | Everyone |
 | 2 | Brainstorm other ideas inside the Smart Buildings topic | 5 | Everyone | Everyone | | 2 | Brainstorm other ideas inside the Smart Buildings topic | 5 | Everyone | Everyone |
 | **12/03/2026 - 18/03/2026** | | | | | | **12/03/2026 - 18/03/2026** | | | | |
Line 333: Line 402:
 | 3 | Improve BlackBox Diagram | 2 | Lena | Everyone | | 3 | Improve BlackBox Diagram | 2 | Lena | Everyone |
 | **19/03/2026 - 25/03/2026** | | | | | | **19/03/2026 - 25/03/2026** | | | | |
-| 4 | Detailed System Schematics | 5 | Amelia | Everyone |+| 4 | Detailed System Schematics | 5 | Amalie | Everyone |
 | 4 | Structural Drawings | 5 | Carlota | Everyone | | 4 | Structural Drawings | 5 | Carlota | Everyone |
 | 4 | Cardboard scale model of Bloem | 3 | Kaiko | Everyone | | 4 | Cardboard scale model of Bloem | 3 | Kaiko | Everyone |
Line 343: Line 412:
 | 5 | Reworking Schematic Drawings | 4 | Amalie | Everyone | | 5 | Reworking Schematic Drawings | 4 | Amalie | Everyone |
 | 5 | Creating Case Study Presentation (Ethics) | 3 | Mohammad | Everyone | | 5 | Creating Case Study Presentation (Ethics) | 3 | Mohammad | Everyone |
-| 5 | Creating the brand identity | 4 | Carlotta | Everyone |+| 5 | Creating the brand identity | 4 | Carlota | Everyone |
 | 5 | Updating marketing brand | 3 | Timon | Everyone | | 5 | Updating marketing brand | 3 | Timon | Everyone |
 | 5 | Smart System HW | 5 | Amalie | Everyone | | 5 | Smart System HW | 5 | Amalie | Everyone |
Line 357: Line 426:
 | 7 | Uploading the Report | 5 | Everyone | Everyone | | 7 | Uploading the Report | 5 | Everyone | Everyone |
 | 7 | Practising the presentation | 4 | Everyone | Everyone | | 7 | Practising the presentation | 4 | Everyone | Everyone |
-| 7 | Project Development | 3 | Carlotta | Everyone |+| 7 | Project Development | 3 | Carlota | Everyone |
 | **16/04/2026 - 22/04/2026** | | | | | | **16/04/2026 - 22/04/2026** | | | | |
 | 8 | Meeting regarding the electrical schematics with Luis | 4 | Amalie & Timon | Everyone | | 8 | Meeting regarding the electrical schematics with Luis | 4 | Amalie & Timon | Everyone |
 | 8 | Creating the 3D model | 5 | Mohammad | Everyone | | 8 | Creating the 3D model | 5 | Mohammad | Everyone |
-| 8 | Consulting on the 3D model | 3 | Carlotta | Everyone |+| 8 | Consulting on the 3D model | 3 | Carlota | Everyone |
 | 8 | Creating app drafts | 4 | Lena | Everyone | | 8 | Creating app drafts | 4 | Lena | Everyone |
 | 8 | Refining a section of the Project Management wiki part | 3 | Lena | Everyone | | 8 | Refining a section of the Project Management wiki part | 3 | Lena | Everyone |
Line 373: Line 442:
 | 9 | Designed seating platform | 4 | Timon & Mohammad | Everyone | | 9 | Designed seating platform | 4 | Timon & Mohammad | Everyone |
 | 9 | Updated electrical circuit design (meeting Luis) | 5 | Amalie | Everyone | | 9 | Updated electrical circuit design (meeting Luis) | 5 | Amalie | Everyone |
-| 9 | Focused on door mechanism (3D video) | 3 | Carlotta | Everyone |+| 9 | Focused on door mechanism (3D video) | 3 | Carlota | Everyone |
 | **30/04/2026 - 13/05/2026** | | | | | | **30/04/2026 - 13/05/2026** | | | | |
-| 10 | 3D model video | 4 | Carlotta | Everyone |+| 10 | 3D model video | 4 | Carlota | Everyone |
 | 10 | Packaging solution | 4 | Amalie & Timon | Everyone | | 10 | Packaging solution | 4 | Amalie & Timon | Everyone |
 | 10 | Continued writing scientific paper | 4 | Timon & Amalie | Everyone | | 10 | Continued writing scientific paper | 4 | Timon & Amalie | Everyone |
Line 427: Line 496:
 | 13 | Proposed solution documentation - scientific paper | 5 | Timon | Everyone | | 13 | Proposed solution documentation - scientific paper | 5 | Timon | Everyone |
 | 13 | Prototype Development - Structure - Scientific paper | 3 | Kai-Ko | Everyone | | 13 | Prototype Development - Structure - Scientific paper | 3 | Kai-Ko | Everyone |
-| 13 | Prototype Development - Smart Control - Scientific paper | 3 | Amlaie | Everyone |+| 13 | Prototype Development - Smart Control - Scientific paper | 3 | Amalie | Everyone |
 | 13 | Prototype Development - User Application - Scientific paper | 3 | Lena | Everyone | | 13 | Prototype Development - User Application - Scientific paper | 3 | Lena | Everyone |
 | 13 | Personal Outcomes Lena - scientific paper | 1 | Lena | Everyone | | 13 | Personal Outcomes Lena - scientific paper | 1 | Lena | Everyone |
Line 451: Line 520:
  
 ==== 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 ===
 Table {{ref>tab:sprint1}} shows the outcome of sprint 1.  Table {{ref>tab:sprint1}} shows the outcome of sprint 1. 
 <WRAP 80%> <WRAP 80%>
Line 476: Line 545:
   * **Tasks Finished:** 1   * **Tasks Finished:** 1
  
 +Unfortunately up until sprint 11 we were no correctly assigning points to our tasks as well as marking them as done evenly throughout the sprint. For those reasons the burndown charts do not show how we were working correctly, so we will not be including them in the outcomes.
  
 +=== Sprint 2 ===
 Table {{ref>tab:sprint2}} shows the outcome of sprint 2.  Table {{ref>tab:sprint2}} shows the outcome of sprint 2. 
 <WRAP 80%> <WRAP 80%>
Line 486: Line 557:
 | 2 | Structural Drafts | 4 | Carlota | Everyone | | 2 | Structural Drafts | 4 | Carlota | Everyone |
 | 2 | Brainstorming Smart Building concepts | 3 | Everyone | Everyone | | 2 | Brainstorming Smart Building concepts | 3 | Everyone | Everyone |
-| 2 | Write Background and Related Work chapters | 4 | Amelia & Timon | Everyone |+| 2 | Write Background and Related Work chapters | 4 | Amalie & Timon | Everyone |
 </table> </table>
 </WRAP> </WRAP>
Line 496: Line 567:
   * Developed the "Black Box" diagrams to map out how the sensors and systems will interact.   * Developed the "Black Box" diagrams to map out how the sensors and systems will interact.
   * Carlota started the first structural sketches to visualize the egg-shaped design.   * Carlota started the first structural sketches to visualize the egg-shaped design.
-  * Amelia and Timon began writing the Background and Related Work sections for the report to provide the research foundation for our project.+  * Amalie and Timon began writing the Background and Related Work sections for the report to provide the research foundation for our project.
  
 **Current Status:** All 4 tasks for this sprint were completed on time. **Current Status:** All 4 tasks for this sprint were completed on time.
Line 504: Line 575:
   * **Completed Tasks:** 4   * **Completed Tasks:** 4
  
 +=== Sprint 3 ===
 Table {{ref>tab:sprint3}} shows the outcome of sprint 3.  Table {{ref>tab:sprint3}} shows the outcome of sprint 3. 
 <WRAP 80%> <WRAP 80%>
Line 532: Line 603:
   * **Tasks carried out:** 4   * **Tasks carried out:** 4
  
 +=== Sprint 4 ===
 Table {{ref>tab:sprint4}} shows the outcome of sprint 4.  Table {{ref>tab:sprint4}} shows the outcome of sprint 4. 
 <WRAP 80%> <WRAP 80%>
Line 538: Line 610:
 ^ Sprint ^ Task ^ Duration ^ Responsible ^ Involved ^ ^ Sprint ^ Task ^ Duration ^ Responsible ^ Involved ^
 | **19/03/2026 - 25/03/2026** | | | | | | **19/03/2026 - 25/03/2026** | | | | |
-| 4 | Detailed System Schematics | 5 | Amelia | Everyone |+| 4 | Detailed System Schematics | 5 | Amalie | Everyone |
 | 4 | Structural Drawings | 5 | Carlota | Everyone | | 4 | Structural Drawings | 5 | Carlota | Everyone |
 | 4 | Cardboard scale model of Bloem | 3 | Kaiko | Everyone | | 4 | Cardboard scale model of Bloem | 3 | Kaiko | Everyone |
Line 553: Line 625:
   * Officially rebranded the project to **Bloem** and finalized the core logo concept to match our "nature meets wellness" theme.   * Officially rebranded the project to **Bloem** and finalized the core logo concept to match our "nature meets wellness" theme.
   * Kaiko built the first physical scale model using cardboard to test the dimensions and the egg-shaped curve of the capsule.   * Kaiko built the first physical scale model using cardboard to test the dimensions and the egg-shaped curve of the capsule.
-  * Amelia and Carlota produced the detailed technical schematics and structural drawings needed for the upcoming prototype phase.+  * Amalie and Carlota produced the detailed technical schematics and structural drawings needed for the upcoming prototype phase.
   * We started working on the Project Plan and Development chapters.   * We started working on the Project Plan and Development chapters.
   * Updated our material list and created a first draft of the marketing flyer to promote Bloem's benefits.   * Updated our material list and created a first draft of the marketing flyer to promote Bloem's benefits.
Line 563: Line 635:
   * **Tasks carried out:** 7   * **Tasks carried out:** 7
  
 +=== Sprint 5 ===
 Table {{ref>tab:sprint5}} shows the outcome of sprint 5. Table {{ref>tab:sprint5}} shows the outcome of sprint 5.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint5> <table tab:sprint5>
Line 573: Line 644:
 | 5 | Reworking Schematic Drawings | 4 | Amalie | Everyone | | 5 | Reworking Schematic Drawings | 4 | Amalie | Everyone |
 | 5 | Creating Case Study Presentation (Ethics) | 3 | Mohammad | Everyone | | 5 | Creating Case Study Presentation (Ethics) | 3 | Mohammad | Everyone |
-| 5 | Creating the brand identity | 4 | Carlotta | Everyone |+| 5 | Creating the brand identity | 4 | Carlota | Everyone |
 | 5 | Updating marketing brand | 3 | Timon | Everyone | | 5 | Updating marketing brand | 3 | Timon | Everyone |
 | 5 | Smart System HW | 5 | Amalie | Everyone | | 5 | Smart System HW | 5 | Amalie | Everyone |
Line 595: Line 666:
   * **Tasks Finished:** 8   * **Tasks Finished:** 8
  
 +=== Sprint 6 ===
 Table {{ref>tab:sprint6}} shows the outcome of sprint 6. Table {{ref>tab:sprint6}} shows the outcome of sprint 6.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint6> <table tab:sprint6>
Line 621: Line 692:
   * **Tasks Finished:** 3   * **Tasks Finished:** 3
  
 +=== Sprint 7 ===
 Table {{ref>tab:sprint7}} shows the outcome of sprint 7. Table {{ref>tab:sprint7}} shows the outcome of sprint 7.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint7> <table tab:sprint7>
Line 647: Line 718:
   * **Tasks Finished:** 4   * **Tasks Finished:** 4
  
 +=== Sprint 8 ===
 Table {{ref>tab:sprint8}} shows the outcome of sprint 8. Table {{ref>tab:sprint8}} shows the outcome of sprint 8.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint8> <table tab:sprint8>
Line 679: Line 750:
   * **Tasks Finished:** 8   * **Tasks Finished:** 8
  
 +=== Sprint 9 ===
 Table {{ref>tab:sprint9}} shows the outcome of sprint 9. Table {{ref>tab:sprint9}} shows the outcome of sprint 9.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint9> <table tab:sprint9>
Line 709: Line 780:
   * **Tasks Finished:** 6   * **Tasks Finished:** 6
  
 +=== Sprint 10 ===
 Table {{ref>tab:sprint10}} shows the outcome of sprint 10. Table {{ref>tab:sprint10}} shows the outcome of sprint 10.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint10> <table tab:sprint10>
Line 738: Line 809:
   * **Tasks Finished:** 6   * **Tasks Finished:** 6
  
 +=== Sprint 11 ===
 Table {{ref>tab:sprint11}} shows the outcome of sprint 11. Table {{ref>tab:sprint11}} shows the outcome of sprint 11.
- 
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint11> <table tab:sprint11>
Line 772: Line 843:
   * **Tasks Finished:** 10   * **Tasks Finished:** 10
  
-Table {{ref>tab:sprint12}} shows the outcome of sprint 12.+{{:report:zrzut_ekranu_2026-06-14_111714.png?600|}}
  
 +In this sprint we can finally see a somewhat correct burndown chart. The sprint began with a commitment of 37 story points, but the burndown chart shows that progress was logged primarily in large batches at the end of the cycle rather than steadily.
 +
 +=== Sprint 12 ===
 +Table {{ref>tab:sprint12}} shows the outcome of sprint 12.
 <WRAP 100%> <WRAP 100%>
 <table tab:sprint12> <table tab:sprint12>
Line 805: Line 880:
 | 12 | Personal Outcomes Lena - scientific paper | 1 | Lena | Everyone | | 12 | Personal Outcomes Lena - scientific paper | 1 | Lena | Everyone |
 | 12 | Personal Outcomes Kai-Ko - scientific paper | 1 | Kai-Ko | Everyone | | 12 | Personal Outcomes Kai-Ko - scientific paper | 1 | Kai-Ko | Everyone |
 +
 </table> </table>
 </WRAP> </WRAP>
Line 823: Line 899:
   * **Tasks Planned:** 26   * **Tasks Planned:** 26
   * **Tasks Finished:** 26   * **Tasks Finished:** 26
 +
 +{{:report:zrzut_ekranu_2026-06-14_112147.png?600|}}
 +
 +For this sprint, we improved our workflow by breaking down large deliverables into smaller, more precise Jira tasks. This approach made it much easier to distribute and manage our massive 116-point workload. Although the burndown chart still shows a late drop-off due to batch-updating task statuses, this detailed tracking ensured majority of the final project components were completed successfully before the deadline.
 +
 +=== Sprint 13 ===
 +Table {{ref>tab:sprint13}} shows the outcome of sprint 13.
 +<WRAP 100%>
 +<table tab:sprint13>
 +<caption>Sprint 13 Overview</caption>
 +^ Sprint ^ Task ^ Duration ^ Responsible ^ Involved ^
 +| **28/05/2026 - 03/06/2026** | ::: | ::: | ::: | ::: |
 +| 13 | Building the wooden part of the prototype | 13 | Timon | Everyone |
 +| 13 | Internal functions in 3D model | 8 | Carlota | Everyone |
 +| 13 | Results of the Functional Tests | 8 | Amalie | Everyone |
 +| 13 | Proposed solution documentation - scientific paper | 5 | Timon | Everyone |
 +| 13 | Render of the capsule | 5 | Carlota | Everyone |
 +| 13 | Report (Wiki) - Prototype | 3 | Kai-Ko | Everyone |
 +| 13 | Prototype Development - Structure - Scientific paper | 3 | Kai-Ko | Everyone |
 +| 13 | Prototype Development - Smart Control - Scientific paper | 3 | Amalie | Everyone |
 +| 13 | Prototype Development - User Application - Scientific paper | 3 | Lena | Everyone |
 +| 13 | Personal Outcomes Lena - scientific paper | 1 | Lena | Everyone |
 +| 13 | Personal Outcomes Kai-Ko - scientific paper | 1 | Kai-Ko | Everyone |
 +</table>
 +</WRAP>
 +
 +**Sprint 13 Summary:**
 +
 +**Main Achievements:**
 +  * Successfully built and assembled the wooden structural components of the prototype.
 +  * Finalized the 3D model's internal functions and generated high-quality renders of the capsule.
 +  * Executed and documented the results of the hardware and software functional tests.
 +  * Made significant progress on the scientific paper, drafting sections for the proposed solution, structure, smart control, and user application.
 +  * Updated the prototype section of the Wiki report and completed the individual personal outcome papers for team members.
 +
 +**Progress Check:** 100% of the planned work for this week is finished.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 11
 +  * **Tasks Finished:** 11
 +
 +{{:report:zrzut_ekranu_2026-06-14_112624.png?600|}}
 +
 +This burndown chart demonstrates a highly improved and much more steady progress tracking across a workload of 53 story points. Instead of a single massive drop at the end, the red line shows a consistent step-down pattern that closely tracks the ideal grey guideline throughout the sprint.
 +
 +
 +=== Sprint 14 ===
 +Table {{ref>tab:sprint14}} shows the outcome of sprint 14.
 +<WRAP 100%>
 +<table tab:sprint14>
 +<caption>Sprint 14 Overview</caption>
 +^ Sprint ^ Task ^ Duration ^ Responsible ^ Involved ^
 +| **04/06/2026 - 10/06/2026** | ::: | ::: | ::: | ::: |
 +| 14 | Set up electronics for the prototype using the new ESP32 | 8 | Amalie | Everyone |
 +| 14 | Add an image of our proposed solution to the scientific paper | 2 | Timon | Everyone |
 +| 14 | Add the sides (made of cardboard) to the prototype | 5 | Kai-Ko | Everyone |
 +| 14 | Generate an image of the capsule in a real-world setting | 1 | Timon | Everyone |
 +| 14 | Review all deliverables (and possibly update images) | 5 | Carlota | Everyone |
 +| 14 | Begin working on the video for Bloem | 13 | Timon | Everyone |
 +| 14 | Add music to the app | 5 | Lena | Everyone |
 +| 14 | Move daily meeting to Jira | 2 | Amalie | Everyone |
 +| 14 | Move retrospectives to Jira | 2 | Amalie | Everyone |
 +| 14 | Rework the Procurement part in Wiki | 3 | Timon | Everyone |
 +| 14 | Rework user manual | 3 | Mohammad | Everyone |
 +| 14 | Rework stress test and add to Wiki (with pictures) | 5 | Mohammad | Everyone |
 +| 14 | Rework the quality chapter in project management | 3 | Lena | Everyone |
 +| 14 | Scientific Paper - stress test | 3 | Mohammad | Everyone |
 +| 14 | 3D model - electrical components (Tablet,Speaker,ESP32) | 8 | Mohammad | Everyone |
 +| 14 | 3D model - modeling wire connection to the LED | 5 | Mohammad | Everyone |
 +| 14 | 3D model - Motion Study | 13 | Mohammad | Everyone |
 +| 14 | Final 3D Model video edit caption and audio | 13 | Mohammad | Everyone |
 +</table>
 +</WRAP>
 +
 +**Sprint 14 Summary:**
 +
 +**Main Achievements:**
 +  * Assembled the cardboard side panels.
 +  * Considerably advanced the 3D modeling workflow, completing the electrical component modeling, LED wire connections, motion studies, and the final 3D model video with captions and audio.
 +  * Improved project management tracking by fully migrating daily meetings and retrospectives into Jira.
 +  * Reviewed and reworked key documentation, heavily updating the Procurement, Quality, and Stress Test sections on the Wiki, alongside revising the User Manual.
 +  * Enhanced the Bloem mobile application by successfully integrating music features.
 +
 +**Progress Check:** 100% of the planned work for this week is finished.
 +
 +**Effort Breakdown:**
 +  * **Tasks Planned:** 18
 +  * **Tasks Finished:** 18
 +
 +{{:report:zrzut_ekranu_2026-06-14_113440.png?600|}}
 +
 +This sprint's burndown chart begins with an initial commitment of 56 story points and shows steady, incremental progress during the first half of the week. Around June 11th, there is a clear scope increase where new tasks were added to the sprint, causing the remaining work line to jump back up above 50 points. Despite this significant late addition, the team successfully burned down all remaining points to close the sprint on time.
 +
 +
 ==== Sprint Evaluations ==== ==== Sprint Evaluations ====
  
Line 833: Line 1003:
 <caption>Sprint 1 reflection</caption> <caption>Sprint 1 reflection</caption>
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| **Positive** | Good teamwork and high motivation when starting the project. |+| **Positive** | Good teamwork and high motivation for starting the project. |
 | **Negative** | More time could have been spent on exploring different project ideas in the beginning, to avoid changing direction later. | | **Negative** | More time could have been spent on exploring different project ideas in the beginning, to avoid changing direction later. |
-| **Ideas** | Focus on the ideation workshop to improve how we formulate problems and evaluate possible solutions more systematically. |+| **Ideas** | Focus on the ideation workshop to improve how we formulate problems and evaluate possible solutions. |
 | **Actions** | — | | **Actions** | — |
 </table> </table>
Line 848: Line 1018:
 <caption>Sprint 2 reflection</caption> <caption>Sprint 2 reflection</caption>
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| **Positive** | Settling on the wellness capsule idea. Team has a clear and exciting goal. Team focuses on how the problem of stress can be solved. A lot of different ideas on design, functions etc. | +| **Positive** | Settling on the wellness capsule idea. The team has a clear goal. We have focused on how the problem of stress can be solved. A lot of different ideas on design and functions. | 
-| **Negative** | Challenging to define the technical inputs/outputs while the design was still changing. Deliverables must be handed in while the project is currently stuck / needs to focus on other topics. |+| **Negative** | Challenging to define the project while the design is still changing. Deliverables must also be handed in while the project is being defind. |
 | **Ideas** | — | | **Ideas** | — |
 | **Actions** | Ask for guidance from the project supervisor. | | **Actions** | Ask for guidance from the project supervisor. |
Line 857: Line 1027:
 **Sprint 3 Evaluation** **Sprint 3 Evaluation**
  
-Sprint 3 was all about research. We looked into sustainable materials to see what would work best. While the marketing chapters were being drafted, we focused on refining the system logic. We also uploaded our first official list of components. The reflection is shown in Table {{ref>tab:eval3}}. +Sprint 3 was all about research. We looked into sustainable materials to see what would work best. While the marketing chapters were being drafted, we focused on refining the system. We also uploaded our first official list of components. The reflection is shown in Table {{ref>tab:eval3}}. 
  
 <WRAP 80%> <WRAP 80%>
Line 863: Line 1033:
 <caption>Sprint 3 reflection</caption> <caption>Sprint 3 reflection</caption>
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| **Positive** | Good progress on the marketing part of the report and solid first drafts for the project. |+| **Positive** | Good progress on the marketing part of the report and solid first drafts of the drawing for the project. |
 | **Negative** | Material research was not detailed or structured enough. | | **Negative** | Material research was not detailed or structured enough. |
 | **Ideas** | Revisit the concept in a more structured research phase, focusing on design, size, functionality, and materials before final decisions. | | **Ideas** | Revisit the concept in a more structured research phase, focusing on design, size, functionality, and materials before final decisions. |
-| **Actions** | List all capsule functions and refine the concept based on clearer requirements. |+| **Actions** | List all capsule functions and refine the concept. |
 </table> </table>
 </WRAP> </WRAP>
Line 878: Line 1048:
 <caption>Sprint 4 reflection</caption> <caption>Sprint 4 reflection</caption>
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| **Positive** | It felt relieving to finally settle on a name and branding decisions after a long time of debating them. The first prototype successfully convinced stakeholders. |+| **Positive** | We settled on a name and branding decisions after a long time of debating. The first prototype successfully convinced stakeholders. |
 | **Negative** | The workload for the drawing part was very high and we should have planned to start it earlier. | | **Negative** | The workload for the drawing part was very high and we should have planned to start it earlier. |
 | **Ideas** | Improve future planning by estimating workload hours in more detail, distributing tasks more evenly across the team, using Jira more actively, and recalculating workload for upcoming tasks. | | **Ideas** | Improve future planning by estimating workload hours in more detail, distributing tasks more evenly across the team, using Jira more actively, and recalculating workload for upcoming tasks. |
Line 893: Line 1063:
 <caption>Sprint 5 Reflection</caption> <caption>Sprint 5 Reflection</caption>
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
-| **Positive** | Detailed structural drawings were completed, and the capsule shape became more finalized. Material layers and internal components were selected. Jira planning for the interim deadline was improved, and both the ethical scandal presentation and course presentation were completed. | +| **Positive** | Detailed structural drawings were completed, and the capsule shape became more clear. Material layers and internal components were selected. Jira planning for the interim deadline was improved, and both the ethical scandal presentation and "interim" presentation were completed. | 
-| **Negative** | Electrical implementation is still not fully defined, and integration of electronic components remains unclear. Some technical decisions are still pending. | +| **Negative** | Electrical implementation is still not defined. Technical decisions are still pending. | 
-| **Ideas** | Develop a clearer electronic system architecture, define communication between electrical components earlier, and create subsystem diagrams to support implementation. |+| **Ideas** | Develop a clearer electronic system architecture, define communication between electrical components, and make a plan for implementation. |
 | **Actions** | Continue developing electrical schematics, finalize the integration concept for electronics, and prepare remaining tasks for the interim milestone. | | **Actions** | Continue developing electrical schematics, finalize the integration concept for electronics, and prepare remaining tasks for the interim milestone. |
 </table> </table>
Line 902: Line 1072:
 **Sprint 6+7 Evaluation** **Sprint 6+7 Evaluation**
  
-In sprint 6+7 we worked on the interim presentation and report completion, but highlighted that software development and app functionality definition are still missing and must be prioritised going forward.+In sprint 6+7 we worked on the interim presentation and report completion, but highlighted that software development and app functionality definition are still missing and must be prioritised going forward. The reflection is shown in Table {{ref>tab:eval6}}.
  
 <WRAP 80%> <WRAP 80%>
Line 909: Line 1079:
 ^ Aspect ^ Reflection ^ ^ Aspect ^ Reflection ^
 | **Positive** | Interim presentation preparation progressed efficiently with clear prioritization of key topics. The interim report was completed, including ethics, project management, and design solution chapters. | | **Positive** | Interim presentation preparation progressed efficiently with clear prioritization of key topics. The interim report was completed, including ethics, project management, and design solution chapters. |
-| **Negative** | Software development had not yet started, and app functionalities remain undefined. The prototype implementation plan also lacks sufficient detail. |+| **Negative** | Software development had not yet started, and app functionalities remain undefined. The prototype implementation plan lacks detail. |
 | **Ideas** | Define core functionalities of the app before adding advanced features, and creating a structured workflow for the prototype. | | **Ideas** | Define core functionalities of the app before adding advanced features, and creating a structured workflow for the prototype. |
 | **Actions** | Start app development, define user functionalities and software architecture, and plan the prototype construction process in more detail. | | **Actions** | Start app development, define user functionalities and software architecture, and plan the prototype construction process in more detail. |
 </table> </table>
 </WRAP> </WRAP>
 +
 +**Sprint 8 Evaluation**
 +
 +Sprint 8 improved technical developing after schematics review with Luis, and material list completion. 3D integration still require further development. The reflection is shown in Table {{ref>tab:eval8}}.
 +
 +<WRAP 80%>
 +<table tab:eval8>
 +<caption>Sprint 8 Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Meeting with Luis regarding the electrical schematics was productive, and the final material list was clarified and completed. |
 +| **Negative** | Errors were identified in the electrical schematics, the door mechanism design is still incomplete, and the 3D model lacks detailed mechanical integration. |
 +| **Ideas** | Develop multiple door mechanism concepts before finalizing. Integrate electrical components in the 3D model and improve internal structure visualization. |
 +| **Actions** | Correct schematic errors, continue refining the 3D model, and work on the door mechanism. |
 +</table>
 +</WRAP>
 +
 +**Sprint 9 Evaluation**
 +
 +Sprint 9 shows strong progress in system design and integration (door mechanism, seating, lighting, and app layout). The reflection is shown in Table {{ref>tab:eval9}}.
 +
 +<WRAP 80%>
 +<table tab:eval9>
 +<caption>Sprint 9 Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Door mechanism integration was further developed, a ceiling-mounted speaker solution was identified, the lighting concept was improved with the placement of the LED strip, the tablet mounting solution was finalized, the seating design and comfort features were defined, and an initial app layout was created. |
 +| **Negative** | Procurement of materials is not yet coordinated, app functionalities are still under development, and some mechanical integration details remain unresolved. |
 +| **Ideas** | Test seating dimensions. |
 +| **Actions** | Continue app implementation. |
 +</table>
 +</WRAP>
 +
 +**Sprint 10 Evaluation**
 +
 +Sprint 10 reflects continued progress in packaging, 3D modeling, and scientific documentation, but also highlights further work on the deliverables. The reflection is shown in Table {{ref>tab:eval10}}.
 +
 +<WRAP 80%>
 +<table tab:eval10>
 +<caption>Sprint Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Packaging solution development progressed, 3D model refinement continued, the scientific paper introduction was completed, and initial versions of the scientific poster and leaflet were created. |
 +| **Negative** | The door mechanism is still not working, the poster and leaflet still require refinement, and remaining scientific paper sections are unfinished. |
 +| **Ideas** | Explore alternative door opening concepts, improve visual consistency across poster and leaflet, and divide paper sections among team members for efficiency. |
 +| **Actions** | Find a solution for the door opening concepts. |
 +</table>
 +</WRAP>
 +
 +**Sprint 11 Evaluation**
 +
 +In sprint 11 we had strong overall progress in technical development, design, packaging, and documentation, but still have challenges with the door mechanism. And Jira workflow clarity that still need to be resolved. The reflection is shown in Table {{ref>tab:eval11}}.
 +
 +<WRAP 80%>
 +<table tab:eval11>
 +<caption>Sprint Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Progress technical development and 3D model, improved structural design (wooden ribs, layered walls, interior detailing), initial packaging concept developed (modular flat-pack for curved geometry), good progress on the scientific paper (solution, structure, packaging, conclusion), improved poster and marketing leaflet layout/content, and a useful meeting with the project management supervisor on Jira workflow. |
 +| **Negative** | The door mechanism still needs work and the Jira workflow still lacks structure and tracking. |
 +| **Ideas** | Explore alternative door concepts (hinged, segmented, foldable), focus on Jira, define clearer “definition of done” for tasks. |
 +| **Actions** | Redesign the door mechanism, finalize 3D model structure and interior and complete scientific paper sections. |
 +</table>
 +</WRAP>
 +
 +**Sprint 12 Evaluation**
 +
 +Sprint 12 shows progress on app and hardware integration, while still needing completion of scientific writing, rendering development, and improved coordination between team deliverables. The reflection is shown in Table {{ref>tab:eval12}}.
 +
 +<WRAP 80%>
 +<table tab:eval12>
 +<caption>Sprint 12 Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Strong progress on 3D model and structural refinement, successful stress analysis, steady app development, and completion of key documentation and marketing deliverables. |
 +| **Negative** | Scientific paper is still incomplete in parts, rendering is in early development, and documentation coordination is slightly fragmented across the team. |
 +| **Ideas** | Improve writing on the scientific paper across the team. |
 +| **Actions** | Complete scientific paper, finalize rendering and complete app–hardware integration. |
 +</table>
 +</WRAP>
 +
 +**Sprint 13 Evaluation**
 +
 +Sprint 13 shows strong overall progress in scientific writing, modeling, and prototype development, but is constrained by materials for the prototype. The reflection is shown in Table {{ref>tab:eval13}}.
 +
 +<WRAP 80%>
 +<table tab:eval13>
 +<caption>Sprint 13 Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | Major progress on the scientific paper, successful integration of internal functions in the 3D model, prototype construction started, functional tests completed, rendering progress made, and an alternative ESP32 solution was secured to reduce risk. |
 +| **Negative** | ESP32 availability issues, material delays affecting prototype construction. |
 +| **Ideas** | Improve early material planning and introduce integration checkpoints. |
 +| **Actions** | Review scientific paper, continue prototype construction, complete rendering and start video production, finalize integration testing, acquire missing materials. |
 +</table>
 +</WRAP>
 +
 +**Sprint 14 Evaluation**
 +
 +Sprint 14 shows strong final progress across documentation, design, and prototype development, with most major deliverables completed. The reflection is shown in Table {{ref>tab:eval14}}.
 +
 +<WRAP 80%>
 +<table tab:eval14>
 +<caption>Sprint 14 Reflection</caption>
 +^ Aspect ^ Reflection ^
 +| **Positive** | The scientific paper was submitted, the final 3D model was completed, many loose ends were finalized, the final image of Bloem was added to all communication materials, and the prototype is now far along. |
 +| **Negative** | There is not much motivation left at this stage of the project. |
 +| **Ideas** | Focus on completing the last remaining tasks efficiently as a team. |
 +| **Actions** | A dedicated day has been scheduled in the next sprint to practice the upcoming presentation. |
 +</table>
 +</WRAP>
 +
 ==== Summary ==== ==== Summary ====
 This chapter showed how we kept the Bloem project organized from the very first week. By using tools like Jira and a Gantt chart, we were able to map out a clear timeline and make sure everyone knew their roles. Breaking the semester into weekly sprints was really helpful because it allowed us to stay on top of the workload and adjust our plans as we moved from brainstorming to technical design. This chapter showed how we kept the Bloem project organized from the very first week. By using tools like Jira and a Gantt chart, we were able to map out a clear timeline and make sure everyone knew their roles. Breaking the semester into weekly sprints was really helpful because it allowed us to stay on top of the workload and adjust our plans as we moved from brainstorming to technical design.
  • report/prm.1780483387.txt.gz
  • Last modified: 2026/06/03 11:43
  • by team2