Scrum
Definition
Scrum is a lightweight agile framework for delivering value in complex environments through short iterations, shared goals, and frequent inspection and adaptation. It structures work into timeboxed sprints and relies on cross-functional teams to plan, build, review, and improve continuously.
Core Ideas
Scrum Theory
The source notes highlight three central ideas:
- transparency — work, goals, and responsibilities should be visible
- inspection — progress and outcomes should be reviewed frequently
- adaptation — teams should change course based on what they learn
Sprints
A sprint is the core Scrum container:
- usually 1 to 4 weeks
- intended to produce a potentially shippable increment
- repeated as a regular delivery rhythm
Key Accountabilities
- Product Owner — prioritizes value, shapes backlog direction, and protects focus on the most important work
- Scrum Master — facilitates ceremonies, coaches the team in Scrum, and removes impediments
- Developers / Development team — cross-functional people who build and deliver the increment
Main Ceremonies
- Sprint Planning — decide what to take into the sprint and how to approach it
- Daily Scrum — short coordination loop around progress, next steps, and impediments
- Sprint Review — show outcomes to stakeholders and gather feedback
- Retrospective — reflect on the process and improve it
- Backlog Refinement / Grooming — prepare future work by clarifying and resizing items
Key Artifacts
- Product Backlog — prioritized list of desired work
- Sprint Backlog — items committed for the current sprint
- User Stories — small, user-centered expressions of need
- Acceptance Criteria — testable conditions for success
- Definition of Done — shared standard for what it means for work to be complete
- Product Increment — usable output created during the sprint
Benefits
- creates a regular delivery cadence
- makes work and blockers visible
- encourages continuous learning and adjustment
- supports strong collaboration in cross-functional teams
Trade-Offs
- can become overly ceremonial if the team loses sight of the underlying goals
- requires real product ownership and disciplined refinement
- may feel heavy for tiny or highly interrupt-driven teams
Relationships
- Agile — Scrum is one of the most common agile frameworks
- Kanban — Kanban offers a flow-based alternative to sprint-based work management
- Scrumban — Scrumban blends Scrum rhythms with Kanban flow and WIP discipline
- RACI Model — RACI can clarify responsibility in larger projects, though rigid matrices may fit Scrum teams poorly
- Work Culture & Management — Scrum is a major operating model in the work-culture notes
- Agile and Team Processes — broader comparison of Scrum with adjacent team-process models
- Respect Over Diversity — Respect as a Scrum value, argued against diversity-as-headcount