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
Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling
Learn to spot six key signs of sloth in Agile teams, including missed deliveries, ignored feedback, rigid processes, and lack of adaptation, …
7 Harbingers of the Agile Apocalypse - Plague
Explores the widespread issue of incompetent Agile coaches and Scrum Masters, its impact on teams and organisations, and practical steps to …
Are there any Scrum courses that teach you how to scale Scrum?
Learn how to scale Scrum by tailoring frameworks to your organisation, focusing on dependency management, alignment, and iterative …
7 Deadly Sins of Agile: Greed
Explores how greed in Agile leads to overwork and reduced value, offering strategies for value-driven delivery, balanced sprints, team …
7 deadly sins of Agile: Gluttony
Explores how Agile teams can avoid overloading backlogs, Sprints, and products by focusing on prioritisation, value delivery, and lean, …
Quotes: Don't scale Scrum! Pragmatic or defeatist?
Examines whether the belief that Scrum can't scale is practical or defeatist, highlighting Nexus as a proven approach for scaling Scrum to …
What are the barriers that prevent developers from fully accepting a Product Owner as the final decision maker?
Explores key barriers preventing developers from accepting Product Owners’ authority, including accountability gaps, stakeholder …
How to Set and Achieve Effective Sprint Goals
Learn how to define, craft, and achieve effective Sprint Goals in Scrum, using frameworks like SMART and OKR to align teams, deliver value, …
The Definition of Done: Ensuring Quality without Compromising Value
Explains how to maintain clear, measurable quality standards with the Definition of Done, while avoiding confusion with acceptance criteria …
Scrum doesn't solve problems, it reveals them. How, and why is that valuable?
Explains how Scrum exposes hidden organisational problems through transparency and feedback, enabling teams to identify issues, improve …
What are the top 3 things a Scrum Master needs to bear in mind when adopting the coaching stance?
Summarises the top considerations for Scrum Masters adopting a coaching stance: building trust, understanding team context, and leading …
Why the Scrum Master’s True Power Lies in Influence, Not Authority
Explains why a Scrum Master leads through influence, not authority, focusing on building trust, fostering team effectiveness, and supporting …
Decoding Scrum Team Work: Balancing Sprint and Refinement Work
Explains how Scrum teams can balance Sprint work and Refinement, with strategies and visual tools to track, manage, and visualise both for …
How does a Scrum Master or Agile coach motivate a Scrum Team?
Explains how Scrum Masters and Agile coaches boost team motivation by setting clear goals, fostering engagement, recognising achievements, …
What should you do if your Sprint Review delivers harsh, scathing feedback?
Learn how Agile teams can handle harsh Sprint Review feedback by analysing root causes, engaging stakeholders, and deciding whether to halt, …
Who Should Lead the Sprint Review? Unpacking the Role of the Product Owner in Agile Success
Explains why the Product Owner should lead Sprint Reviews in Agile, detailing their role in maximising value, gathering feedback, and …
What should be top of mind when a Scrum team prepare for a Sprint review?
Learn how Scrum teams can boost Sprint review success by engaging stakeholders, tailoring communication, and focusing on value, …
What is empiricism and why is it so critical to great Agile?
Explains how empiricism, continuous observation, inspection, and adaptation, drives Agile success by enabling teams to respond effectively …
Why do you trust Joanna to deliver Scrum.Org classes for NKD Agility?
Discover how Joanna’s technical expertise, clear teaching, and real-world Agile experience make her Scrum.Org classes at NKD Agility …
Unlocking Agility: How EPS Immersive Learning Transforms Your Team's Performance
Discover how EPS immersive learning boosts team agility with structured feedback, coaching, and tailored sessions, driving continuous …
What are 3 key takeaways for a scrum team after attending an APS immersive learning experience course?
Discover three essential lessons for Scrum teams after an APS immersive course: deepening core understanding, overcoming early challenges, …
How effectively does an APS prepare a team to do a solid, professional Scrum?
Explains how Applied Professional Scrum (APS) helps teams master Scrum by focusing on fundamentals, removing unhelpful practices, and …
Navigating the Future with a Fine-Tuned Product Backlog
Explains how a well-ordered, refined Product Backlog guides Agile teams, supports goal alignment, and ensures value-driven product …
Hardest part of becoming a professional Scrum Master?
Explores why embracing true professionalism is the hardest part of becoming a Scrum Master, highlighting the importance of deep …
Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations
Failing to deliver a usable product each agile iteration leads to lost trust, technical debt, poor adaptability, misaligned expectations, …
Why is the Professional Agile Leadership - Essentials course a natural evolution for an experienced Scrum Master?
Explains how the Professional Agile Leadership – Essentials course helps experienced Scrum Masters gain leadership skills, understand …
Transform Your Career: How to Become a Confident Scrum Master Through Real-World Learning and Community Support
Learn how practical training, real-world application, and community support help you build confidence and skills to succeed as a Scrum …
Reasons to do a PSM II Course in 60 seconds
Discover how the PSM II course deepens Scrum Master skills, boosts team performance, supports product owners, and advances agile careers …
Why have you decided to go all in on immersive learning experiences?
Explores how immersive learning boosts engagement, retention, and understanding through hands-on practice, community support, and …
Part 2: Common Mistakes that Scrum Masters Make
Explains why Scrum Masters should avoid taking on administrative tasks, highlighting the importance of focusing on team effectiveness rather …