Artefacts

Team Backlog Item (TBI)

Team Backlog Items (TBI) are the individual elements (Backlog Items) of a Team Backlog and describe work for a single Team. The size of  a TBI is initially not limited. It must be small enough in size or devided (refined) into several individual items that can be done in one Iteration, before it can be pulled…

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 Mission

Content of a Mission The mission covers the areas of responsibility (the What) and the culture and standards of behavior (the How). The mission clarifies the following points: What is our self-image. What is the purpose of the team? How does the team position itself within the cluster and the organization? How do we want…

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…

Backlog Item Types

“The Backlog is the only source of the work.” The general description of  Backlogs and their properties can be found here. The hierarchy of the Backlog structure describes (in a simple way) the product development process. Backlog entries or Backlog Items are the individual building blocks of backlogs. They are clearly ranked within the backlogs,…