During a sprint, an ideal curve is plotted against which the user stories need to be closed in the sprint to account for points delivered. Stories need to be closed against the team’s ‘Definition of Done’. The actual closing rate is plotted against the ideal. The team should inspect this on a daily basis to ensure that problems of not meeting sprint deliverables are addressed.

The Sprint report in this framework compares velocity against Story points. Velocity is the total of all closed and resolved issue’s story points. Story points are for all stories that are still in an open status based on the filter selected.

Responsibility to generate & distribute: Team
Frequency: Daily Review

Tabled Sprint Progress
Sprint Progress

The report can be filtered by Year, Month, Week, Day, Project Name, Project Release and Company Product / Service.

Sprint Progress Graph will give detail by number of velocity and Total story points

View 1

Total Story Points = 3421

Story points 3421

Velocity = 2289

Velocity 2289

View 2

Sprint view 2

Why is this important? 2 reasons:

    • The further the variance between total Story Points and Velocity, the bigger your backlogs are growing, which indicates that the amount of work coming is not being delivered quickly enough
    • It could also indicate that Product Owners are not on top of their backlogs