-
-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint 5 wrap up
Sprint 5 closed on the 12th December 2018. We had a meeting with the Product Owner face to face in order to demonstrate our final delivery of the product as well as to show the improvements over the previous sprint and to to fully close the this final iteration.
We fully implemented all of the 12 planned PBIs:
- #11
- #12
- #14
- #15
- #20
- #21
- #23
- #47
- #90
- #93
- #26
- #94
All the closed PBIs, development tasks, and increment descriptions can be found in the changelog.md.
- Acceptance test in the web development part of the project should be behaviour driven
- Action Point: start integrating frameworks like Laravel Dusk
- We believe that in this sprint everything went smoothly other than some planned problems
- Continue making unit and feature tests to keep coverage high
- Action Point: Creating Unit Tests
- Continue with the effective task allocation and segmentation
- Action Point: Split tasks equally
- Continue to enforce linters, both locally and on the pipeline
- Continue creating good documentation for the Merge Requests that create big changes on the developing environment
On a future 6th iteration the following 5 PBIs are the main implementation focus:
- #27
- #28
- #29
- #30
- #31
The total estimated effort is 13.
Given that, as always, 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 PBIs are all related to the class features and have a total estimated weight of 13, which, as predicted, will not be done as there are no more iterations. If we had an hypothetical 6th iteration, with the usual planned weight of 20, the project would be completely done.