Organizational Levels

Team System Engineering Group (TSEG)

The Team System Engineer Group is made up of all Team System Engineers of the Custer. At the Cluster level, it corresponds to the role of the Working Team. The Team System Engineer Group with the Cluster System Engineer is responsible for the Technology & Architecture within the product development at the Cluster / System…

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…

Marketable Systems and Applications

Applications and market variants are the organization’s integrated, tested and approved products that can be sold to customers in the target markets. They meet the requirements specified as a group from the Stakeholer Needs in the ” feature sets “. These are individually defined in the System Requirements & Functions as well as the Quality…

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…

Knowledge Gaps

Today, product developments very rarely start “on the green field”. Depending on the competence of the organization, certain things are already known and can be reused. The P4 framework describes all unknown things as “Knowledge Gaps”. The idea behind this is that product development can be considered complete once all knowledge gaps have been turned…

Working Team

In addition to the Team System Engineer, the Working Team consists of the so-called Nucleus Team: these are persons who work in this Team for a predominant part of their working time (> 80%), plus the Extended Team: these are persons who work in a few teams (between 20% and 80%). Nucleus Team members sit…