Acceptance Criteria

Acceptance criteria define conditions that must be met so that the affected Backlog Item is considered fulfilled. These can be refined requirements, special Quality Attributes or Constraints or boundary conditions (QA&C) of the described function, or procedural conditions during implementation. Estimates lead to good acceptance criteria. Good acceptance criteria lead to better estimates. During the…

Applications and Market Variants

Applications and market versions are integrated, tested and approved products of the organization that can be sold in target markets to customers. 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…

Organizational Artefacts

Die Organisation ist die oberste Ebene in P4 und organisiert das Portfolio. Hierfür besitzt die Organisation ein Portfolio-Backlog mit Applikationen als Elemente, ein Portfolio-Kanban-Board und die Organisations-DoD.

Cluster Artefacts

Jeder Cluster besteht aus mehreren Teams und unterteilt die Organisation in sinnvolle Wertströme. Er organisiert die verschiedenen Systeme, Applikationen (Produkte) und Märkte. Hierfür besitzt er ein Cluster-Backlog mit Systemversionen bestehend aus Features und Modulen als Elemente, ein Cluster-Kanban-Board und die Cluster-DoD.

Team Artefacts

Teams innerhalb der Organisation sind in Cluster strukturiert. Alle zukünftigen Arbeiten des Teams werden im Team-Backlog verwaltet. Aktuelle Arbeit wird im Iterations-Backlog oder auf einem Kanban-Board dargestellt. Je nach Team-Art, erzeugen Teams Features und Applikationen, Module und Systemplattformen oder Dienstleistungen (Services). Die Qualitätsansprüche des Teams sind in der Team-DoD aufgeführt.

Backlog (generic)

A Backlog is an ordered list of everything known that should be carried out by an organizational unit (Team , group, Cluster, Organization ) and serves as the only source of work by this organizational unit. The Product Owner is responsible for the Backlog, its content, access to it and the order of the entries.…

Backlog Item (generic)

A Backlog Item contains as attributes a description, an effort estimate, as well as Acceptance Criteria and Test Descriptions, which prove the completeness and describe when it is done. All backlog entries have the following properties and attributes: A unique short name or other identification (e.g. a number) A description that is as short as…

Cluster Backlog Item (CBI)

Cluster Backlog Items (CBI) are the individual elements (Backlog Items) of a Cluster Backlog and describe work for a Cluster. The size of  a CBI is initially not limited. It must be small enough in size or devided (refined in the Cluster Backlog Refinement) into several individual items that can be done in one ClusterCycle,…

Cluster Backlog, Cluster Cycle Backlog and Cluster Kanban

Each Cluster has exactly one Backlog for its area of ​​responsibility and tasks , the Cluster Backlog. In its simplest form, it consists of elements of just one System development that all Teams in the Cluster are working on. In this case, the Cluster Backlog can be referred to as the System Backlog. If the…