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 is the Sprint Review workshop and how will it help organisations?
Explains the Sprint Review workshop, detailing its role in Agile teams for stakeholder engagement, market alignment, and continuous product …
Most Common Thing You Hear in a PSPO Course?
Product Owners often feel limited in control and influence. This article explores common challenges and offers steps to boost empowerment …
Words matter
Explore how precise language and transparency impact communication and effectiveness in agile teams, with insights from experienced agile …
Unlocking the Power of Sprint Planning: Transform Your Agile Approach for Success
Learn how effective Sprint planning boosts Agile team performance, with practical workshops, coaching, feedback, and adaptable methods for …
Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment
Learn practical steps to help Scrum teams achieve continuous delivery, clarify business value, integrate feedback, and build empowerment …
How Hard is it to Transition from Being a Developer to a Scrum developer?
Explores the challenges and skills needed to shift from traditional development to Scrum, focusing on continuous learning, Agile practices, …
Unpacking the Scrum Master Myth: Why Servant Leadership is Key to Team Success
Explains why the Scrum Master is a servant leader, not an authority figure, and how this approach empowers teams, encourages autonomy, and …
Hardest Part of Adopting Scrum?
Overcoming the belief in quick fixes is the hardest part of Scrum adoption; true success requires mindset change, continuous learning, and …
Worst Contribution from a Product Owner that You Know Of
A real-world example of a product owner undermining their Scrum team during a sprint review, highlighting the importance of support, …
Best Scrum advice you ever received?
Emphasises the importance of flexibility and pragmatism in Scrum, encouraging teams to adapt frameworks to their context rather than rigidly …
How do you know if you've got a great Sprint Goal?
Learn how to identify a great sprint goal by recognising signs of team excitement, curiosity, and engagement, ensuring your Agile sprints …
How does a Scrum team decide on a Sprint goal?
Explains how Scrum teams collaboratively define a clear, achievable Sprint goal through early stakeholder input, planning, consensus, and …
Are office spaces dead
Explores how remote work is changing office life, training, coaching, and consulting, with insights from experienced agile coaches and …
How does a Scrum team create a sprint goal?
Explains how Scrum teams create effective sprint goals by aligning product strategy, tactical needs, and backlog priorities to deliver …
How does a Scrum team estimate what can be delivered in a Sprint?
Scrum teams estimate Sprint deliverables by assessing the size and complexity of backlog items, focusing on shared understanding rather than …
What is a sprint goal?
Explains the sprint goal in Scrum as a clear, tactical objective for each sprint, guiding team focus, enabling actionable feedback, and …
How critical is a Product Owner in developing a great Product Backlog?
Explains why a product owner is essential for shaping, prioritising, and maintaining a focused, lean product backlog that drives effective …
How do you select the most valuable items for the sprint backlog?
Learn how Agile teams collaboratively select high-value sprint backlog items by balancing business needs, technical priorities, and …
What is a Sprint Backlog?
Explains the Sprint Backlog as a transparent, flexible plan in Scrum, combining goals, tasks, and strategy to help teams stay focused, …
Mastering Sprint Planning: Key Principles for Agile Success
Learn essential principles for effective Sprint planning in Agile, including understanding the product backlog, setting clear goals, and …
What is the most common mistake in sprint planning?
Explains the sprint goal in Scrum as a clear, tactical objective for each sprint, guiding team focus, enabling actionable feedback, and …
What is Sprint Planning?
Sprint planning is a collaborative session where teams define and align on goals, tasks, and priorities for the next sprint, ensuring …
What is a product owner? Why are they essential?
Explains the product owner's role in Scrum, focusing on accountability for maximising value, aligning teams with strategy, and ensuring …
Unlocking Team Potential: The Essential Role of a Scrum Master in Agile Success
Explains how a Scrum Master empowers Agile teams by bridging business, technical, and organisational needs to boost effectiveness, …
#1 tip for a new Scrum Master
New Scrum Masters should start by thoroughly reading the Scrum Guide to understand Scrum principles, roles, and practices, forming a strong …
Redefining the Scrum Master: From Misconceptions to Empowering Leadership
Explores common misconceptions about the Scrum Master role, highlighting the shift from tool admin to empowering leader who fosters team …
Beyond the Rituals: Embracing the Core Principles of Scrum for True Agile Success
Explores how focusing on Scrum’s core principles, empiricism, transparency, and value delivery, leads to true agile success, beyond just …
Unlocking Trust in Scrum: The Power of Openness and Transparency
Explores how openness and transparency in Scrum foster trust, clear communication, and a supportive team culture, essential for effective …
Redefining the Scrum Master: From Boss to Empowering Facilitator
Explains how effective Scrum Masters empower teams through facilitation, support, and coaching, moving away from authority and …
Unlocking the Scrum Master's Potential: Embracing Broader Responsibilities for Agile Success
Explores how Scrum Masters can expand their impact by embracing wider organisational responsibilities, challenging outdated practices, and …