A Scrum Team is the core accountability in Scrum, responsible for delivering value through iterative, incremental work. It consists of a Scrum Master, Product Owner, and Developers, working collaboratively toward a single Product Goal.
The Scrum Team is self-managing and cross-functional. It has no sub-teams or hierarchies, and it is collectively accountable for creating a usable Increment every Sprint. Each member may hold a distinct accountability, but the team itself is responsible for the outcome.
Unlike roles or practices, the Scrum Team is an entity defined in the Scrum framework, empowered by the organisation to manage its own work. Its accountability spans all aspects of product delivery, from stakeholder collaboration and development to validation and release.
This tag is used to explore the nature, structure, and responsibilities of the Scrum Team as a whole, not just how the individuals interact, but what they are collectively accountable for in complex, adaptive environments.
The strongest work on Scrum Team — 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 …
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, …
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 …
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 …
Searching for self-organisation
Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and …
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 …
The fallacy of the rejected backlog item
Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, …
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 …
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 …
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 …
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, …
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 …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
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 …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
If your backlog is not refined then you are doing it wrong
Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure …
Getting started with a Definition of Done (DoD)
Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
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 …
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 …
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, …
Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success
Learn how to customise Azure DevOps to support Scrum teams, manage backlogs, plan sprints, and improve agile workflows with practical setup …
The Power of Building Relationships Through Immersive Learning in Scrum
Explores how immersive learning in Scrum fosters strong peer relationships, enhancing collaboration, trust, and long-term growth for …
Mastering Scrum: Essential Insights for New Teams from a Scrum Master's Journey
Guidance for new Scrum teams on building strong foundations, embracing empiricism, Scrum values, continuous learning, and the Scrum Master's …
The Scrum Guide (February 2010)
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 …
66 resources, newest first
The fallacy of the rejected backlog item
Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, …
Delivering Live Virtual Classes in Microsoft Teams and Mural
Guidance on running live virtual Scrum classes using Microsoft Teams and Mural, focusing on tech setup, safe collaboration, self-organising …
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 …
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 …
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 …
Searching for self-organisation
Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and …
Product Owners are not a myth
Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large …
You are doing Scrum but the Scrum Master tells the team what to do!
Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team …
My first Scrum team in the wild
A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and …
Professional Scrum Developer (.NET) Training in London
Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team …
Adventures in Scrum: Lesson 2 - For the record
Highlights the importance of clear communication and documenting disagreements in Scrum to prevent misunderstandings and failed sprints, …
Adventures in Scrum: Lesson 1 – The failed Sprint
Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned …
The Scrum Guide (February 2010)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …