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
Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work
Explains key Scrum concepts: distinguishing Definition of Done from acceptance criteria, using spikes vs. refinement, and strategies for …
Unlocking Agile Success: Your Guide to the Professional Scrum Foundations Class and PSM I Assessment
Learn what to expect from the Professional Scrum Foundations class, key Scrum concepts, hands-on learning, and tips to prepare for the PSM I …
Unlocking Agile Success: Embrace Continuous Forecasting and Transform Your Training Experience
Explore practical strategies for Agile training, including virtual class setups, continuous forecasting, and using metrics to improve …
Maximise Your Virtual Classroom Experience: Essential Tech Tips for Scrum Training
Practical tech tips for using Microsoft Teams and Mural to improve collaboration, engagement, and learning in live virtual Scrum training …
Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World
Practical strategies for remote Agile teams, covering communication, tool selection, value delivery, team dynamics, gamification, and …
Live Webcast: Q&A with Martin Hinshelwood on 27th March 2020
Martin Hinshelwood answers questions on integrating UX into Scrum teams, sharing practical advice from his experience teaching Professional …
Scaling Agility: Navigating the Dragons of Change in the Future of Work
Explores practical strategies for scaling agile practices, key metrics, virtual training adaptations, and global insights to navigate change …
What is your perspective on collocation?
Explores the benefits and challenges of collocation in Scrum teams, comparing face-to-face collaboration with remote work, and offering …
Can the Definition of Done change per Sprint?
The Definition of Done can evolve to improve quality but should not be weakened or vary per backlog item. Consistency ensures transparency …
How do you handle conflict in a Scrum Team?
Guidance on resolving conflict in Scrum Teams, including facilitation techniques, escalation steps, and the Scrum Master's role in fostering …
In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?
Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and …
Should the Scrum Master always remove impediments?
Explains when a Scrum Master should remove impediments, focusing on team self-sufficiency, true impediments, and supporting team growth …
What's the best way to work around multiple PO?
Guidance on addressing issues with multiple Product Owners in Scrum, highlighting the need for clear backlog ownership and accountability to …
How do you make a good Forecast?
Explains how to create reliable forecasts in agile projects by using flow metrics like cycle time and throughput, and shifting from …
Are technical skills required to be a Scrum Master?
Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum …
No Estimates and is it advisable for a Scrum Team to adopt it?
Explores whether Scrum Teams should adopt No Estimates, comparing estimation methods, team maturity, and metrics like cycle time, …
How do you incorporate a Design Sprint in Scrum?
Explains how to integrate Design Sprint activities within Scrum by embedding design and UX work into regular sprints and backlog refinement, …
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 …
Professional Scrum is for everyone in your organisation
Explains how involving everyone in Professional Scrum training fosters organisational agility, breaks down silos, and empowers teams to …
Create your own path to Organisational Agility
Learn how to achieve organisational agility by tailoring change to your unique context, building a guiding coalition, and engaging all …
Round up for 2017 and beyond: Agility, DevOps, and Everything In-between
Summary of 2017 conferences, talks, and training on Agile, DevOps, Scrum, and team leadership, with insights from global workshops and …
Professional Scrum Training for the Ghana Police Service
Professional Scrum training introduced Ghana Police officers to Agile methods, using hands-on sprints to support organisational change and …
Professional Organisational Change at the Ghana Police Service
Explores the Ghana Police Service’s shift to a modern, professional model using servant leadership, agile frameworks, and strategic change …
Embracing Process Improvement: How Understanding Scrum Transformed a Developer's Mindset
Explores how learning Scrum and process improvement can shift developer mindsets, boost collaboration, and enhance software delivery in …
Scrum Tapas: Scrum and Continuous Delivery
Explains how Scrum and Continuous Delivery work together, highlighting their complementary roles in agile software development and practical …
Scrum Tapas: The Importance of Professionalism
Explores why professionalism and adherence to engineering excellence are essential for effective Scrum teams, highlighting common pitfalls …
Choosing a Process Template for your Team Project
Guidance on selecting the best process template for team projects in TFS or VSTS, highlighting why the Scrum template reduces friction for …
Scaling Professional Scrum with Visual Studio Team Services
Explains how to scale Professional Scrum across multiple teams using Visual Studio Team Services, covering automation, Nexus integration, …
Professional Scrum Courses for 2016 in Oslo, Norway
Details 2016 Professional Scrum Master and Developer courses in Oslo and Kongsberg, covering advanced Scrum, coaching, DevOps, and Agile …
Big Scrum: All you need and not enough
Explores how to scale Scrum effectively by applying agile values, fostering professional teams, and adapting processes to fit unique …