Scrum Pillars
Agile Scrum

Scrum Pillars

Scrum events provide space for inspection and adaptation, enabling the transparency required, which are three pillars of Scrum.
Read more
Get PDF
Tags
3 pillars of scrum Adaptation image Infographic Inspection pillars of scrum Poster Scrum Scrum Events Scrum overview Scrum pillars scrum pillars poster Scrum process framework three pillars of scrum Transparency what are the three pillars of scrum
Article

Scrum Pillars


Scrum combines four formal events, implementing the empirical Scrum pillars of transparency, inspection, and adaptation, and a containing event, the Sprint. These events are opportunities to inspect and adapt Scrum artifacts designed to enable the transparency required.

Transparency

Processes and work must be visible for both the scrum team and stakeholders. The low transparency artifacts can lead to risk increase and value decrease. The key to transparency is a common understanding of what is being inspected.


Inspection

The artifacts and the progress must be inspected frequently and diligently, however it should not get in the way of the work. An inspection enables adaptation, without which is pointless.


Adaptation

If the Scrum Team finds any aspects of a process deviate outside acceptable limits it is expected to adapt accordingly to minimize deviations. With a lack of empowerment and self-management, adaptation is becoming more difficult.


Scrum framework overview
Resources
scrumguides.org scrum.org agilistix.com medium.com

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.