Artefacts

The Mission for Teams, Cluster and the Organization

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? What are the responsibilities of the team and…

Documentation of Product and Process

“We favor working software over comprehensive documentation”, Agile Manifesto, 2001. The above statement from the Agile Manifesto means that executable and functioning products/software/systems are more important than documentation. However, this does not mean that documentation is unimportant and can be omitted completely. An important criterion for documents is therefore that they are needed, especially whether…

Functional Safety Requirements

These are defined by the following standards, depending on the product type and intended use: Medical devices: ISO 60601, 62304 Automotive: IATF 16949 Industry: ISO 61508, ISO 13489

Improvement Backlog

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant organizational unit, self-organized. A rule that describes how much work the organizational unit spends on improvements over time (e.g. 10-20%) helps to keep the predictability of high, especially when Teams are young. The Improvement Backlog is the…

Inspectable Result

Each team organized within the P4 framework produces inspectable results, i.e. all team results can be checked for completeness and quality according to their acceptance criteria and the Definition of Done. The type of inspectable results can vary greatly depending on the type and responsibilities of the team. It is important that the team’s added…

Integrated System Sample (System increments)

System increments are partial or full integrations of system versions that are verified by internal or external tests and (depending on the degree of regulation) by user or market tests. System increments are often created at cluster level, i.e. by integrating sub-products from the various Teams in a Cluster. For the System increment, P4 has…

Internally provided Services

Internal services are the result of Service Teams.   Common attributes of Teams 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 the respective results and…

Lightweight Business Case (LBC)

The lightweight business case is borrowed from the SAFe framework and describes a feature in a lightweight way. It includes results of an initial analysis, such as effort and investment, as well as benefits and advantages to assess priority. Example of a LBC Description: What (is the problem?) What is the context? Stakeholders, Users, Markets:…

NABC

NABC is a method used for the development, assessment and presentation of ideas developed by the Standford Research Institute (SRI). The presented NABC-Canvas is a template to perform and write down the NABC procedure. NABC = Need, Approach, Benefit, Competition NABC Need describes the needs or problems of customers, stakeholders or users. Starting with the…

Usable Knowledge & Documented Decisions

Usable and documented knowledge is the basis of any system development. It makes it possible to make conscious design decisions. Usable Knowledge also represents the first stage of reuse (see principles). At a higher level, however, they also represens knowledge of the possibilities and limitations of integrated system solutions (Limits and Trade-offs). To achieve this,…