Organizational Levels

Organisation Sync

Organizational Sync (Scrum-of-Scrums-of-Scrums) This event enables several Clusters to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. during ongoing work. The Clusters themselves decide how often this is needed (e.g. daily, weekly). The representatives of the Cluster can be the Cluster System Engineers of the Clusters. However, other…

Modelling the organization

With organizational modeling, the specific organization is modeled by P4 elements, i.e. the teams, groups and Clusters are represented by their information and work flows. The processes can now be represented within the organizational model, whereby this is done by defining and documenting the corresponding inputs, responsibilities, actions and outputs. Every  organizational unit is described…

P4N – The P4 Network

The P4N is a network of organizations using the P4 Framework, as well as consultants and coaches who are committed to the introduction of agile structures in accordance with the P4 Framework, the support of teams and the development of the framework. The P4N thus forms the bridge and the exchange platform between various organizations,…

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 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 Refinement

Refinement of the Portfolio Backlog is the process of creating new backlog items, adding details to backlog items, making estimates, splitting backlog items, or changing the order of items in the Portfolio Backlog. Refinement is a continuous process in which the Portfolio Owner and the Cluster System Engineer Group (CSEG) jointly detail the Portfolio Backlog…

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