Scrum Guide
The official Scrum framework by Schwaber & Sutherland — roles, events, artifacts.
PURPOSE
Software development teams and increasingly other departments need a lightweight framework to tackle complex work iteratively and incrementally. The Scrum Guide defines the rules for Scrum so teams can work in a self-organized manner, deliver regularly, and continuously improve. It establishes transparency, inspection, and adaptation as core principles.
HOW TO USE
Teams work in fixed time boxes (sprints of 1-4 weeks) in which they create a potentially shippable product increment. The Product Owner prioritizes the Product Backlog, the team plans work in Sprint Planning, and synchronizes in the Daily Scrum. At the end, there is a Sprint Review (inspecting results) and Sprint Retrospective (improving the process).
WHAT IT IS
The Scrum Guide is the official rulebook for the Scrum framework, authored by Ken Schwaber and Jeff Sutherland. It defines three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). The framework is built on the pillars of Transparency, Inspection, and Adaptation.
EXAMPLE
Example: Your development team at an e-commerce company is switching to agile work and you are introducing Scrum. Using the Scrum Guide, you define the roles (Product Owner, Scrum Master, Developers), set up two-week sprints, and establish the events — from Sprint Planning to the Retrospective.