Skip to content

Sprint3

Jump to bottom
mrjex edited this page May 20, 2023 · 15 revisions

Scope

Sprint 3 issues

Out of scope

Issues labeled out-of-scope signifies our future updates if we were to continue this project

Out-of-scope issues

Challenges and Lessons Learned

Hardware limitations

  • Impossibility of sending a MQTT-message of a string containing notes for an entire song: Too much space when sending string containing all notes - We came up with a solution to send sequential song-note-chunks

  • Impossibility of sending pictures along with the string of song notes: RAM limited, images were bigger than the music itself, you can't chunk the images

Other

  • Text

Learning Outcomes

Text

General reflection of all sprints

Lessons applicable to other courses (General, Team dynamics, Team management, What we would be different if we would do the project again)

  • Detailed plan of system and its interactions from the start - Use diagrams - Sequence diagrams
  • Because we developed our idea as the project progressed
  • This detailed plan will help us identify what interactions between systems to be implemented, then we would first make sure every connection works and then we would focus on implementing the features - Save time - Classes not bloated

Video

Link here

Retrospection

Sprint 3 went quite well. Although it was a lot of work initially, we managed to get the majority of it done. However we did consider some features to be out of scope due to technically difficulties in their implementation such as saving a bitmap of the users profile picture to the phones local storage. Moreover there were many bugs that we had to iron out and consider that could have been delt with if we tried the app extensively instead of testing it only after a feature is implemented which lead to a lot of chaos and long meetings to fix them.

The documentation of the project we feel was overall good. We made a few diagrams that could help newcomers to better understand the project scope, aim, architecture and functionality it provides.

We believe the app is easily extensible and modular for future updates if the team wishes to work more on it as a passion project.

In conclusion we are quite satisfied with the MVP the team has created for users who are passioante about their weight loss journey while enjoying music in a way they have not experienced before.

Clone this wiki locally