Technical Journal - November - May / Technical Journal - November - May /
Production Release - Sprint #2 Part 2

The team ended up completing way fewer tasks this sprint then what was originally planned. This is due to external/personal situations that some members of the team needed to tend to before they could dedicate any time to the project this sprint. So, this time around the team's low velocity was, for the most part, out of the team's control, and wouldn't have happened had these external situations happened.

Capture.PNG.33

For now, it's best to move forward into our final sprint of the release and finish as many high-priority tasks as possible to give us time to carry out some user testing before we complete the Production release. However, our small workload last sprint means we each have a lot to do for this final sprint - we have 60.5 estimated hours of work to do within this last sprint.

Capture.PNG.34

Provided everything goes mostly smoothly, and the team completes tasks by the time they expect to, then we should be able to complete this workload efficiently and to the best of our ability.