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, …
Evidence-Based Portfolio Management
322 resources, newest first
Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation
Explores and corrects common misconceptions about Scrum, clarifying its true principles, events, planning, and governance to help teams …
You can't stop the signal! But you can ignore it!
Explores why teams ignore clear signals from Agile and Scrum, highlighting how culture and fear hinder continuous improvement and effective …
Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility
Identifies seven common Agile pitfalls, quick fixes, backlog overload, resource focus, lack of accountability, blame, imitation, and pride, …
Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success
Learn how to customise Azure DevOps to support Scrum teams, manage backlogs, plan sprints, and improve agile workflows with practical setup …
Rethinking Backlog Management: Why a Flat Structure Boosts Agility and Value Delivery
Explains how using a flat backlog structure, rather than a hierarchy, improves agility, prioritisation, and value delivery in Scrum and …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
Rethinking Sprint Planning: Why Burndown Charts Are Agile Banditry and What to Do Instead
Explains why burndown charts hinder agile teams, highlighting the pitfalls of detailed upfront planning and advocating for minimal, adaptive …
Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products
Explains why relying on special Sprints undermines Agile, and advocates for continuous improvement, accountability, and delivering usable …
Special Sprints: Agile Banditry or Risk Management?
Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …
Overcoming the Ghost of Agile Certifications
Explores the limits of Agile certifications, emphasising real-world experience, continuous learning, and team validation over credentials …
Agile Alchemy
This podcast discusses why precise language and transparency are essential in agile practices, highlighting how word choice impacts …
Mastering Product Backlog Management: Essential Skills for Product Owners
Learn the core skills and best practices for effective product backlog management, including risk, value, sizing, learning, and refinement …
The Evolution of Agile Learning: Insights from Scrum.org's Webinar
Explores the shift from traditional to immersive Agile learning, highlighting how ongoing, real-world practice and reflection improve …
Mastering Product Backlog Management: Insights from the New Scrum.org Course
Learn practical skills for effective product backlog management, including item creation, prioritisation, breakdown, and alignment with …
Mastering Scrum: Essential Insights for New Teams from a Scrum Master's Journey
Guidance for new Scrum teams on building strong foundations, embracing empiricism, Scrum values, continuous learning, and the Scrum Master's …
Understanding the True Role of a Scrum Master
Explains the true responsibilities of a Scrum Master, how to maximise team effectiveness, teach Scrum principles, and address organisational …
The Real Scope of a Product Owner: Beyond the Backlog
Explores the full responsibilities of a Product Owner in Agile, highlighting strategic decision-making, value maximisation, and the …
Continuous Delivery
This podcast discusses the role of precise language and transparency in Agile, highlighting how word choice impacts communication, delivery, …
The Power of Immersive Learning: Elevating Scrum Mastery in Your Organization
Explains how immersive learning helps Scrum Masters apply knowledge through real-world practice, feedback, and collaboration, leading to …
Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training
Explore how immersive, double-loop learning in Professional Scrum Master training helps Scrum Masters apply theory, reflect, and collaborate …
Mastering Agile: 3 Essential Strategies to Boost Your Team's Sprint Success
Learn three key Agile strategies: define clear completion criteria, avoid overcommitting in Sprints, and prioritise backlog refinement for …
Mastering Complexity in Scrum: Transform Your Team with Agile Product Strategy Insights
Learn how understanding complexity, empiricism, and key Scrum principles like transparency, inspection, and adaptation can boost Agile team …
Why 'Definition of Done' is Crucial for Success in Scrum
Explains how a clear Definition of Done in Scrum ensures consistent quality, team alignment, and customer satisfaction across all projects, …
Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery
Explains why a clear Definition of Done is vital in Agile and Scrum for quality delivery, transparency, and risk mitigation, with tips for …
How to Tackle the Challenge of an Ineffective Product Owner in Agile Teams
Learn practical steps for Agile teams to address ineffective Product Owners, including support, education, relationship-building, and …
Decoding Ethics in Agile: A Deep Dive with Martin & Simon
Explore how language, transparency, and precision shape ethical practices in Agile, with insights from experienced Agile coaches and …
Why Agile Success Relies on Effective Planning: Debunking the Myths of Scrum
Explains why effective planning is essential in Agile and Scrum, debunking myths about planning, and highlights strategies for teams of all …
Scrum is like communism, it doesn't work. Myth 3
Explores the myth that Scrum leads to micromanagement, clarifying that true Scrum empowers teams with autonomy, collaboration, and trust, …
Scrum is like communism, it doesn't work. Myth 1
Explains why Scrum events are not pointless meetings but structured opportunities for inspection, adaptation, and progress, clarifying …
7 Harbingers of the Agile apocalypse - Silence
Explores how silence in agile teams signals disengagement, and offers strategies to boost stakeholder participation, open communication, and …