Scrum is a lightweight framework designed to help teams address complex problems and deliver value through adaptive solutions.
Its purpose is to enable teams to generate value in a flexible, iterative way, with frequent opportunities for inspection and adaptation.
Empiricism: Scrum is based on the idea that knowledge comes from experience and making decisions based on what is observed.
Experience-based or learning by doing
Lean Thinking: Scrum focuses on reducing waste and concentrating on what is essential.
Focus on what matters or cutting out waste
Transparency, Inspection, and Adaptation: All aspects of the work must be visible to those responsible for the outcome. Regularly inspect progress and adapt as needed.
Commitment, Focus, Openness, Respect, and Courage: These values guide the behavior and work of the Scrum Team, fostering trust and collaboration.
Composed of:
Product Owner: Responsible for maximizing the value of the product and managing the Product Backlog.
Scrum Master: Ensures the team understands and follows Scrum, removes impediments, and fosters an effective environment.
Developers or Team Members: Create the product increment each Sprint and are accountable for the Sprint Backlog and meeting the Definition of Done.
Self-managing and cross-functional: The team decides how to do the work and contains all necessary skills.
Sprint: A fixed-length period (one month or less) during which a usable, potentially releasable product increment is created.
Sprint Planning: The team plans the work to be performed in the Sprint.
Daily Scrum: A short, daily meeting for the Developers to inspect progress toward the Sprint Goal and adapt the plan.
Sprint Review: The team and stakeholders inspect the increment and adapt the Product Backlog.
Sprint Retrospective: The team reflects on the Sprint and plans improvements for the next one.
Product Backlog: An ordered list of everything that is needed in the product.
Sprint Backlog: The set of Product Backlog items selected for the Sprint, plus a plan for delivering the increment.
Increment: The sum of all completed Product Backlog items during a Sprint, which must meet the Definition of Done.
Product Goal: The long-term objective for the Scrum Team.
Sprint Goal: The single objective for the Sprint.
Definition of Done: The criteria that must be met for an increment to be considered complete.
The Scrum Guide defines Scrum as a simple, flexible framework for product development that relies on transparency, inspection, and adaptation. It specifies clear roles, events, and artifacts, and emphasizes the importance of following its rules to achieve the full benefits of Scrum. If you are not following the Scrum Guide, you may be using some Agile practices, but it would not be considered Scrum as defined by its creators.