Scrum
Version 1.0.0 · Updated 2026-07-28
CORE DEFINITION
A concrete framework within agile development. It manages complex projects through short iterative cycles (Sprints), daily stand-up meetings, fixed roles (such as Scrum Master), and artifacts (such as the product backlog). Scaffold role: an execution framework for uncertainty. Unlike traditional waterfall management, Scrum accepts that requirements change, and through frequent delivery and feedback loops it lets a team adapt quickly while keeping output stable.
SCAFFOLDING EFFECT
Reduce cognitive load
- Handle uncertainty: accept that requirements will change and plan for adaptation instead of locking the plan. - Short feedback loops: deliver in Sprints and use daily stand-ups to surface blockers early. - Clear roles and artifacts: separate the product backlog from the sprint backlog to keep priorities visible.
Anchor fast decisions
An iterative framework that uses fixed short sprints, roles (PO/SM/team), and ceremonies (stand-ups, reviews, retrospectives) to achieve transparency, inspection, and adaptation. It structures complex work.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Scrumverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS