(Supplements core Scrum)

Synopsis

Throughout the Sprint, the Scrum Master and the entire development team monitor the Sprint progress.

Value 

Monitoring Sprint progress helps the team understand if they will be able to deliver what they committed to and to take corrective action sooner rather than later. Reports such as burndown charts, progress bars, and dashboard widgets, help the team get real-time status from a single source of truth.

Steps

The Scrum Master ensures that the entire team knows how to monitor Sprint progress following these steps.

1. Review overall progress

How many story points have been completed compared with the total required for the Sprint? 

How many task hours have been completed compared with the total estimated task hours for the Sprint?

2. Review Sprint Burndown

The trend shown by the Sprint Burndown chart indicate if the Sprint is on track. Concerns with the Sprint Burndown should be discussed with the team.

3. Review work items needing attention 

• Ensure all development tasks have a parent story.
• Ensure all development tasks have an estimate. 

Fix inconsistencies (or ask someone else).

Note that tasks assigned to non-development team members (Scrum Master, Product Owner, Project Area Administrator) will typically not have a parent story or an estimate.

4. Review and update impediments and risks

The Scrum Master should regularly review, address, and update impediments and risks.

5. Review  blocked work items

For each blocked work item, review the blocking work items. Work with the team to resolve the blocking work item.

6. Review team member task assignments 

Examine unassigned tasks to determine if they should be assigned.

7. Review stories in progress

Make sure that the team is working on the stories with the highest business value.