Environment: preview · Version: v1.2.2

Scrum Team

The Scrum Team is a defined accountability within Scrum, composed of a Scrum Master, Product Owner, and Developers working together toward a shared Product Goal.

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

Article Scrum Technical Leadership w140

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, …

Read article
Article Engineering Excellence Scrum w195

Professional Scrum teams build software that works

Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …

Read article
Article Scrum Product Development w200

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, …

Read article
Article Scrum Engineering Excellence w200

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 …

Read article
Video Product Development Scrum w225

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 …

Watch video
Video Scrum Product Development w235

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 …

Watch video
Video Scrum Product Management w240

Free Workshop 04: Introduction to Sprint Reviews [Review & Retrospective]

Covers key concepts of Sprint Reviews, interactive workshop delivery using Teams and Mural, technical challenges faced, participant …

Watch video
Video Scrum Product Development w250

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 …

Watch video
Article Scrum Technical Leadership w255

Hiring a Professional Scrum Master

Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …

Read article
Debug: Kind=term | Type=tag | Layout= | Section=tags
No bundle resources.
Page template:site\layouts\term.html