Skip to content

Sprint #3 Delivery

George P. Latos edited this page Nov 12, 2024 · 2 revisions


! DEAD LINKS DUE TO MIGRATION !

Scope

https://git.chalmers.se/courses/dit113/2023/group-2/group-2/-/issues/?label_name%5B%5D=Sprint%203

Challenges and lessons learned

In this sprint, much like the previous, we faced some serious challenges. Ultimately, this led to the unscoping of many features, such as push notifications and graph drawing. One crucial lesson we learned is the importance of a testing phase, which we planned but eventually didn't have time for. The collective opinion of the group was that we should have set more concrete deadlines to avoid running out of time.

Another challenge we faced is using gitlab, and allocating enough time for dealing with merge conflicts. A large portion of our time was spent on this.

Learning outcomes

  • Git - we finally practiced proper commit messages in this final sprint, with the commit message starting with the issue #
  • Connectivity - We implemented bi-directional connectivity with the Wio terminal in this final sprint. The terminal now shows a welcome message upon receiving a signal from the app (that mqtt is connected)
  • Third tier - A new tier to the system was implemented in this sprint, that being a nodeJS server that can continuously run and save data to a json file, which can then be retrieved by the android app when the mqtt connection is re-established