Provide here an overview of the contents (structure) of this chapter. Explain the project management approach your group followed and justify why you think it is a good approach.

Defining the scope of Bloem is essential for keeping our efforts focused on the project's core objectives. By mapping out exactly what is included in the project, we can prevent scope creep and make sure every team member understands the roadmap. The Work Breakdown Structure (WBS) below illustrates how we have divided the project into manageable phases to ensure we reach a successful final prototype.

3.2 Time

In this section, we lay out the schedule and all the major deadlines we have to hit throughout the semester. 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.

Table 1 …

Describe your project budget and its key components. Explain how your budget was managed throughout the project. Document the planned vs. effective costs of your project.

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.

Bloem Product Quality

The quality metrics for the physical prototype are focused on three main points:

• 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.
• 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.

Documentation Quality

To make sure our report and wiki are easy for the supervisors and other students to follow, we follow these rules:

• 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.
• 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.

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.

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.

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.

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.

Table 2 …

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.

We meet in person during class hours several times a week.

Table 3 shows the actual communication channels we use for the project.

Table 3 …

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.

Identify key risks (product and project level), evaluate them and define how they should be handled (responses) and monitored. Perform quantitative and qualitative risk analysis and use the results to define the appropriate risk responses.

Document your procurement management strategy including make vs buy decisions, materials/services to be acquired, sources, costs, timings, etc.

The project is organized into one-week sprints to support an iterative and flexible development workflow. The full timeline is presented in Table 4, which serves as a structured reference for monitoring progress and ensuring alignment with the overall project goals.

Our project backlog works as a roadmap for the team, helping us stay on top of all the EPS milestones. We’ve arranged these tasks to make sure the workflow stays consistent and that we're hitting our deadlines as we build Bloem. The detailed list of these items and their current status is provided in Table 5 below.

To manage our time effectively, we’ve broken the project down into one-week 'sprints.' This allows us to focus on specific tasks each week and ensures that we are making steady progress toward our final goals. Table 6 shows our schedule, including the duration of each task and who is responsible for leading them.

Figure 1 provides a visual overview of our complete schedule. It allows us to track the duration of each task at a glance and see how they fit together over the semester, making it easier to manage the long-term deadlines for Bloem.

Include the outcomes of all sprint reviews (what was the sprint backlog, completion status, planned capacity vs. achieved velocity).

Table 7 …

Sprint 1 Summary:

Main Achievements:

• Held our first team meetings to discuss project interests.
• Researching and ranking our top 3 project choices for the supervisors.
• Agreed on the initial vision for a dehumidifier structure.

Progress Check: 100% of the planned work for this week is finished.

Workload Stats:

• Tasks Planned: 1
• Tasks Finished: 1

Table 8 …

Sprint 2 Summary:

What we got done:

• Explored different “Smart Building” ideas and officially chose the wellness capsule.
• 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.
• Amelia 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.

Workload Summary:

• Planned Tasks: 4
• Completed Tasks: 4

Table 9 …

Sprint 3 Summary:

Tasks Completed:

• The whole team researched sustainable materials (like cork and hemp) and technical components to ensure the capsule meets our wellness goals.
• Amalie and Lena compiled the initial material list and uploaded it to the project wiki.
• Timon drafted the Marketing chapters.
• Lena refined the Black Box diagram based on the new research and feedback from our supervisors.

Status Update: 100% of tasks were finished by the end of the week.

Efficiency Metrics:

• Tasks in the plan: 4
• Tasks carried out: 4

Table 10 …

Sprint 4 Summary:

Key Results for this period:

• 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.
• Amelia 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.
• Updated our material list and created a first draft of the marketing flyer to promote Bloem's benefits.

Current Status: Sprint successfully completed with 100% of tasks finished.

Effort Breakdown:

• Tasks in the plan: 7
• Tasks carried out: 7

3.12 Sprint Evaluations

Sprint 1 Evaluation

In the first sprint, the team focused on getting organized. We chose our initial topic and attended the introduction sessions. It was mostly about figuring out how we would work together and getting the basic tools ready.

Table 11 …

Sprint 2 Evaluation

During this sprint, we did a deep dive into Smart Buildings and officially decided to create the wellness capsule. We started on the first structural drawings and the Black Box diagrams to see how it would all work. We also began the first research chapters for the report.

Table 12 …

Sprint 3 Evaluation

Sprint 3 was all about research. We looked into sustainable materials to see what would work best for the shell. While the marketing chapters were being drafted, the IT side focused on refining the system logic. We also uploaded our first official list of components.

Table 13 …

Sprint 4 Evaluation

This was a big week for us. We officially rebranded to Bloem, finalized the logo and built a physical cardboard model to check the scale. We also did the detailed technical drawings and worked on the Project Plan and Development chapters to document our progress.

Table 14 …

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.

Throughout these first four weeks, the team successfully navigated the shift from a broad “Smart Building” concept to the specific Bloem wellness capsule. We've now reached a point where we have a solid technical foundation, including detailed drawings and a physical cardboard scale model.

With the project management and initial planning now established, the following chapter will focus on our Marketing Plan and how we intend to position Bloem in the wellness market.