THE GUIDE
The Scrum Guide is a foundational document that provides the framework for implementing the Scrum methodology. It is authored by Jeff Sutherland and Ken Schwaber, the co-creators of Scrum. The guide is periodically updated to reflect the evolving understanding and best practices in Scrum. As of my last knowledge update in January 2022, I'll provide a general overview of the key elements typically found in the Scrum Guide:
Scrum Framework:
Describes the three key roles in Scrum: Scrum Master, Product Owner, and Development Team.
Outlines the five Scrum events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Introduces the three artifacts: Product Backlog, Sprint Backlog, and Increment.
Roles:
Scrum Master: The servant-leader for the Scrum Team, responsible for promoting and supporting Scrum.
Product Owner: Represents the stakeholders and ensures the value of the work done by the Development Team.
Development Team: Self-organizing and cross-functional, responsible for delivering potentially releasable increments of product.
Events:
Sprint: A time-boxed iteration during which a potentially releasable product increment is created.
Sprint Planning: A collaborative event where the Scrum Team plans the work to be performed during the Sprint.
Daily Scrum: A short daily meeting for the Development Team to synchronize activities and plan the next 24 hours.
Sprint Review: A meeting at the end of the Sprint to inspect the Increment and adapt the Product Backlog.
Sprint Retrospective: An opportunity for the Scrum Team to inspect itself and create a plan for improvements.
Artifacts:
Product Backlog: An ordered list of everything that is known to be needed in the product, maintained by the Product Owner.
Sprint Backlog: The set of Product Backlog items selected for the Sprint, plus a plan for delivering the product increment.
Increment: The sum of all the Product Backlog items completed during a Sprint, providing a potentially shippable product.
Values:
Commitment
Courage
Focus
Openness
Respect
Rules:
Definition of Done: A shared understanding of when work is considered complete and meets the quality standards.
The Scrum Guide serves as the authoritative reference for Scrum, guiding teams in their adoption and implementation. For the most up-to-date information, it is recommended to refer to the latest version of the Scrum Guide available on the official Scrum website.
