Sprint Timeline Overview
Day 1: Planning
→
Days 1-8: Development
→
Days 8-10: QA Testing
→
Day 10: Review
→
Day 10: Retro
Sprint Planning (Day 1)
| Aspect |
Details |
| Duration |
2-4 hours |
| Attendees |
PO, Functional Lead, Technical Lead, Scrum Master, PC, Dev Team, QA |
Agenda
- PO presents prioritized backlog items with completed designs and PRDs
- Team discusses technical approach and identifies dependencies
- Stories broken into tasks and estimated (story points)
- Team commits to Sprint Goal and Sprint Backlog
- Capacity confirmed (accounting for PTO, meetings)
Definition of Ready (DoR)
- PRD approved with objectives, use cases, and user stories
- Acceptance criteria defined for each story
- UX/UI designs complete and reviewed
- Dependencies identified
- Story sized (under 8 points, otherwise split)
Keep planning focused. If a story is well-defined, don't over-discuss. Move on.
Daily Standup
| Aspect |
Details |
| Duration |
15 minutes (strict timebox) |
| Frequency |
Every day |
| Attendees |
Scrum Master, PC, Dev Team, QA |
Format
Each team member answers:
- What did I complete yesterday?
- What will I work on today?
- Any blockers?
Rules: Start on time, timebox strictly. Detailed discussions taken offline. Scrum Master tracks and resolves blockers.
Development Workflow
To Do
→
In Progress
→
Code Review
→
Ready for QA
→
QA Testing
→
Done
Development Standards
- Feature branches from main/develop
- Pull requests require 1-2 approvals
- Automated tests required (unit, integration)
- CI pipeline must pass before merge
- Domain expert review for critical modules (payroll, billing)
Backlog Refinement (Mid-Sprint)
| Aspect |
Details |
| Timing |
Mid-sprint (Day 4-5) |
| Duration |
1-2 hours |
| Purpose |
Prepare items for NEXT sprint |
| Attendees |
PO, Scrum Master, PC, Dev Team, QA |
Agenda
- Review upcoming backlog items
- Clarify requirements, review designs
- Initial estimation and story splitting
- Identify technical spikes needed
QA Process
Continuous Testing (During Sprint)
- QA begins testing as features complete
- Test cases written during refinement/planning
- Automated regression suite maintained
- Bug fixes prioritized within sprint
End-of-Sprint Testing (Days 8-10)
- Full regression testing
- Cross-browser/device testing
- Performance validation
- Sign-off on sprint deliverables
Sprint Review/Demo (Day 10)
| Aspect |
Details |
| Duration |
1-2 hours |
| Attendees |
PO, Functional Lead, Technical Lead, Scrum Master, Team, Stakeholders |
Agenda
- Demo completed features
- Stakeholder feedback captured
- PO accepts/rejects stories based on acceptance criteria
- Backlog adjustments discussed
Sprint Retrospective (Day 10)
| Aspect |
Details |
| Duration |
1 hour |
| Attendees |
Scrum Master, PC, Dev Team, QA (PO optional) |
Format
- What went well? - Celebrate successes
- What needs improvement? - Identify pain points
- Action items - Concrete improvements for next sprint
Output: 2-3 actionable improvements for next sprint with owners assigned.
Definition of Done (DoD)
- Code complete and peer reviewed
- Unit tests written and passing
- Integration tests passing
- QA tested and approved
- Documentation updated
- Deployed to staging environment
Sprint Metrics
Velocity Tracking
Track story points completed per sprint to improve forecasting.
- Measure: Total story points completed (not started)
- Trend: Track 3-sprint rolling average
- Use for: Sprint planning capacity, release forecasting
Key Metrics
| Metric |
What It Shows |
Target |
| Velocity |
Team throughput |
Stable trend |
| Commitment vs Delivered |
Planning accuracy |
>85% |
| Burndown |
Daily progress |
On/below line |
| Escaped Defects |
Quality |
Decreasing |
Metrics are guides, not goals. Don't game velocity. Focus on sustainable delivery.
Next Phase
Items that meet DoD proceed to
Release Process for UAT regression testing and production deployment.