Sprint 3: Revenue Dashboard
Calculate revenue at risk and build the executive dashboard view with key churn, revenue-risk and filtering features.
17 July to 24 July
Sprint 3 focused on calculating revenue at risk and building the main executive dashboard view for the SaaS churn analysis project.
| Jira ID | Story | Status | Story Points |
|---|---|---|---|
| SCRUM-14 | Calculate revenue at risk | Done | 3 |
| SCRUM-15 | Build executive dashboard view | Done | 3 |
| SCRUM-16 | Add dashboard filters | Done | 2 |
During Sprint 3, the financial impact of churn was analysed through monthly and annual revenue-at-risk calculations. This helped translate customer churn into business impact for revenue and leadership stakeholders.
The sprint also focused on building the executive dashboard view, including KPI cards, churn visuals, revenue-risk visuals and filters. The dashboard was designed to support clear stakeholder decision-making rather than technical reporting only.
Sprint 3 was completed successfully. All 3 planned stories were moved to Done in Jira, completing 8 out of 8 planned story points.
- Churn analysis was connected to revenue impact.
- The dashboard structure focused on executive-level decision-making.
- Filters improved stakeholder exploration of churn and revenue risk.
- The sprint created a strong visual reporting layer for the project.
- Dashboard wireframes could be created earlier before building visuals.
- Revenue-at-risk assumptions should be reviewed with stakeholders before final use.
- More user testing could improve dashboard clarity and usability.
This sprint showed that analytics becomes more valuable when technical findings are translated into financial and business impact. Revenue-at-risk analysis helps stakeholders understand why churn matters and where action should be prioritised.
Sprint 3 completion screenshot: 06-sprint-3-completed.png
