Team Planning

is part ofIteration
is organized byTeam Product Owner
Attendees:Team Scrum Master, Working Team
Refined Artefacts:Team Backlog
Estimated Artefacts:Team Backlog Item
Created result (artefact):Team Iteration Backlog

Iteration Planning of the Teams (Scrum)

Each Iteration begins with the Team Planning event of the Team. Here, the Team Product Owner presents the Working Team with the current state of the Team Backlog. New entries or changes that are not yet known to the Working Team since the last Team Backlog Refinement are estimated, and if necessary supplemented by Acceptance Criteria and prioritized by the Team Product Owner within the Team Backlog.
The Working Team determines the capacity for the next Iteration by looking at the team’s previous work rate (Team Velocity) and filling the Team Calendar, which shows the time that each Team Member can spend for the Working Team.
The Working Team pulls the number of TBIs into the Iteration Backlog that matches the teams capacity for the next Iteration. Afterwards the Working Team optionally refines the TBIs by creating Tasks, depending on the complexity.

Then, the Working Team starts the Iteration by pulling the first Tasks (or TBIs) from “open” to “in progress”.

Continuous Team Planning (Kanban-mode)

As an alternative to the planning of the team’s work in iterations, it can also be done continuously. This is done during, the Team Backlog Refinements, whereby the work on a Team Backlog Item can be started directly after the analysis and estimation. This meeting is also known as Replenishment meeting in other Kanban frameworks.

Further suitable links:

Events Roles Groups Artifacts
Team Sync

Team Backlog Refinement

Team Review

Team Retrospective


Cluster Planning


Portfolio Planning

Team Product Owner

Team System Engineer

Team Scrum Master

Working Team

Community of Practice

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog