# Scrum

## _Capability Template Details_

### Scrum

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. This Agile team assessment focuses on a high-performing Scrum team's practices, skills, and behaviors. Influenced by many Scrum thought leaders and the recent version of the Scrum Guide (2020), this template provides an opportunity for Scrum teams to measure and improve their Agile team performance. In addition to being a scrum team assessment, it can also be used to aid in developing an Agile transformation roadmap, Agile coach plan, and Agile maturity model focused on Agile team performance.

### Ideal For

New and seasoned Scrum teams.

### References

Works of thought leaders that influenced the Growth Criteria, assigned Stage, and associated Outcomes.

### Capabilities by Dimension

**12** total capabilities

##### Product

- Team Backlog
- Team Product Owner
- Team Backlog Refinement

##### Engineering

- Team Definition of Done
- Team Focus on Quality

##### Process

- Team Composition
- Team Iteration
- Team Iteration Planning
- Team Stand-Up
- Team Iteration Review

##### Improvement

- Team Retrospective

##### Leadership

- Team Lead Facilitator

### Capability Growth Criteria Example

#### Team Backlog Refinement

Assesses the team's ability to progressively elaborate backlog items and create a shared understanding of the work.

**Starting (0)**  
There is a lack of activity that enables the team to create a shared understanding of upcoming backlog items (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))).

**Developing (1)**  
Ongoing activity that occurs on cadence  
Is attended by the right people to progressively elaborate and decompose backlog items (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))).  
Includes rich conversation, backlog item (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))) writing, decomposition, team-based estimation (i.e., [planning poker](https://www.agilealliance.org/glossary/poker/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'planning*20poker))~searchTerm~'~sort~false~sortDirection~'asc~page~1))), and progressive elaboration on acceptance criteria and quality assurance.

**Emerging (2)**  
Surfaces ambiguity, risk, and the need for research [spikes](https://www.agile-academy.com/en/agile-dictionary/spike/)  
Backlog item [Definition of Ready](https://www.agilealliance.org/glossary/definition-of-ready/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'definition*20of*20ready))~searchTerm~'~sort~false~sortDirection~'asc~page~1)) is established, and Backlog Refinement is geared toward meeting that criteria.  
Used as not only a requirement activity but also a planning activity.  
Time boxes are used for backlog items (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))) Refinement to avoid analysis paralysis.

**Adapting (3)**  
Refinement of backlog items (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))) continues until it is sufficiently independent to be worked on by the team without excessive coordination.  
Informal Backlog Refinement activity is naturally occurring amongst team members beyond the formal event.

**Optimizing (4)**  
Iterative planning (i.e., sprint planning) meetings are smooth and fast due to the readiness of backlog items (i.e., [User Stories](https://www.agilealliance.org/glossary/user-stories/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'user*20stories))~searchTerm~'~sort~false~sortDirection~'asc~page~1))) and clarity on purpose and scope.