Logbook

This is your logbook. Insert here all relevant information regarding the evolution of your project

The team got to know eachothers strengths and weaknesses in relation to their education and group work in general. Based on experience and motivation the team managed to eliminate themes from the project list, resulting in a list of 6 themes. We dicussed the selected themes and ended up with our top 3: digital art, innovative city experiences and smart bug/smart food production. The team experienced difficulties with choosing direction within each theme, resulting in miscommunication and an overdue mail about our preferred project themes. There was a meeting regarding miscommunication to prevent incidents in the near future.

The team started the week by brainstorming ideas related to the themes of city experiences and digital art. During this process, the team was assigned the smart bug/smart food theme. After discussing both options, the team decided to focus on smart food, as the motivation and interest within the group were higher for this direction.

The team explored different problems related to this theme. One idea was to focus on urban farming in small living spaces, such as student apartments. The discussion included the concept of small grow pods, including the possibility of stackable pods to optimize limited space.

One challenge during the week was identifying a specific and innovative problem to solve, rather than simply replicating grow pod products that already exist on the market.

After the meeting on Thursday, the team discussed different plant types that could be used in the system, including plants, fruits, herbs, and flowers, and considered which would be most suitable for the concept.

The design thinking session on Friday helped the team refine the idea further. Through additional brainstorming, the focus shifted to identifying a more specific problem. This led to the concept of combining a smart grow pod with digital wellbeing and screen-time reduction. The idea is inspired by study applications where virtual plants grow when the user avoids using their phone. The concept follows the same principle, but with a real plant growing inside a smart pod.

The team also discussed using basil as the initial plant for the prototype, since basil reacts quickly to environmental changes such as reduced water or light, making the feedback visible to the user. The system is designed to remain ethically responsible, meaning that the plant will never be harmed or killed intentionally. Instead, users will be rewarded with optimal plant growth conditions when they keep their screen time within their chosen limits.

During this week, the team focused on refining the project concept, as well as organizing further work and responsibilities within the group.

The team discussed whether the concept of a Smart Grow Pod for digital wellbeing is realistic and suitable. The system design was also reviewed using a black-box model and a structural overview to understand how the components interact.

Key design decisions included choosing basil and grains for the prototype. The team discussed components such as an ESP32 microcontroller, basic sensors, a water pump, and a reservoir. The plan is to keep the system simple and expand if possible.

Research and writing tasks were divided in Jira for the background chapter. The rest of the team is also contributing ideas through brainstorming.

The concept was further developed by creating a logo and discussing design ideas, including using gravity for watering by placing the water source at the top, for example. The team also visited the school's systems with Abel to look at water pumps.

Lastly, the team discussed key questions regarding the concept, component realism, scope, and related aspects.

What went well:

• The team prepared a proper presentation and finished most of the deliverables on time.

What went not so well:

• There was no agenda
• Low engagement with each other
• The team didn't review each other's work
• No proper forms of communication off-campus
• Jira tasks didn't get updated in time

Actions:

• The team should start communicating and engaging more off-campus. We need to show more engagement towards members’s to-review tasks and reply to each other on WhatsApp, even if it’s confirmation on reading a message.
• The team should keep going into discussion when we disagree with opinions, it opens new windows and rooms for idea.
• The team should stop leaving each other’s messages unanswered.

19/03/2026: Scrum has a hierarchy of themes, epics, features and tasks. The free version of Jira however has many limitations on story mapping. It's impossible to both link existing tasks to features and vise versa. Finally, subtasks of features are invisible on the board. Keeping a proper Scrum timeline is important for management and reporting, so the team has decided the following.

• Instead of tasks, the team decided to use more granular features. These will be more detailed and will contain subtasks when necessary.
• Epics will keep serving their purpose, being groupings of features. Every deliverable becomes its own epic.
• Epics will be grouped under labels, these will serve as a substitute for themes.

Because this sprint has already started however, with a load of tasks, the team has decided to implement the change starting next sprint.

23/03/2026 The team got feedback on their market analysis.

• The structure & flow of analysis are both good
• Use the TAMSAMSOM principle to further narrow down the target group
  • Additionally, use this principle in the idea formulation chapter

30/03/2026 Presentation on case study of ethical business scandal for communications class was prepared and presented.

31/03/2026 Team improved the way of presenting together, feedback from ma-com presentation preparing for the Interim.

01/04/2026: After a meeting with the teachers, the team concluded the following:

