When setting the initial goals and strategy for our first sprint, looking at- and organizing the tasks, we quickly came to the conclusion, that we need three different Main functions and as many subfunctions as necessary for each of them.
The plan is to assign people to the main functions, and they will be responsible for all the corresponding subfunctions. What we are trying to figure out is how the main functions should be defined and what should be included under each of them. Our initial thoughts was to name them “Pouring”, with things like anti-foaming device, “Casing”, with things like assembly and materials, and “Hardware and Software”, which involve coding and electronics. Alternatively, the main functions could be called something like Hardware, Software, and Usability.
After further considerations, the main functions were discussed again, and we agreed that we need to ensure that the entire system is divided into meaningful areas that allow us to work efficiently. We arrived at the following main functions:
Customer usability & design “R&D – Regulations and Design” (Oscar, Tobias)
- Anti-foaming
- Design implementations (on the app and/or the prototype)
- Interface (On app or on frame? Design proposals hereof)
Casing & framing “C&F” (Haris, Morten)
- Assembly
- General look
- Materials
- Dimensions
- Drip tray
Electronics & software “F&E – Fluids and Electronic” (Christian, Lui, Stefan)
- Coding
- UX/UI
- Payment
- Interface on the prototype (QR-code, NFC chip…)
- Pipes
- Flow sensor
General tasks: Blog (Morten), Template fillings (protomap & prototype planners), ropeholder.
General tasks, week 2-3: video, report.
SCRUM Master: Tobias
There are certainly overlaps where there are interfaces between the different parts, but we will communicate and coordinate as necessary. We have also planned other tasks such as blogging, report writing, and possibly documentation for BeerWell, etc.
Additionally, we have also updated our design brief and our basic specifications for BeerWell.