Sprint 4 wrap up
Sprint 4 close on the 27th 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 all of the 7 planned PBIs:
- #66
- #24
- #22
- #17
- #10
- #9
- #8
Of which #66 was a task related to the development environment (CD) left from the previous sprint, and all the others were features and functionalities of the Website component.
All the closed PBIs, development tasks, and increment descriptions can be found in the changelog.md.
-
Merge Requests should have more documentation
- Action Point: add a detailed description of what the MR adds, including an engineering overview of what was done, and whether that MR is an intermediate merge of the branch or its final.
-
Merging branches to other branches without precautions
- Action Point: when merging a branch into another branch (other than the development branch), commits should be squashed to avoid cluttering future MRs with pointless commits.
- Continue making unit and feature tests to keep coverage high
- Continue with the effective task allocation and segmentation
- Continue to enforce linters, both locally and on the pipeline
On the 5th iteration it was agreed with the PO to implement the following 11 PBIs:
- #90
- #26
- #23
- #21
- #12
- #11
- #93
- #47
- #20
- #15
- #14
The total estimated effort is 20.
Given that on this iteration we estimated 20 effort points and implemented 20 effort points, we can make predictions about the final state of the project.
The current unimplemented items have a total estimated weight of 33. If we implement 20 effort points on the 5th iteration, we will be left with the equivalent of 13 effort points of unimplemented functionalities.
Thematically, our PBIs can be divided into class-related features and quality-of-life improvements, the former with 13 effort points and the latter with 20. Depending on how they are divided by the PO, and given that there is only one sprint left, either the QoL improvements will be implemented with no class features, or the class features will be implemented with just a few QoL improvements.
As said in the sprint planning, the route taken was to implement the QoL improvements and drop the class features. As such, the class-related features will not be implemented.
This was the fourth sprint burndown chart, which demonstrates how the development of the PBIs occurred over time.
The PBIs were mostly closed at the end of the sprint because to each team member was attributed just one PBI. All elements of the team has managed their time in order to finish his work until the sprint deadline.
