Artefacts

The Development Process defined by Backlog Items

Different types of Backlog Items define the development process at various levels. 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, i.e. clearly prioritized. The higher a backlog entry is,…

Design Jounal

A design journal is created for each system/product/application. In the format of a logbook, it contains … all design decisions and design changes that have been made. For each selected and implemented solution: The reasons that led to the change, and the solution options considered (with an analysis of the pros and cons). The contents…

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

Foundation of the P4-Dev Process

The P4-Dev Framework supports several different macro processes in product development: The knowledge- and maturity-based makro process This involves learning on the basis of development samples (e.g. prototypes). It is important that the knowledge-gaps are identified first and the development patterns (samples) are planned accordingly and not vice versa. This hybrid of the classic and…

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…