Team Level

Team Backlog

Team Backlog Each Team has exactly one Backlog for its area of ​​responsibility and tasks . Its elements (Team Backlog Items) consist in the finest level of granularity of Team Goals. The Team Product Owner is  responsible for and prioritizes the Team Backlog. A large part of the Team Backlog is derived by the Team…

Team DoD (Definition of Done)

The Team , the Team Product Owner and the Stakeholders must agree on what it means when a backlog entry or a result is referred to as “done”. Although this can vary significantly from team to team, all Team Members must have a common understanding of when work is done to ensure transparency. This is…

Team Improvement Backlog

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant group, self-organized. A rule that describes how much work the group spends on improvements (e.g. 10-20%) helps to keep the predictability of other Backlog Items high. The Improvement Backlog is the planning and structuring tool of the…

Team Iteration Backlog

The Team Iteration Backlog reflects the work of a Team for a currently running Iteration. The planned work, reflected by backlog elements, is pulled into the Team Iteration Backlog by the Working Team at the start of the Iteration, which is referred to as Pull.   Further suitable links: Events Roles Groups Artifacts Team Planning…

Team Calendar

The Team Calendar shows the availability of the Nucleus and Extended Team members for an Iteration. Each Team Member enters planned absences in order to determine the gross capacity of the team before (or at the latest in) the Iteration Planning. The gros capacity is used to adjust the  work forecast by relating it to…

Team Planning

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,…

Team Product Owner (TPO)

The Team Product Owner prioritizes the Team Backlog and approves the results of the Working Team. The Team Backlog can contain several product developments or parts of them. (A general description of the Product Owner role can be found here …) Depending on the type and area of responsibility of the Team (“team flavor”), the…

Team Retrospective

The Team Retrospective gives the team the opportunity to review themselves and to identify and plan improvements in the way they work for the upcoming iteration . It takes place between the Team Review and the next Team Planning. For a four-week iteration, an upper limit of three hours is set. The meeting is usually…

Team Review

At the end of each iteration, an Team Review is held in which the Team presents the results to the Stakeholders, with the Team receiving feedback from the Stakeholders and then jointly adjusting the Team Backlog when needed. Together with any changes to Team Backlog during the past Iteration (within the Team Backlog Refinement meetings),…

Team Scrum Master (TSM)

Team Scrum Master (TSM) The TSM ensures that the members of his Team can work optimally. He ensures an optimal work flow between the team members, by discovering improvements and solving disabilities and problems (presented managed in the Team Improvement Backlog) that arise in the cooperation of the teams. This especially concerns those that cannot…