Areas

Organization Retrospective

The Organization Retrospective offers the Organization Scrum Master (OSM) the opportunity to review the working methods of the organization, represented by the Portfolio Owner (PFO) and the Cluster System Engineer Group (CSEG) , as well as improvements to the Identify and plan how to work for the coming cycle . The Organization Retrospective takes place…

P4-Ops

P4-Ops describes the Operation of an organization. It is divided into the following areas: Product Management, Sales and Marketing Supply chain (purchasing, production, shipping Application Engineering, Service, Support/Hotline, Trainings Infrastructure Services (IT, HR, accounting and site management) are shared with the Clusters and Teams of product developement.     The P4-Ops framework alone is sufficient…

Portfolio Architect (PFA)

With the Cluster System Engineer Group at Portfolio and organizational level, the Portfolio architect is responsible for the technology and architecture side of the entire product development process. The Portfolio architect forms the management of the entire Organization together with the Portfolio Owner and the Organization Scrum Master .   Together with the Portfolio architect,…

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

Portfolio Owner (PFO)

The Portfolio Owner is the “Product Owner” of the Organization and has the overall responsibility for the Market and Business side of the product development on the Portfolio / Organizational level, together with the Cluster Product Owner Group (CPOG). (A general description of the Product Owner role can be found here.)   Together with the Portfolio…

Product Development

  1. Elicit System Functions and Features –Define Context & Scope (Intended use, environments, markets) –Stakeholders & Needs, external interfaces –Quality Attributes, System Use Cases 2.Model a coarse System Architecture/Concept incl. test and production systems (Multiple options maybe necessary) –Output: Components and interfaces 3.Determine maturity of concepts, components and interfaces by gatherings K-Gaps (unknown concepts,…

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…

Process Management

Process management is the set of activities involved in planning, defining, and improving processes and workflows across the entire organization.

System Requirements & Functions

Systems are described at the top level by System Requirements and Functions (features). Requirements only describe abilities or properties in the “problem area”, so they are still independent of concrete system solutions. The solution space is already limited by the Quality Attributes & Constraints . Interfaces to neighboring systems in the environment and their properties…

System Increment

System increments are partial or full integrations of system versions that are verified by internal or external tests, as well as by user and / or market tests. System increments are mostly created by the Application teams of the Cluster i.e. by integrating partial results of the different teams of a cluster (module and platform…