🔄 Agile & Scrum
Iterative delivery framework for product development.
Scrum roles
- Product Owner — Defines what to build, owns the backlog
- Scrum Master — Facilitates process, removes impediments
- Development Team — Self-organizing, cross-functional, delivers increments
Scrum ceremonies
| Ceremony | Duration | Purpose |
|---|---|---|
| Sprint Planning | 1-2h | Select and commit to sprint backlog |
| Daily Standup | 15min | Sync on progress, surface blockers |
| Sprint Review | 1h | Demo deliverables to stakeholders |
| Retrospective | 1h | Reflect and improve team process |
| Backlog Refinement | 1h/week | Clarify, estimate, and prioritize upcoming work |
Sprint mechanics
- Duration: 1-2 weeks (consistent across sprints)
- Velocity: average story points completed per sprint
- Definition of Done: shared checklist for "complete" work
- Sprint Goal: one clear objective per sprint
Agile principles (key ones)
- Working software over comprehensive documentation
- Responding to change over following a plan
- Individuals and interactions over processes and tools
- Deliver frequently — prefer shorter timescales
Anti-patterns to avoid
- Sprint scope changes mid-sprint
- No retrospective or ignoring retro actions
- Product Owner absent from sprint events
- Treating story points as hours
- Sprints without a clear sprint goal