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
Big Scrum: Are you doing mechanical Scrum
Explores the difference between mechanical and Professional Scrum, highlighting the importance of values, principles, and technical …
My journey into Professional Scrum
Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges …
Do you need an expert in Visual Studio ALM, TFS, or Scrum?
Expert consulting and onsite training available in Visual Studio ALM, TFS, and Scrum, including project migration, course delivery, and …
Upcomming Scrum at Scale Workshop from Scrum.org
Learn how to scale Scrum across your organisation, drive cultural change, and measure agile maturity with evidence-based practices in this …
Bruce Lee on Scrum and Agile
Explores how Bruce Lee’s philosophy applies to Scrum and Agile, emphasising adaptability, simplicity, and creating flexible, tailored …
TFS Process Template migration script updated
Provides a step-by-step PowerShell script for migrating and updating TFS process templates, including customisations, work item types, …
Does your organisation have both Project Mangers as well as Product Owners?
Explores the challenges of having both Project Managers and Product Owners in teams, highlighting conflicts, reporting issues, and impacts …
Professional Scrum in Immingham, UK
Summary of a multi-team Professional Scrum training at DFDS Seaways in Immingham, UK, highlighting co-located learning, cross-team …
Professional Scrum Foundations coming to Glasgow, Scotland in November 2013
Professional Scrum training courses in Glasgow, Scotland, offer foundational and advanced Scrum skills for teams, Scrum Masters, and …
There is no "do agile" there is only "be agile"
Explores the difference between adopting agile practices superficially and truly embracing agile values, highlighting the need for deep …
Review: The Professional Scrum Masters Handbook
A critical review of The Professional Scrum Masters Handbook, highlighting its practical tips for new Scrum Masters and common Scrum …
A change for the better #4 - Homecoming
Details a move from the USA back to Scotland for family and education reasons, continuing ALM consulting, and plans to offer agile coaching …
Searching for self-organisation
Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and …
What's new in Visual Studio 2013 Team Foundation Server Preview
Highlights new features in Visual Studio 2013 Team Foundation Server, including agile portfolio management, enhanced team collaboration, and …
Upgrading your process template from MSF for Agile 4 to Visual Studio Scrum 2.x
Step-by-step guide to safely upgrade from MSF for Agile 4 to Visual Studio Scrum 2.x process templates in TFS, including handling …
Working within a single Team Project with Team Foundation Server 2012
Explains how to organise teams, products, and projects within a single Team Project in Team Foundation Server 2012, covering design, …
The Insufficiency of Scrum is a fallacy
Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and …
Professional Scrum Foundations in Alameda, California
Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles …
TFS 2012 Agile Planning Tools Issue - nested tasks makes the parent task disappear
Explains why nesting tasks in TFS 2012 Agile Planning Tools causes parent tasks to disappear, and recommends using nested Product Backlog …
One Team Project to rule them all
Explains how to manage multiple teams and projects in Team Foundation Server using a single Team Project, with tips on Agile planning, …
One Team Project Collection to rule them all - Consolidating Team Projects
Step-by-step guide to consolidating multiple Team Projects and Collections in TFS 2012 using the TFS Integration Platform, covering …
Upgrading TFS 2010 to TFS 2012 with VSS Migration and Process Template consolidation
Step-by-step guide to upgrading TFS 2010 to TFS 2012, migrating VSS data, consolidating process templates, and resolving common issues …
Process Template Upgrade #7 – Rename Work Items and Import new ones
Step-by-step guide to upgrading TFS process templates by renaming and importing work item types, preserving data, updating fields, …
What's in a burndown?
Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to …
Professional Scrum Foundations in Salt Lake City, Utah
Covers hands-on experiences teaching the Professional Scrum Foundations course in Salt Lake City, highlighting teamwork, agile practices, …
You can't stack rank hierarchical work items?
Explains why stack ranking hierarchical work items is challenging in agile software development, highlighting issues with ordering, …
Scrum-damentals Webcast on 17th February 2012
Explore common challenges in Scrum adoption, practical strategies for overcoming them, and proven practices to help teams implement Scrum …
Visual Studio 2010 Overview - A day in the life of ... Plan, Code & Test
Explore how developers, testers, and managers use Visual Studio 2010 and TFS for planning, coding, testing, bug fixes, and sprint management …
Can you really commit to delivering work?
Explores why Scrum shifted from "commitment" to "forecasting" work delivery, highlighting the risks of overpromising and the benefits of …
Are you doing Scrum? Really?
Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if …