Loading content
Scrum is an agile framework that helps teams manage complex projects efficiently. It is based on iterative and incremental approaches to promote flexibility and adaptability. Scrum defines specific roles, events, and artifacts that support a transparent and collaborative way of working.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Scrum is an agile framework that enables the development and ongoing stewardship of complex products through explicit accountabilities, events, and artifacts—bound together by rules.
Scrum was developed by Jeff Sutherland and Ken Schwaber. The Scrum Guide defines Scrum as a combination of accountabilities, events, artifacts, and the rules that bind them together; it is written and provided by Sutherland and Schwaber. The supplied material also states that Schwaber co-developed the Scrum process with Sutherland in the early 1990s.
Think of Scrum as a recurring sprint rhythm with a fixed timebox. Before each sprint, work is selected in Sprint Planning from the Product Backlog and carried into the Sprint Backlog. During the sprint, the Developers drive implementation, with the Daily Scrum supporting coordination. At the end of the sprint, an Increment is delivered and reviewed with stakeholders in the Sprint Review. After that, the team uses the Sprint Retrospective to improve collaboration and the way work is performed; the outcomes feed into the next sprint planning. Roles make sure product-direction decisions, delivery, and adherence to the Scrum structure are each clearly owned.
Scrum is not just a set of practices; it specifies rules that keep accountabilities, events, and artifacts together.
Work is organized into repeating timeboxes that include planning, execution, review, and adaptation.
Clear responsibility for product direction, delivery, and enabling/maintaining the Scrum structure.
Product and sprint transparency is provided via artifacts that anchor planning and control across the sprint.
Time-boxed events provide recurring inspection and coordination points within the sprint.
Scrum fits when you expect complexity in the product and need continuous, early feedback rather than relying on a single upfront plan. The framework delivers its intended effect only when the organization actually follows the integrated structure of roles, events, artifacts, and rules (for example, maintaining the sprint timebox, using the artifacts for transparency, and conducting real reviews). Trade-off: the fixed cadence and required stakeholder interaction increase coordination effort; without that discipline, Scrum can degrade into informal “agile-ish” project management.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.