Scrum Roles
| Role | Responsibility |
|---|
| Product Owner | Owns the backlog, prioritizes work, represents stakeholders |
| Scrum Master | Facilitates process, removes blockers, coaches the team — NOT a project manager |
| Development Team | Self-organizing, cross-functional — 3-9 people who build the product |
Scrum Ceremonies
| Ceremony | Duration | Purpose |
|---|
| Sprint Planning | 2-4 hours (2-week sprint) | Select backlog items, define sprint goal |
| Daily Standup | 15 min max | What did you do? What will you do? Any blockers? |
| Sprint Review | 1-2 hours | Demo working software to stakeholders — get feedback |
| Retrospective | 1-1.5 hours | What went well? What didn't? What will we change? |
Artifacts
| Artifact | What It Is |
|---|
| Product Backlog | Ordered list of everything needed — maintained by Product Owner |
| Sprint Backlog | Items selected for this sprint + plan for delivering them |
| Increment | Sum of all completed backlog items at sprint end — must be "Done" |
Definition of Done
| Must include: |
|---|
| ☐ Code reviewed by at least one teammate |
| ☐ Unit tests written and passing |
| ☐ Integration tests passing |
| ☐ Documentation updated |
| ☐ Deployed to staging and verified |
| ☐ Acceptance criteria met and demo-ready |
Pro Tip: The standup is NOT a status report for the manager — it's a coordination meeting for the team. If your standups feel like reporting to the boss, you're doing Scrum wrong. The Scrum Master should facilitate, not interrogate.