Sprint 4 Retrospective

[BSU-EzekielHolmes]

Sprint 4 Goal:

The goal for Sprint 4 was to: setup and hold a meeting with our sponsor and assess where we're at, getting the dials working properly, setting up unit testing. adding labels for the heat map, saving the images from the canvas, and implementing the parsing methods built from last sprint.

Did we meet this goal:

We were able to complete most of our goal for this sprint. We have not yet added numeric labels to our heat map key and we weren't able to successfully setup unit testing. The dials work for the most part (they are able to rotate and modify the values displayed in the numeric labels), but there is still room for improvement. Our parsing methods seem to draw the different knee bones quite well but the data seems random (An end-user is able to tell which bone they're looking at, but can't gain any useful info in terms of pressure being applied in different areas).

What we can improve on:

Collectively, the team agrees we still need to improve on starting sprint tasks sooner than we have been. and documenting our code (we want more in-line comments and it'd be nice to have a README built for an end-user to easily understand).

Overall performance:

The team feels this is our best sprint so far and we're steadily getting better at following the scrum process. We're actually pretty close to having a good "beta" for this project, there are definitely a few cleanup things for us to deal with but the overall appearance has a few modular things to add in before its truly at where the sponsor would like. Team communication and our willingness/ability to help one another when needed has stayed strong since the beginning of this project.

Team capacity and velocity:

Consistently, everyone has been assigned two user stories per sprint and it seems to be a realistic goal when we managed both our time and expectations. Most of the work was completed successfully but as indicated in the goal status, not all of the work was completed or fully implemented. Since the upcoming sprint is longer (Thanksgiving break) we're at least considering increasing the work load but also recognize it is break and given our past completion history we're leaning more towards staying at the current capacity and using the break as an opportunity to see if we can fulfill an entire sprint goal this time.

User Stories being carried over:

We will be carrying over user stories #83, #156 and #155.

• Stories Update fonts and text in app to be custom and responsive #156 and Add pressures to Heat Map key #155 are being carried over into Sprint 5 simply because the work wasn't completed.
• Story Update CI with unit Tests #83 is being carried into Sprint 5 because while tests can be run now, the tests themselves are not set up correctly and not ready to be added to the CI.