HeaderSIS.jpg

IS480 Team wiki: 2013T2 Five&AHalfMen Project Management Metrics Sprints Burndown

From IS480
Jump to navigation Jump to search

Five&ahalfLogo.png


Home   Project Overview   Project Management   Documentation   The Team
Schedule Risks Metrics Resources Learning Outcomes
Product
Backlog
Sprints
Burndown
Bug
Metrics
Manhours
Overview


Sprints Metrics


Burndown Metrics Table

5.5burndownmetricstable.png




Released Sprints Burndown

Sprint Burndown Chart Description
1

5.5Sprint1burndownchart.png

Initial transiting period from iterative to SCRUM PM framework & preparing for Acceptance

2

5.5Sprint2burndownchart.png

Team was still accustoming from the transition from iterative to SCRUM PM framework, plus it was final project deadline & exam period

3

5.5Sprint3burndownchart.png

Expected

4

5.5Sprint4burndownchart.png

More complicated, we underestimated client's data validation process & the accompanying technical planning before starting on the relatively complex Data Validation Engine tasks In addition due to lack of manpower, 4 member's trip to Bali inclusive of visiting client's field operations, another member was still on BSM trip

5

5.5Sprint5burndownchart.png

A team member was out of town for 10 days, scheduling of sprint backlog avoided complex mobile related tasks. In addition, because of the festive seasons, team members deserve a break for family & girlfriend time although it was considered disruptive for the project's progress

6

5.5Sprint6burndownchart.png

Expected especially when it was the start of the semester where every team member is in town & have relatively more time to take in more function-module tasks

7

5.5Sprint7burndownchart.png

Expected despite the Chinese New Year festive season

8

5.5Sprint8burndownchart.png

In view of having our Local UT within this sprint & prepping for it, less time-consuming function-module tasks are put into this sprint's backlog

9

5.5sprint9burndown.png

Velocity got higher after mid-sprint in view of preparations for midterm presentation (27th February).

10

5.5sprint10burndown.png

We were still recuperating from mid-terms & a few members were still having mid-term project milestones

11

5.5sprint11burndown.png

Allocated lesser work for this sprint in view of project milestones, which also explains our velocity for the entire sprint.

12

5.5sprint12burndown.png

Still bogged down by other module’s projects, where after mid-sprint we managed to regain our velocity.