{"id":1055,"date":"2019-10-05T18:16:39","date_gmt":"2019-10-05T16:16:39","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?page_id=1055"},"modified":"2026-02-10T12:17:31","modified_gmt":"2026-02-10T11:17:31","slug":"about","status":"publish","type":"page","link":"https:\/\/p4dev.hardscrum.com\/en\/about\/","title":{"rendered":"About P4-Dev: Pragmatic Paradigms, Princples and Practices"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <a href=\"http:\/\/p4dev.hardscrum.com\/\">P4-Dev framework<\/a> describes a modern type of organizational structure for companies that develop physical products. <\/span><span style=\"vertical-align: inherit;\">Together with its sister framework, the <a href=\"https:\/\/p4-ops.com\">P4-Ops<\/a> for the operational business, P4-Dev describes a holistic operating system for product dev and ops in modern organizations implementing the principles of lean and agility. <a href=\"https:\/\/p4-devops.com\">P4-DevOps<\/a> decribes the extensions that enable the conformance with mutiple process standards by using Process Mapping and ProcessAsCode. This is finally closing the gap between scaled lean &amp; pragmatic frameworks, and the process compliant, regulated, heavy and linear processes.<\/span><\/span><\/p>\n<h2><span style=\"color: #3366ff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P<\/span><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">ragmatic <\/span><\/span><span style=\"color: #3366ff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P<\/span><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">aradigms, <\/span><\/span><span style=\"color: #3366ff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P<\/span><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">rincipals &amp; <\/span><\/span><span style=\"color: #3366ff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P<\/span><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">ractices for Development<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The P4-Dev Framework (P4 for short) is based on the <\/span><\/span><a href=\"https:\/\/scrumguides.org\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Scrum framework<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and extends this with additional levels in order to be able to map organizations of size between 30 and approx. 1000 people. <\/span><span style=\"vertical-align: inherit;\">At these levels, additional roles, artifacts and events are defined according to the Scrum principles. <\/span><span style=\"vertical-align: inherit;\">Alternatively to using Scrum, teams can also apply Kanban.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P4 is divided into the description of Roles, Artifacts and Events:<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Roles: The description of the organization in the form of single roles, teams and groups<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Artifacts: The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">backlogs<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, backlog elements and <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlogitemtypes\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">element types<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, as well as the results and products<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Events: periods and meetings and their content<\/span><\/span><\/li>\n<\/ul>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Many of the pragmatic <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">principles<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and <\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">practices described<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> are known from other systems and frameworks and are integrated holistically in the P4 framework:<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Toyota Product Development System: continuous workflow and pull principle<\/span><\/span><\/li>\n<li><a href=\"http:\/\/p4dev.hardscrum.com\/mapping-p4-to-safe\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Scaled Agile Framework (SAFe)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, <\/span><\/span><a href=\"https:\/\/less.works\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Large Scale Scrum (LeSS)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , <\/span><\/span><a href=\"https:\/\/www.scrum.org\/node\/4709\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Nexus<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , <\/span><\/span><a href=\"https:\/\/www.scrumatscale.com\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Scrum @ Scale<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> : Scaling agile teams<\/span><\/span><\/li>\n<li><a href=\"http:\/\/theleanstartup.com\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Lean Startup<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">: Fast learning and adaptation with the market<\/span><\/span><\/li>\n<li><a href=\"https:\/\/de.wikipedia.org\/wiki\/Design_Thinking\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Design Thinking<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">: Exploration of the problem and solution space by quickly generating prototypes<\/span><\/span><\/li>\n<li><a href=\"https:\/\/www.lean.org\/leanpd\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Lean Product &amp; Process Development (LPPD)<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">: knowledge-based development, visible knowledge and set-based design<\/span><\/span><\/li>\n<li><a href=\"https:\/\/de.wikipedia.org\/wiki\/Theory_of_Constraints\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Theory-of-constraints and critical chain<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> : The regulation of workflows by aligning them, and the optimization of bottlenecks (constraints)<\/span><\/span><\/li>\n<\/ul>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Why another agile scaling framework?<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Although there are a number of frameworks for scaling agility, they lack some elements that are particularly necessary for the development of physical products and complex systems. <\/span><span style=\"vertical-align: inherit;\">Therefore, we have integrated the following additional elements into the P4 framework:<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rportfoliolevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">P4 organizational structure<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> takes into account not only <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/application-team\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">interdisciplinary (cross-functional) teams with responsibility for features, products or applications<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, but also <a href=\"https:\/\/p4dev.hardscrum.com\/module-team\/\">supplying Module, Component and platform teams<\/a>, as well as <a href=\"https:\/\/p4dev.hardscrum.com\/service-team\/\">teams that provide special expertise as a service to other teams<\/a> . <\/span><span style=\"vertical-align: inherit;\">The high level of specialization in modern system development makes the different types of teams necessary. <\/span><span style=\"vertical-align: inherit;\">In the P4 framework we call these team types &#8220;team flavors&#8221;.<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In addition to the roles of <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/marketbusiness\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Product Owner<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/infrastructureprocesses\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Scrum Master<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, P4 introduces the role of the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/technologyarchitecture\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System Engineer<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, in which the responsibility for the technology and architecture of a Team is bundled. <\/span><span style=\"vertical-align: inherit;\">The System Engineer also represents his team&#8217;s technological expertise at the next higher scaling level.<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">For the training and further education of members of interdisciplinary teams, as well as the joint further development of internally used tools, P4 integrates the ideas of <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Communities of Practice<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> .<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">At the scaling <\/span><span style=\"vertical-align: inherit;\">levels <\/span><span style=\"vertical-align: inherit;\">(<\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cluster<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rportfoliolevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organization<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">), groups are formed from members of the &#8220;lower&#8221; level. <\/span><span style=\"vertical-align: inherit;\">This <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles#ueberlappung\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">overlap principle<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> simplifies the information flow between the levels. <\/span><span style=\"vertical-align: inherit;\">Events at all levels are decoupled by the so-called <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/year\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Cadence<\/span><\/span><\/a>.<span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> It provides a kind of &#8220;timetable&#8221; for the Organization.<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlogitemtypes\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Backlog Structure<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and its partly new elements support the developments of physical products and represent a procedure guide. In particular, the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/knowledgegaps\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">concept of Knowledge Gaps<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> enables structured knowledge-based development and iterative learning.<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The collaboration model of <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Nucleus, Extended Team, Supporter<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/stakeholder\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Stakeholder<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> integrated in P4 <\/span><span style=\"vertical-align: inherit;\">expands the simple Scrum model (employees are completely or not at all in a team) and thus supports the collaboration of experts with several but few teams. <\/span><span style=\"vertical-align: inherit;\">The collaboration is fully integrated into the organization&#8217;s events.<\/span><\/span><\/li>\n<\/ul>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Extensions<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In addition to the practices described above, tried and tested elements from classic methods are integrated into the &#8220;P4 toolbox&#8221;, such as requirements management, test management, risk management, as well as model-based systems engineering (MBSE).<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Since P4 is a framework, other beneficial and deemed necessary practices can be integrated. <\/span><span style=\"vertical-align: inherit;\">However, it is essential to ensure that the P4 principles are observed ( <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">see P4 principles<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ).<\/span><\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">What is different from the classic matrix organization?<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">A classic matrix organization usually consists of the specialist departments (the lines or &#8220;silos&#8221;) and a project organization in which interdisciplinary collaboration is carried out in many parallel projects. <\/span><span style=\"vertical-align: inherit;\">Each employee usually works in several projects at the same time. <\/span><span style=\"vertical-align: inherit;\">In large companies there is sometimes a third dimension, which divides the line organization into an international and a location-based line with the corresponding additional superiors (sometimes referred to as &#8220;dotted line&#8221;).<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In today&#8217;s world of work, this &#8220;serving several masters&#8221; is often a problem, since most of the work is done in the projects, but the project managers are often less empowered and in the event of a conflict, the line managers usually prevail. <\/span><span style=\"vertical-align: inherit;\">This is reinforced by the large number of line managers in the interdisciplinary project team, who are mostly driven by different goals, local efficiencies and therefore acting in different directions.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In modern agile frameworks, such as P4-Dev, the balance of power of the matrix is \u200b\u200breversed: the team that is stable over time and in which an employee is located has the strongest \u201cbond\u201d and is allocated the most capacity of the employee, ideally 100%. <\/span><span style=\"vertical-align: inherit;\">An employee working for several teams (Extended Team member) is only an exceptional case. <\/span><span style=\"vertical-align: inherit;\">The type of team (in P4 \u201cteam flavor\u201d) defines whether a team works interdisciplinary with Product responsibility, partly interdisciplinary with Component, Module or Platform responsibility or as a specialist group, e.g. as a service team with a certain technical competence.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The classical technical lines merge into the so-called \u201c<\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Communities-of-practice<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, where the employees exchange content, where training takes place, and technologies and tools are maintained and further developed.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Teams that work together on the same products or product groups organize themselves in a cluster, similar to the &#8220;Agile Release Train&#8221;, the &#8220;Value Stream&#8221; or the &#8220;Program Level&#8221; in other agile frameworks. <\/span><span style=\"vertical-align: inherit;\">The overall organization consists of several <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Clusters<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> that are responsible for different product areas. <\/span><span style=\"vertical-align: inherit;\">This creates clear priorities as well as a high degree of coherence between the goals and responsibility of the teams in the cluster.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In P4 there are no projects, no project managers nor project teams. <\/span><span style=\"vertical-align: inherit;\">Contents of product development projects are represented in the backlogs of the Organization as large backlog items of the Clusters and the Teams. <\/span><span style=\"vertical-align: inherit;\">The projects most closely correspond to the system or application versions (releases) planned at the Organization\/Portfolio level.<\/span><\/span><\/p>\n<p><strong>Continue reading?<\/strong> <a href=\"http:\/\/p4dev.hardscrum.com\/introducing-p4\/\">How to implement P4 (An agile Journey)<\/a>.<\/p>\n<hr \/>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles\">Principles of the P4 framework<\/a> | <a href=\"http:\/\/p4dev.hardscrum.com\/p4news\/\">News\u00a0<\/a> |\u00a0 <a href=\"http:\/\/p4dev.hardscrum.com\/p4faq\/\">FAQs<\/a>\u00a0 |\u00a0 <a href=\"https:\/\/p4dev.hardscrum.com\/\">Main page<\/a><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr style=\"background-color: #f8f8f8;\">\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr style=\"background-color: #ffffff;\">\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\">Team Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Team Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\">Team Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\">Cluster Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\">Cluster Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\">Cluster Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\">Cluster Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\">Cluster Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-planning\/\">Portfolio Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisation-sync\/\">Organisation Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\">Portfolio Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-review\/\">Portfolio Review<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\">Organisation Retrospective<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\">Team System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\">Team Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\">Cluster Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\">Cluster System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\">Portfolio Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\">Portfolio Architect<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\">Organisation Scrum Master<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\">Working Team<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\">Community of Practice<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">Team Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\">Team System Engineer Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\">Team Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\">Cluster Management Circle<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\">Cluster Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\">Cluster System Engineer Group<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\">Cluster Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\">Organisation Management Circle<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/ateamlevel\/\">Inspectable Results<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Team DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/improvementbacklog\/\">Team Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\">Cluster Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/usableknowledge\/\">Usable Knowledge<\/a> &amp; <a href=\"http:\/\/p4dev.hardscrum.com\/systemincrement\/\">System Increment<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\">Cluster DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\">Cluster Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\">Portfolio Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioproduct\/\">Systems &amp; Applications<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/applications\/\">System Platforms &amp; Variants<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\">Organisation DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioimprovementbacklog\/\">Organisation Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"The P4-Dev framework describes a modern type of organizational structure for companies that develop physical products. Together with its sister framework, the P4-Ops for the operational business, P4-Dev describes a holistic operating system for product dev and ops in modern organizations implementing the principles of lean and agility. P4-DevOps decribes the extensions that enable the&hellip;","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/pages\/1055"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=1055"}],"version-history":[{"count":39,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/pages\/1055\/revisions"}],"predecessor-version":[{"id":2093,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/pages\/1055\/revisions\/2093"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=1055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}