Artefacts

Portfolio Backlog Item (PFBI)

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

Portfolio Backlog, Portfolio Cycle Backlog & Portfolio Kanban

The top level of the Backlogs of the P4 framework, the Portfolio and Organizational level , describes all Applications and market variants of the Systems and Products to be develped in the entire Organization. Each of these variants is described by a set of System Requirements (feature set). In this way, the Application, systems &…

Products, Applications and Market Variants

The Portfolio Backlog at the Organizational level, the top level of all Backlogs, contains Systems, Products and Application variants, as well as product variants for special markets. Each of these product variants is described by a set of System Requirements (feature set). In this way, the product variants can be estimated against each other with…

Product Vision / Business Case

The product vision describes in compact form … the Intended Use, for which users, in which markets the product is intended, which are the basic requirements and standards what are the main functions of the product how the product fits into the application context and what interfaces it has with surrounding systems. There are different…

Quality Attributes & Constraints

Quality attributes are Non-Functional Requirements that more or less restrict the Functions and features of a system. These are mostly “How” questions, i.e. how fast, how big, how heavy, how expensive, how long-lasting, how robust, how safe? These requirements often have to be balanced against each other. For this purpose, minimum achievable and desired values…

Risk impact of K-Gaps and Decisions

In every product development, there are design decisions that make the whole concept fly or make it impossible. These naturally have the greatest (risk) impact and should therefore be made first. The decision tree answers the question of the importance and influence of Knowledge Gaps, and thus the order of processing and solution in the…

Samples & Integrations (Backlog Item Type)

Samples & Integrations represent all work that is required to develop, build, integrate and test prototype samples (whether virtual or physical). These Samples can be concepts, simulations, prototypical partial assemblies, virtual prototypes, rapid prototypes, up to pre-series samples, which may be tested in user studies. Samples & Integrations are created  to close Knowledge Gaps through…

Stakeholder Needs

Stakeholders are all persons and groups of people affected by a system, as well as everyone directly interested or involved in the product. Stakeholders are invited to the reviews at all levels and can optionally be invited to backlog refinement meetings to explain their requirements. In order to identify stakeholders, the P4 framework uses two…

Stakeholder Story

In the P4 framework, the Stakeholder Story represents the extension of the User Story to all stakeholders. It can and should be used to formulate the needs and requirements of all Stakeholders for the product. These are much more than just the users, especially in the environment of physical product development. Stakeholder Stories can also…