Organization Level

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 Cycle

The basic idea of the Iteration as a time-box for the Teams is used at Organization level by the Portfolio Cycle as a larger fixed period as a basic rhythm for the Organization. Frequently, the System versions, products and Applications are also brought to the market in the rhythm of the Portfolio Cycles. The advantage of…

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…

Portfolio Planning

Planning at the Portfolio level is a semi-continuous process in the P4 framework, just like budget planning, for example, which is closely linked to Portfolio Planning. The planning process consists of the preparation through the Portfolio refinement and the Portfolio Planning event. The planning process takes place at the level of the Portfolio Backlog elements.…

Portfolio Review

At the end of each Portfolio Cycle, a Portfolio Review is held in which the Cluster System Engineer Group (CSEG) and the Portfolio Owner (PFO) present the results to the Stakeholders. They receive feedback from the Stakeholders on the results so that the Portfolio Owner can adjust the Portfolio Backlog if necessary . Along with any…

Practice Lead

Practice leads are professional coaches or trainers within the organization who take care of expertise or technical discipline. They lead a community of practice , train their members and take care of the further development of the topic and the employees within the Organization. In the transition from classic organizations, the former line managers can…

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…

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…