Scrum is a Framework and a social technology for delivering adaptive solutions in complex environments. It is built on empiricism, transparency, inspection, and adaptation, and is designed to help teams deliver value iteratively and incrementally. Scrum is a framework that helps teams work together to solve complex problems and deliver high-value products. Its about planning.
First Principals
- Empiricism: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
- Self-Organization: Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
- Collaboration: Scrum promotes collaboration among all roles to deliver the highest value.
- Value-Based Prioritization: The Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team.
- Time-Boxing: Time-boxed events are used to create regularity and to minimize the need for meetings not defined in Scrum.
- Iterative Development: Scrum uses an iterative, incremental approach to optimize predictability and control risk.
- Incremental Delivery: Scrum delivers a potentially releasable product increment at the end of each Sprint.
- Continuous Improvement: Scrum Teams continuously improve through the use of the Scrum Events and by inspecting and adapting the product, processes, and practices.
Values
- Commitment: The Scrum Team commits to achieving the Sprint Goal.
- Focus: The Scrum Team focuses on the work of the Sprint and the goals of the Scrum Team.
- Openness: The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
- Respect: Scrum Team members respect each other to be capable, independent people.
- Courage: The Scrum Team has the courage to do the right thing and work on tough problems.
Accountabilities
- Scrum Team – Consists of a Product Owner, Developers, and a Scrum Master. The Scrum Team is self-managing and works collaboratively to deliver a usable Increment every Sprint.
- Product Owner: Accountable for maximising product value and managing the Product Backlog.
- Developers: Accountable for delivering usable Increments that meet the Definition of Done.
- Scrum Master: Accountable for Scrum effectiveness, causing the removal of impediments, and coaching the team.
Events
- Sprint: A fixed-length iteration (≤ 1 month) in which the team creates at least one usable Increment.
- Sprint Planning: Based on the Product Goal, the team plans the work for the Sprint.
- Daily Scrum: Based on the Sprint Goal the Developers plan work for the next 24 hours.
- Sprint Review: Based on the current state of the Product, current business conditions, and possible future business conduction the Scrum Team plans whats next.
- Sprint Retrospective: The Scrum Team plan on how they will change their system to improve the next Sprint.
Artifacts
- Commitments
- Product Goal: The long-term vision for the product.
- Sprint Goal: A tactical objective for the Sprint.
- Definition of Done (DoD): A quality standard for completed work.
Key Accountabilities
Scrum is lightweight, but difficult to master. It is not a process or methodology but a framework that helps teams navigate complexity through empirical process control.
The strongest work on Scrum — ranked by substance, not recency. How this is ranked
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results
Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Scrum Teams don’t set the bar for quality, they meet it
Scrum Teams must consistently meet a clear, non-negotiable Definition of Done to ensure quality, manage risk, and prevent technical debt in …
Definition of Done - Objective vs Subjective
Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria …
Work can flow across the Sprint boundary
Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results
Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why the Concept of a "Junior Scrum Master" is a Misguided Myth
Explains why the Scrum Master role requires experience and competence, debunking the myth of a "junior" Scrum Master and highlighting the …
Mastering Product Development Costs: Empower Your Team for Financial Success
Learn how to track, manage, and optimise product development costs by empowering teams with financial awareness, key metrics, and continuous …
Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability
Explores common misconceptions about Scrum Masters, clarifies their true accountabilities, and highlights the importance of principles, …
The Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI
Incompetent Scrum Masters reduce team performance and ROI by lacking key skills. Learn how to measure their impact using innovation, usage, …
The Scrum Guide (February 2010)
Evidence-Based Portfolio Management
322 resources, newest first
What will you learn on the professional scrum master course?
Gain practical skills and deep understanding of the scrum master role, scrum theory, empiricism, team dynamics, and delivering value in …
How does the APS course help people apply scrum effectively?
Explains how the APS course uses practical exercises and simulations to help people understand, apply, and improve scrum practices in …
Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft
Discover how hands-on Scrum training using Minecraft helps learners experience project chaos, apply agile principles, and gain practical …
Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events
Explains Scrum’s core values, roles, artifacts, and events, highlighting how they support teamwork, transparency, and adaptability in …
Unlocking Agile Success: How Empirical Models Transform Project Outcomes
Explains how empirical Agile models improve project outcomes by increasing visibility, enabling change, reducing risk, and delivering value …
Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey
Learn how the Professional Scrum Product Owner course builds agile skills, practical product management, and ongoing support for effective …
Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course
Learn practical strategies for overcoming common challenges in scaling Scrum, based on hands-on insights from the Scaled Professional Scrum …
Unlocking Your Potential: Transformative Training for Aspiring Scrum Masters
Comprehensive Scrum Master training offering interactive workshops, practical activities, community support, and assessment to build Agile …
Free Workshop 04: Introduction to Sprint Reviews [Review & Retrospective]
Covers key concepts of Sprint Reviews, interactive workshop delivery using Teams and Mural, technical challenges faced, participant …
Announcing Professional Agile Leadership with Evidence-Based Management Training (PAL-EBM) from Scrum.org
Learn about Scrum.org’s new PAL-EBM training, which helps leaders use evidence-based management and custom metrics to align teams with …
Hiring a Professional Product Owner
Explains the key accountabilities, skills, and behaviours required for a Scrum Product Owner, including hiring trends, role requirements, …
Stop normalizing unprofessional behaviour in the name of agility
Highlights the importance of professionalism in agile teams, warning against excusing unprofessional behaviour as agility and stressing …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
Sprint Goal is an Immediate Tactical Goal
Explains how the Sprint Goal serves as an immediate tactical objective in Scrum, guiding teams toward strategic Product Goals and maximising …
Story Points & Velocity are a sign of an unsuccessful team
Explains why relying on story points and velocity signals team immaturity in Scrum, and highlights better ways to build confidence and …
Evidence-based Management: Gathering the metrics
Explains how to gather key metrics for evidence-based management in software organisations, focusing on value delivery, time to market, and …
If your backlog is not refined then you are doing it wrong
Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure …
Evidence-Based Portfolio Management
Getting started with a Definition of Done (DoD)
Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent …
A better way than staggered iterations for delivery
Explains why staggered iterations harm software delivery, increasing technical debt, and recommends cross-functional teams, test-first, and …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
The Sprint Goal is a commitment for the Sprint Backlog
Explains how the Sprint Goal guides Scrum teams by providing a clear, shared objective for each Sprint, ensuring focus, transparency, and …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Product Goal is a commitment for the Product Backlog
Defines the Product Goal as a clear, measurable objective in the Product Backlog that guides Scrum Teams, ensuring focus, transparency, and …
Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework
Summarises key changes in the 2020 Scrum Guide, including simplified language, self-managing teams, and new commitments for goals, backlog, …
I do continuous deliver, why should I Sprint?
Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and …
The fallacy of the rejected backlog item
Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, …
Unlocking Agile Leadership: Transform Your Skills with Scrum.org's Essentials Workshop
Learn practical agile leadership skills, foster team alignment, and drive cultural change with Scrum.org’s workshop to support agile …
Delivering Live Virtual Classes in Microsoft Teams and Mural
Guidance on running live virtual Scrum classes using Microsoft Teams and Mural, focusing on tech setup, safe collaboration, self-organising …
Live Virtual Classroom's and the new normal
Explores how live virtual classrooms have become effective alternatives to in-person training, highlighting benefits, challenges, and the …