test_c
Mid-level artefact C. Inherited (included): Highest level artefact A. Highest level artefact b.
Artefacts
test_d
Low-level artefact D. Inherited (included): Mid-level artefact C. Inherited (included): Highest level artefact A. Highest level artefact b.
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,…
Environmental Requirements
These are defined by the following standards, depending on the makets and areas: ISO 14001 WEEE RoHS European PFAS Directive …
Use Case
Use Cases are used to describe scenarios in which users and other stakeholders interact with the system. Use Cases are a good method for describing functional requirements and dynamic behavior of the system. Many non-functional requirements can also be discovered during the analysis. In order not to forget any essential Use Cases during the requirements…
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…