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
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 …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Scrum Master is accountable for Delivery
Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint …
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, …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
Hiring a Professional Product Owner
A reusable Product Owner job specification covering product leadership, decision authority, customer outcomes and modern product management, …
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 …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
The Scrum Master is accountable for Delivery
Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint …
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 …
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, …
Empowering Agility: Why Authority Is Critical to Sustainable Engineering Leadership
Why Scrum Masters and Product Owners need real authority, not just influence, to remove impediments, uphold engineering standards 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, …
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 …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …
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 …
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 …
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 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 …
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 Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success
Scrum Masters with deep knowledge and competence enable teams to deliver better products, drive business outcomes, and foster real …
The Competence Crisis in Scrum Master Roles: A Call for Excellence
Many Scrum Masters lack essential skills and experience, leading to poor agile outcomes. True competence requires deep knowledge, practical …
Evidence-Based Portfolio Management
Explains how evidence-based portfolio management helps organisations extend agile practices beyond teams, enabling greater responsiveness …
The Scrum Guide (November 2020)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …
Nexus Guide
Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery …
317 resources, newest first
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 …
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 …
Worst trait in unskilled scrum masters?
Highlights the most damaging traits of unskilled Scrum Masters, such as micromanagement and bossiness, and contrasts them with effective, …
One critical skill for a Scrum Master and why?
Teaching is the key skill for Scrum Masters, enabling teams to understand Agile principles, embrace change, and achieve deeper engagement …
Is a scrum master an agile micromanager?
A Scrum Master empowers teams by facilitating, mentoring, and supporting, not micromanaging, fostering trust, collaboration, and continuous …
Unlocking the True Potential of Scrum: Why Professionalism Matters in Agile Teams
Explores how true professionalism in Scrum enables Agile teams to deliver production-ready products, highlighting the importance of …
How would you like to be remembered as a Professional Scrum Trainer? What 3 things matter most to you?
Shares the top three values guiding a Professional Scrum Trainer: integrity, honesty, and approachability, with a focus on transparency, …
Is a PSM II certification validation of your skills, or does it develop your skill and capability as a Scrum Master?
Explains how the PSM II course focuses on developing advanced Scrum Master skills, facilitation techniques, and accountability, rather than …
Why Many Scrum Masters Stall at PSM1: The Crucial Role of Passion in Professional Growth
Many Scrum Masters stop at PSM1 due to lack of passion. Ongoing learning, genuine interest, and active engagement are key to advancing and …
What is the difference between a newbie scrum master and a professional Scrum Master?
Explores why the distinction between 'newbie' and 'professional' Scrum Master is misleading, emphasising the role’s responsibilities, …
Is Your Scrum Master Struggling? Discover When to Choose an Agile Process Simulation Workshop
Learn when to use an Agile Process Simulation workshop to support struggling Scrum Masters, improve team dynamics, and foster collaborative, …
How will a PSM II course challenge your assumptions the most?
Explores how the PSM II course challenges common misconceptions about Scrum Masters, emphasising advanced skills, team empowerment, and …
The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap
Explores the real differences between new and experienced Scrum Masters, challenging common myths and highlighting the importance of …
Mastering Scrum: Effective Planning and Prioritisation for Agile Success
Learn how to plan and prioritise effectively in Scrum by aligning with business goals, assessing value and risk, and keeping a lean, focused …
Unlocking Greatness: How the Right Scrum Master Transforms Teams and Organisations
Explores how an effective Scrum Master drives team success by fostering team fit, addressing organisational barriers, and building …
What is your best advice for becoming a Scrum Master outside software engineering?
Practical guidance on becoming a Scrum Master outside software, covering certification, skill development, validated learning, and applying …
Why Pursuing Agile Certifications is Your Key to Career Advancement
Explains how Agile certifications validate knowledge, support continuous learning, and help employers assess candidates, while emphasising …
Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course
Discover how the Advanced PSM course helps Scrum Masters shift from admin tasks to empowering teams, supporting Product Owners, and tackling …
What is the most common Aha moment people have in a scrum course?
Most people in scrum courses realise the true value of empiricism and purpose behind scrum’s events and artefacts, shifting from rote …
Why is Scrum so easy to understand but incredibly hard to master?
Explores why Scrum is challenging to master, highlighting cultural barriers, the importance of transparency, and the gap between …
Why did you choose the Scrum.Org track rather than the Scrum Alliance track?
Explains choosing Scrum.Org over Scrum Alliance, focusing on values, certification costs, flexibility, community support, and alignment with …
Why do you think the PSU course has become so popular for product development?
The PSU course bridges the gap in product development by integrating user experience and design into Scrum, enabling teams to deliver more …
What is a common mistake made by rookie agile consultants?
Rookie agile consultants often mistake strict adherence to frameworks like Scrum for success, overlooking the need for context, team buy-in, …
What would you advise a scrum team to do in their first 4 weeks?
Guidance for new scrum teams on establishing effective practices, learning from experience, experimenting, and improving during their first …
In high competition markets, how does scrum product development help acquire and retain customers?
Explains how Scrum supports customer acquisition and retention in competitive markets by enabling rapid delivery, feedback, and continuous …
What is the hardest part of working with a brand-new scrum team?
The biggest challenge with new scrum teams is overcoming misconceptions about scrum and shifting focus from process mechanics to core agile …
Debunking the Scrum Myth: Why "Twice the Work in Half the Time" is a Misleading Promise
Explores why Scrum's "twice the work in half the time" claim is misleading, emphasising value over output and the importance of realistic …
What does a poor scrum team look, act and feel like?
Explores signs of a poor scrum team, including autocratic leadership, dysfunctional product ownership, lack of trust, and organisational …
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 …