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?

Review the progress bars in the Sprint plan.

• Click Plans > All Plans >[Sprint name]
• Click Plan Details
• Click Progress

See Load, Progress, and Burndown reports in the Plan Details.

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.

Display the team dashboard:

• Click Project Dashboards > All [Project name] Dashboards > [Team Name]

Click the Scrum Master tab to view the Sprint Burndown chart.

The Burndown chart is explained in Checking project status by iteration. 

The Expected Complete line should be close to the Ideal line.  If the Sprint is behind, the Expected Complete line will be steeper than the Ideal line.  The Planned Work line shows changes in estimated task hours through the sprint. This occurs if the team corrects initial estimates, or if additional tasks were added to the Sprint.

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) may not have a parent story or an estimate.

On the Scrum Master tab, in the Work Items Needing Attention widget:

• Click the Tasks without a parent query. A table with all tasks without a parent story appears
• Click the Tasks without Estimates query. A table with all tasks without an estimate appears

4. Review and update impediments and risks

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

View the Scrum Master tab, Open Impediments and Open Risks widgets.

Click on and update risks and impediments as needed.

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.

View the Development Team tab Blocked Work Items widget.

Hover over the blocked tasks to display the details.

In the Quick Information area, hover over the work item number next to Depends On to view the name of the related blocker.

6. Review team member task assignments 

Examine unassigned tasks to determine if they should be assigned.

View the Development Team tab Work Items by Owner widget.

7. Review stories in progress

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

On the Development Team tab:

• The Stories In Progress (current sprint) and Stories Closed (current sprint) widgets show the stories in a bar chart distributed on business value.