Team Level

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…

Team Sync (Daily Scrum)

The Team Sync is a daily recurring team event of no more than 15 minutes in which the members of the Working Team synchronize themselves “on eye-level” without reporting to a supervisor. The Team Product Owner only takes part if the team invites him. Even the Team Scrum Master does not have to participate, but…

Team System Engineer (TSE)

The Team System Engineer represents the technical expertise and responsibility of his Team in the Team System Engineer Group of the Cluster . If the team does not agree on any other regulation, he also represents the Team in the Cluster Syncs (scrum-of-scrums) . For this, he should have the broadest possible knowledge of the…

Team Tasks

Team Tasks are activities and actions that a Working Team plans and carries out in order to achieve Team Goals . Team tasks are not part of the Team-Backlog, but part of the Team-Iteration Backlog and are usually created and planned in the Team Planning event. . Further suitable links: Events Roles Groups Artifacts Team…

Team Goals

Team Goals are the most used elements of the Team Backlog . They describe the goals and (interim) results of the team regarding a Feature, a Module or a Service , depending on the type and responsibility of the Team . Generally speaking, the Working Team turns Team Goals into Inspectable Results. Within an Iteration…

Team

The Team is the basic element of an agile organization and forms the home of working people. Up to nine related Teams form a Cluster. Most of the work takes place in stable and long-lasting Teams. Due to the stability or “longevity”, the teams are available in the event of problems even if the Application…

Versioned Modules & Platforms

Versioned Modules & Platforms are the results of Module Teams .   Common attributes of Team results The minimum requirement for a Team result is that it can be inspected, ie it must be presented in a form that makes it assessable for the Stakeholders (e.g. users of the result). The Definition of Done for…