The Scrum framework : rules

The Scrum framework consists of Scrum Teams and their associated accountabilities, artifacts, events and rules as defined in the Scrum Guide.

Scrum Guide rule

• The Scrum Guide contains the definition of Scrum.

Scrum framework rules

• Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
  • According to the Scrum Guide, mandatory rules and Principles of Scrum are Scrum Accountabilities, Scrum Events, Sprint Goal, Product Backlog, Sprint Backlog, Increment, Definition of Done (DoD), and Monitoring progress in Sprint and Project levels.
  • Other things are practices that could employ in the Scrum framework and are up to the team and project and are not mandatory.
• Scrum exists only in its entirety, because Scrum is a framework, and functions well as a container for other techniques, methodologies, and practices.
  • Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum.
  • The Scrum framework, as outlined herein, is immutable.
  • While implementing only parts of Scrum is possible, the result is not Scrum.
  • Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
• As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in the Scrum Guide, may be found, applied and devised.

Scrum usage rule

• Various processes, techniques and methods can be employed within the framework.
  • Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses.
  • Such tactics for using within the Scrum framework vary widely and are described elsewhere.

Scrum and practices rules

• Scrum wraps around existing practices or renders them unnecessary.
• Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.

Transparency, Inspection and Adaptation rules

• Transparency enables Inspection.
  • Inspection without Transparency is misleading and wasteful.
• Inspection enables Adaptation.
  • Inspection without Adaptation is considered pointless.
• Adaptation becomes more difficult when the people involved are not empowered or self-managing.
• A Scrum Team is expected to adapt the moment it learns anything new through Inspection.
  • The adjustment must be made as soon as possible to minimize further deviation.

Sprint rules

• No changes are made that would endanger the Sprint Goal;
• Quality does not decrease;
• The Product Backlog is refined as needed; and Scope may be clarified and renegotiated with the Product Owner as more is learned.

Increment rules

• The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
  • In order to provide value, the Increment must be usable.
• Work cannot be considered part of an Increment unless it meets the Definition of Done (DoD).

Scrum Team rule

• A core Scrum Team is small and has no sub-teams,
  • Within a Scrum Team, there are no sub-teams or hierarchies.
• The Scrum Team as a whole is accountable for the delivery,
  • The Scrum Team is empowered,
  • The Scrum Team is working as autonomous as it is possible,
  • The Scrum Team is self-organizing,
  • The skills within the Scrum Team are balanced,
  • Team members share the same norms and rules,
• Ideally Scrum Team members :
  • Are dedicated to their teams with 100% capacity,
  • Are collocated, and share the same room.
• If there are multiple Scrum Teams working together on a Product, they must mutually define and comply with the same Definition of Done (DoD).

Product Owner rules

• The Product Owner is accountable for maximizing the value of the product resulting from the work of
  the Scrum Team.
  • The Product Owner is also accountable for effective Product Backlog management.
• For Product Owners to succeed, the entire organization must respect their decisions.
  • The Product Owner is one person, not a committee.
  • Only the Product Owner has the authority to cancel the Sprint.

Developers rules

• Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
• The Developers are required to conform to the Definition of Done (DoD).

Scrum Master rules

• The Scrum Master is accountable for the Scrum Team’s effectiveness.
• The Scrum Master must be a servant leader.

Scrum events rules

• Each event in Scrum is a formal opportunity to Inspect and Adapt Scrum artifacts.
  • Scrum events are designed to provoke change.
• Optimally, all events are held at the same time and place to reduce complexity.
• The Daily Scrum is a 15-minute event for all the Developers of the Scrum Team.
• The Sprint Retrospective concludes the Sprint.
• The Sprint Review should never be considered a gate to releasing value.

Scrum framework

More informations for the Scrum PSD certification here.

Updated : 03/09/2021