24 June 2024

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

Scrum framework rules

  • Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
  • 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

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

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

Developers rules

Scrum Master rules

Scrum events rules

Scrum framework

More informations for the Scrum PSD certification here.

Updated : 03/09/2021

Leave a Reply

Your email address will not be published. Required fields are marked *