This is a simulated Agile delivery case study showing how a SaaS customer churn and revenue-at-risk dashboard can be planned and managed using Scrum, Jira and business analysis artefacts.
The project demonstrates how a Business Analyst or Agile Delivery Analyst can translate a business problem into stakeholder requirements, user stories, acceptance criteria, sprint plans and delivery documentation.
A SaaS business needs to understand customer churn, identify high-risk customer segments and quantify recurring revenue exposure.
The dashboard is designed to support decision-making for Customer Success, Revenue Operations, Product and Executive stakeholders.
Business Analyst / Agile Delivery Analyst
- Business Analysis
- Agile Delivery
- Scrum
- Jira
- Stakeholder Requirements
- User Stories
- Acceptance Criteria
- Product Backlog Management
- Sprint Planning
- Story Point Estimation
- Sprint Review
- Retrospective Documentation
- Dashboard Delivery Planning
- Analytics Project Management
| File | Description |
|---|---|
01-project-charter.md |
Defines project goal, business problem, stakeholders and delivery scope |
02-stakeholder-requirements.md |
Documents stakeholder needs, functional requirements and success criteria |
03-epics-and-backlog.md |
Defines epics and product backlog items |
04-user-stories-acceptance-criteria.md |
Converts requirements into user stories and acceptance criteria |
05-sprint-plan.md |
Plans four one-week Agile sprints |
06-jira-board-setup.md |
Documents Jira board setup, issue types and workflow |
07-jira-issue-list.md |
Lists Jira epics, stories, sprint planning and screenshot evidence |
08-sprint-1-review-retrospective.md |
Sprint 1 review and retrospective |
09-sprint-2-review-retrospective.md |
Sprint 2 review and retrospective |
10-sprint-3-review-retrospective.md |
Sprint 3 review and retrospective |
11-sprint-4-review-retrospective.md |
Sprint 4 review and retrospective |
12-final-project-summary.md |
Final project summary and portfolio relevance |
| Sprint | Focus | Story Points | Status |
|---|---|---|---|
| Sprint 1: Requirements | Stakeholder requirements and success criteria | 6 | Completed |
| Sprint 2: Data Churn | Data preparation, validation and churn analysis | 11 | Completed |
| Sprint 3: Revenue Dashboard | Revenue-at-risk analysis and dashboard build | 8 | Completed |
| Sprint 4: Testing Delivery | Dashboard validation, recommendations and retrospective | 8 | Completed |
The project includes Jira screenshots showing:
- Epics created
- User stories created
- Backlog structure
- Sprint planning
- Sprint completion evidence
Screenshots are stored in:
jira-board-screenshots/
This project demonstrates an end-to-end Agile delivery workflow for an analytics dashboard project. It shows how requirements are gathered, work is structured, Jira is used for delivery tracking and sprint-based progress is documented.
This project is relevant for roles such as:
- Business Analyst
- Agile Business Analyst
- Data Analyst
- BI Analyst
- Analytics Consultant
- Product Analyst
- Junior Scrum Analyst
- Strategy and Analytics Analyst
This is a simulated portfolio project created for learning and demonstration purposes. It does not represent a real client engagement or confidential business project.