Alpha Analytics
Sprint burndown charts, velocity tracking, and progress metrics for agile teams
Analytics
The analytics page provides insights into team performance and sprint execution. Use these metrics to improve estimation accuracy, identify bottlenecks, and maintain a sustainable pace.
Sprint Burndown
The burndown chart tracks remaining work throughout the active sprint.
graph TD
A[Sprint Start] --> B[Ideal Burndown Line]
A --> C[Actual Remaining Work]
B --> D[Sprint End: 0 remaining]
C --> E[Actual completion point]The chart plots two lines:
- Ideal burndown -- a straight line from total story points at sprint start to zero at sprint end
- Actual burndown -- the real remaining story points, updated as tasks move to DONE
Reading the Burndown
| Pattern | Meaning |
|---|---|
| Actual tracks ideal | Sprint is on pace |
| Actual above ideal | Behind schedule; work is completing slower than planned |
| Actual below ideal | Ahead of schedule; may have capacity for additional work |
| Flat sections | No tasks completed during that period; potential blocker |
| Sudden drops | Large tasks completed or scope removed |
Velocity Chart
Velocity measures the amount of work completed per sprint, expressed in story points.
The velocity chart shows:
- Completed story points per sprint (bar chart)
- Rolling average across the last several sprints (trend line)
- Committed vs. completed to show planning accuracy
Using Velocity for Planning
- Use the rolling average to estimate how many story points the team can handle in the next sprint
- If velocity is declining, investigate causes (scope creep, blockers, team changes)
- Avoid comparing velocity between teams; it is a team-specific metric
Progress Tracking
By Status
A breakdown of all tasks in the current sprint by status:
| Status | Count | Percentage |
|---|---|---|
| TODO | -- | -- |
| IN_PROGRESS | -- | -- |
| IN_REVIEW | -- | -- |
| DONE | -- | -- |
By Type
See the distribution of work across task types (Task, Bug, Story, Improvement, Ticket Escalation) to understand where effort is being spent.
By Assignee
View workload distribution across team members. Identify if work is unevenly distributed so it can be rebalanced.
Sprint Reports
After a sprint is completed, a sprint report is generated summarizing:
- Committed items -- what the team planned to deliver
- Completed items -- what was actually finished
- Incomplete items -- what was carried over or returned to the backlog
- Scope changes -- tasks added or removed mid-sprint
- Velocity -- total story points completed