Sprint 3 wrap up
Sprint 3 close on the 14th November 2018. We reunited with the Product Owner face to face in order to demonstrate our improvements over the previous sprint and to to fully close the iteration and in order to plan for the next one, which started on the next day.
We fully implemented 5 out of 6 PBIs:
- #67
- #65
- #56
- #55
- #18
Of which #18 was a new feature, and all the others tasks were related to development. All PBIs were approved by the PO.
The following PBI was not fully implemented: #66.
We have decided, together with the PO, to move it into the next sprint with the revised effort of 1, as it is almost fully done.
All the closed PBIs, development tasks, and increment descriptions can be found in the changelog.md.
- The CI pipeline is robust and added value to the development process
- Linters and coverage reports are now available to every development branch
- Both the team and the PO continue with increased satisfaction about the work done
- We made proper use of the burndown chart, and now it reflects the actual development
- Our coverage metrics improved even more than they did on the previous iteration
- Iterations should be closed on a more timely fashion by both us and the PO.
- The effort for the PBIs should not be underestimated again.
On the 4th iteration we plan to implement the following 6 PBIs, all of which related to the Web component of the project:
- #10
- #9
- #17
- #8
- #22
- #24
We also plan to finalize item #66, which was left from the previous sprint, and which has a new revised effort value of 1.
The total estimated effort is, once again, 20.
Given that on this iteration we estimated 20 effort value and implemented 19, we can make predictions about the next iterations.
The current unimplemented items have a total estimated weight of 53. If we implement 19 effort points in the 4th and 5th iterations each, we will fall short of 15 effort points (53 - 19 - 19).
Therefore, we predict that we will fully implement the basic features of the project as originally proposed, but will not implement some of the quality-of-life improvements proposed or the features related to classes.
This was the third sprint burndown chart, which demonstrates how the development of the PBIs occurred over time.
