Each Iteration<\/a> begins with the Team Planning<\/strong> event of the Team<\/a>. Here, the Team Product Owner<\/a> presents the Working Team<\/a> with the current state of the Team Backlog<\/a>. New entries or changes that are not yet known to the Working Team since the last Team Backlog Refinement<\/a> are estimated, and if necessary supplemented by Acceptance Criteria and prioritized by the Team Product Owner within the Team Backlog. Then, the Working Team starts the Iteration by pulling the first Tasks (or TBIs) from “open” to “in progress”.<\/p>\n 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<\/a>, 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.<\/p>\n –<\/span><\/p>\n Further suitable links:<\/p>\n
\nThe Working Team determines the capacity for the next Iteration by looking at the team’s previous work rate (Team Velocity<\/a>) and filling the Team Calendar<\/a>, which shows the time that each Team Member can spend for the Working Team.
\nThe Working Team pulls<\/span> the number of TBIs into the Iteration Backlog<\/a> that matches the teams capacity for the next Iteration. Afterwards the Working Team optionally refines the TBIs by creating Tasks<\/a>, depending on the complexity.<\/p>\nContinuous Team Planning (Kanban-mode)<\/h2>\n
\n