Artefacts

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.  

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,…

Organization DoD

Die Teams aller Cluster der Organisation, die Cluster-System-Engineer-Gruppe, die Cluster-Product-Owner-Gruppe und die Stakeholder müssen verstehen was es bedeutet, wenn ein Backlog-Eintrag oder ein Ergebnis als „Done“ bezeichnet wird. Obwohl sich die Cluster-DoDs erheblich von Cluster zu Cluster unterscheiden können, gibt es nur eine DoD auf Portfolio-Ebene für die gesamte Organisation.

Organisation Improvement Backlog

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant group, self-organized. A rule that describes how much work the group spends on improvements (e.g. 10-20%) helps to keep the predictability of other Backlog Items high. The Improvement Backlog is the planning and structuring tool of the…

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

Die oberste Ebene der Backlogs des P4-Frameworks, die Portfolio- und Organisationsebene, beschreibt Applikationen und Marktvarianten der Systeme und Produkte. Jede dieser Varianten wird durch einen Satz von System-Anforderungen (Feature Set) beschrieben.

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…

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…

Samples & Integrations (Backlog Item Type)

Samples & Integrations represent all work that is required to develop, build 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 learning.…