This is a team-level dashboard.
It answers:
How is the team doing right now, and what should we act on today or this sprint?
1. Sprint progress
This shows whether the team is on track to complete the sprint goal.
| Question | Example metric |
|---|---|
| Are we on track? | Sprint burndown |
| How much work is left? | Remaining story points / tasks |
| Are stories moving to Done? | Completed vs remaining work |
| Is the sprint goal at risk? | Sprint goal status |
Teaching line:
Sprint progress tells the team whether the current sprint is moving toward completion.
Example:
Burndown line is above ideal → more work remains than expected → team may be behind.
2. Quality
This shows whether the team is delivering good work, not just fast work.
| Question | Example metric |
|---|---|
| Are defects increasing? | Open bugs / escaped defects |
| Are tests passing? | Test pass rate |
| Is code maintainable? | Code quality / static analysis |
| Is work truly Done? | DoD compliance |
Teaching line:
Quality tells the team whether completed work is reliable, usable, and maintainable.
Example:
Velocity is high, but escaped defects are also high → team may be moving fast but not building quality in.
3. Blockers
This shows what is preventing the team from finishing work.
| Question | Example metric |
|---|---|
| What is stuck? | Blocked items |
| Where is work waiting? | WIP by column |
| Who needs help? | Blocker owner |
| What needs escalation? | Blocker age |
Teaching line:
Blockers show where the team needs to swarm, help each other, or escalate.
Example:
Three stories are waiting for API access from another team → dependency blocker.
4. Team health
This shows how sustainable and healthy the team is.
| Question | Example metric |
|---|---|
| Is workload reasonable? | Capacity vs commitment |
| Is morale okay? | Team satisfaction survey |
| Is the team overloaded? | WIP, overtime, unfinished work |
| Is collaboration working? | Retrospective feedback |
Teaching line:
Team health shows whether the team can continue delivering sustainably.
Example:
Team completed the sprint, but everyone worked overtime and satisfaction dropped → delivery may not be sustainable.
Simple classroom explanation
“A team dashboard is not mainly for executives. It helps the Agile team inspect and adapt during the sprint. It shows sprint progress, quality, blockers, and team health so the team knows what to fix next.”
Best short explanation
Team dashboard = daily/sprint-level decision dashboard. It helps the team see whether work is progressing, quality is good, blockers need attention, and the team is healthy enough to keep delivering.
REF: ChatGPT/AI Tools
