The map / Team
Level · Day · 2 weeks
Team
Development: a stable team that delivers a working, tested increment every sprint.
01What it's for
The team is where the product is built. A stable, cross-functional team delivers a working and tested increment every sprint, towards the PI objectives it committed to, and decides itself how to do the work.
02What it turns into on the old system
The team becomes a resource pool. People are allocated to projects by percentage, teams are organised per component, a manager assigns the tasks, and velocity turns into a productivity target.
03How you notice
- People are part of three teams at once.
- The team's composition changes every PI.
- Stories are tasks, and the team cannot finish anything of value on its own.
- Velocity is compared between teams.
04How to make it work
Keep teams stable, cross-functional and aligned to value.
Let the team decide how it works and what it can commit to.
Improve through the retrospective, and escalate what the team cannot fix to Inspect & Adapt.
→The parts of this level
- Story — A small, testable slice of user value, finished within a sprint.
- Story Refinement — The team and the Product Owner get the next stories ready.
- Sprint Planning — The team sets a sprint goal towards the PI objectives and decides how.
- Daily Scrum — The team inspects progress towards the sprint goal and adapts the day.
- Sprint Review — Working increment in front of stakeholders; the backlog adapts.
- Sprint Retro — The team inspects how it works and picks one improvement.
- Team increments — Every team's work integrates into one system, continuously.