• There's no uniformity in number and unit usage. When using a number and a unit, there must always be a space in between.
• Basil doesn't need light but users might want to grow other plants. The team must consider a lighting system.
• The schematic deliverable and the list of materials & components need to be revised. If help is needed, the team can contact the professor (LUL)
• The SWOT analysis needs to be corrected. Threats are external phenomena, so related to users and the area. Weaknesses are internal, like component failure.
• The team is mixing the words pod and pot in the report, only one can remain.

• Presentation
• Modus operandi
• Project proposals
• Electronic logbook (Wiki)

The first meeting was held in the auditorium with all project teams present. During the session, the supervisors introduced the EPS project themes and provided an overview of the project framework. The working methodology, expectations, and timeline for the semester were explained. Instructions were given on how to use the Wiki for documentation and reporting throughout the project.

• Smart food: brainstorm regarding which problem to solve.
• Question regarding the shape and factors.
  • air flow
  • humidity
  • temperature
  • materials
  • space
  • work load
  • cleaning
  • …
• Main focus of the project
• Discuss possible technologies
• Next steps

During the meeting, the team discussed the direction of the smart food project. While the idea of building a dome on top of Building G was mentioned, the current focus is on developing a small, affordable growth pod for student apartments. The concept should emphasize energy resilience, potentially using solar panels and different power modes.

It was highlighted that all design decisions must be supported by ethics, sustainability and market considerations. Finally, the product should include some form of innovation to stand out in the market. The team also discussed possible plant options including vegetables, berries, and herbs.

The next steps include creating a black-box diagram of the system, researching compatible ESP32 components and starting the state-of-the-art chapter by reviewing existing solutions and competitors.

- Overview of the current project concept: Smart grow pod for digital wellbeing.

- System design overview: Black-box and structural.

- Key design decisions: basil, hydroponic growing system.

- Materials and component selection: ESP32 microcontroller, sensors (start with the basic: water level, ..), hydroponic reservoir, water pump(s), servo?.

Questions:

- Is the project concept acceptable?

- Are the system components realistic for the prototype?

- Should the team simplify or expand any part of the product?

- What is the criteria for sitation in the report?

- What is the most important moving on?

- Gantt Chart?

This week, the focus is on writing the background section with proper citations, using the wiki as the main reference source, and including ethics and competitor pricing. The project should prioritize sustainability, affordability, and human-centered design, with attention to energy use and materials.

The concept involves a vertical hydroponic system with plants and fish, supported by a smart control system (new black box diagram). Key decisions include the level of automation and alignment with the target user group. The app will feature automation, user guidance, notifications, and a teaching function, while also encouraging community interaction and outdoor engagement.

Design should incorporate natural, locally sourced materials, with a compact structure and integrated screen. All choices must support sustainability and ethical standards. Proofreading and typo checks are required.

- Project progress update wiki with research, some ethics/sustainability, market analysis, component list. Flyer.

- The new product with the app (features such as step count, daily summary).

- No LED's - want to focus on the basis of the system.

- No DWC → Seramis.

- Feedback on components and materials.

Questions:

NO MEETING WITH PRESENTATION

The team had a small impromptu meeting with the lecturers where they gave quick feedback.

• The materials & components list only included components.
• The list missed some vital columns such as maximum current and voltage.
• The team must now start considering local providers.
• The structural diagram was missing in the report.

1. Presentation ⇒ update on our project.

2. Detailed schematics

3. Structural drawings

4. Cardboard model

5. Plan for the upcoming week

Questions:

1. Feedback:

• Components & materials list

• Electrical system, structural diagram & detailed schematics

• Wiki + which chapters to focus on

2. Community socials as bibliography

3. 3D print the prototype: need to focus on other chosen material for the “real” product itself in the report?

We clarified the details regarding the interim presentation and report. The presentation should include: problem, project management, state of the art, ethics and market analysis, leading into the solution design, and ending with conclusion.

Moving forward, chapter 7 needs more work and should be improved. Overall, the report needs to be more professional. The group needs to improve the start page, including the title and project name. The basil plant's life cycle should be considered in the design. It was suggesten tat the user could collect seeds, and that the design could include a second pot for planting.

The group should finalize the design and update the structural diagram, as well as improve the black box.

A list of materials must be created, including relevant providers/suppliers.

If we want to 3D-print the prototype, we have to provide drawings for this. But also we need to write about the real material used in the product that we are selling.

1. Presentation ⇒ update on our project.

2. Presenting final marketing materials - logo, color pallet, flyer

3. Structural drawings updated based on previous week feedback

4. SWOT analysis

5. Fixed black-box diagram

Please register here all accomplished project activities