This repository has been archived by the owner on Jan 30, 2023. It is now read-only.
Sprint 5 Retrospective #282
katerosenthal
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sprint 5 Goal
The goals for Sprint 5 were to:
Did We Meet This Goal
We were able to complete all of these goals this sprint other than having the parameters affect the drawn image. Based on feedback from our sponsor, the calculations for how the parameters actually affect the data is way too complex, so if anything was implemented for that, it would just be a placeholder for now. There is also still a bit of cleaning up and documenting code to do, but overall, this goal was met, too.
What We Can Improve On:
Although there will not be another sprint, we did struggle rather heavily with time management this sprint due to a combination of the break, travel, and large assignments also due in other courses. If we were to have one more sprint, we could greatly improve upon that and endeavor to complete work sooner than the week/weekend before it is due.
Overall performance:
The team did really well with completing tasks and communicating about pieces of the project that had multiple people working on different pieces of them or that influenced other sections of work. There was some delay on starting work, and some tasks could not be started sooner because they relied on other tasks to be completed, but this was overall a very good sprint for the team.
Team capacity and velocity:
Once again, everyone was assigned two user stories per sprint because this has seemed to be our limit in the past. It is a realistic measurement of what we have been able to complete, and that remained true this sprint. There were, however, a few more tasks per story this sprint, so overall, our capacity was slightly greater than in past sprints.
Items left incomplete:
#83 - Unit tests were not written. Code was tested by hand using many console log statements and referencing the actual data files.
#216 - The sponsor was unable to provide calculations that would make this feature functional or useful, so for now it is just a framework put in place for future teams to build on if they are given a way to calculate this.
Known Bugs:
We are aware of a bug that currently causes the heat map to be drawn in just one color as of the end of this sprint. It is related to changes in the way the image is drawn and the recalculateHeatmapForces() function which was created before these changes. We believe we already have a fix figured out that will be implemented before the project handoff.
Beta Was this translation helpful? Give feedback.
All reactions