M4 - Burndown and Velocity Charts

Sprint Management Overview

Schedule Tracking

• Team Status:

  • Ahead of Schedule

  • Behind Schedule

• Total Work Tracking:

  • Monitor total work remaining (measured in story points and issue counts) against the time available in a sprint.

Burndown Chart

• Definition: Used to track the work remaining in a sprint over time.

• Application: Helps visualize progress and identify whether the team is on track.

• Date of Reference: 12/26/2024

• Attribution: W.P. Carey Information Systems, Louise Tung

Sprint Velocity

Definition

• Sprint Velocity:

  • Measures a team's future capacity based on the average story points completed in past sprints.

Calculation

• Formula:

  • Team Velocity = Total Story Points Completed / Total Sprints Completed

Jira Velocity Chart

Example Calculation

• Story Points Completed in Sprints:

  • Sprint 1: 13

  • Sprint 2: 10

  • Sprint 3: 17

  • Sprint 4: 26

  • Sprint 5: 23

• Total Story Points: 13 + 10 + 17 + 26 + 23 = 89

• Total Sprints: 5

• Average Velocity Calculation:

  • Average Velocity = Total Story Points Completed / Total Sprints Completed

  • Average Velocity = 89 / 5 = 17.8 (rounded to 18)

Product Backlog and Task Selection

Task Prioritization

• Tasks Listed:

  • Task A, Task B, Task C, Task D, Task E, Task F, Task G, Task H, Task I, Task J, Task K, Task L, Task M

• Priorities and Story Points:

  • Must Have, Should Have, Could Have, Won't Have

  • Example Story Points:

    • Task A: 3

    • Task B: 7

    • Task C: 9

    • ...

    • Task M: 6

• Team Average Velocity: 15 story points

Sprint Task Selection Criteria

• Selection Factors:

  • Average team capacity (velocity)

  • Task priority

  • Story points estimation

  • Task dependencies

User Stories

• Definition: Requirements expressed from the standpoint of an end user.