Team layer
The Team layer delivers. Small cross-functional teams build, test, safety-assess and release changes in two-week sprints, using Scrum or Kanban.
Used in EssentialOrganisationNetworkPortfolio of Networks
When you need it
Always on. Every configuration includes at least one delivery team.
What this layer decides
- The sprint goal and which stories fit in the sprint
- How the work is designed, built and tested
- Whether a story meets the Definition of Done
- One or two improvements to try each sprint
Team board
Scrum or Kanban, the team’s choice. Stories, service requests and defects flow to done with safety and CAB evidence attached.
To doIn progressBlockedValidateDone
Levers used here
The rest of this page is for subscribers
Subscribe to read the other 7 sections of this page:
- Roles
- Events
- Artifacts
- Inputs and outputs
- How it connects
- If you use Jira or Azure DevOps
- Getting started