{"id":658,"date":"2019-08-21T22:35:22","date_gmt":"2019-08-21T20:35:22","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=658"},"modified":"2024-05-17T13:31:34","modified_gmt":"2024-05-17T11:31:34","slug":"clusterproduct","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/clusterproduct\/","title":{"rendered":"Integrated System Sample (System increments)"},"content":{"rendered":"<p>System increments are partial or full integrations of system versions that are verified by internal or external tests and (depending on the degree of regulation) by user or market tests.<\/p>\n<p>System increments are often created at cluster level, i.e. by integrating sub-products from the various Teams in a Cluster.<\/p>\n<p>For the System increment, P4 has adopted the types and definitions of patterns from the Design Thinking Framework. They also define the maturity levels of the samples.<\/p>\n<p>The maturity level is ultimately defined by the type and number of knowledge gaps. Samples are created to close <a href=\"https:\/\/p4dev.hardscrum.com\/knowledgegaps\/\">Knowledge Gaps<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr>\n<td width=\"123\"><strong>Prototype<\/strong><\/td>\n<td width=\"180\"><strong>Name<\/strong><\/td>\n<td width=\"302\"><strong>Description<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>B<\/strong><\/td>\n<td width=\"180\"><strong>B<\/strong>ase Prototype<\/td>\n<td width=\"302\">for design space exploration<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>C<\/strong><\/td>\n<td width=\"180\"><strong>C<\/strong>ritical Function Prototype<\/td>\n<td width=\"302\">Need finding; feasibility; fail early<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>D<\/strong><\/td>\n<td width=\"180\"><strong>D<\/strong>ark Horse Prototype<\/td>\n<td width=\"302\">The alternative; thinking out of the box<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>E<\/strong><\/td>\n<td width=\"180\"><strong>E<\/strong>mergent Prototype<\/td>\n<td width=\"302\">Combining several Functions and ideas; iterative and incremental<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>F<\/strong><\/td>\n<td width=\"180\"><strong>F<\/strong>unctional Prototype<\/td>\n<td width=\"302\">Fully functional, but differs in (e.g. form-factor)<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>G<\/strong><\/td>\n<td width=\"180\"><strong>G<\/strong>ap Closing Prototype<\/td>\n<td width=\"302\">Specific to close Knowledge Gaps or prove Hypotheses<\/td>\n<\/tr>\n<tr>\n<td width=\"123\"><strong>H<\/strong><\/td>\n<td width=\"180\"><strong>H<\/strong>indmost Prototype<\/td>\n<td width=\"302\">Closest to series production<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"text-align: left;\">All Prototype can appear as iterating Prototypes, like G1, G2, G3.<\/p>\n<p>&nbsp;<\/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\/cycleplanning\/\"><span style=\"color: #333333;\">Cluster Planning<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\"><span style=\"color: #333333;\">Cluster Sync<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\"><span style=\"color: #333333;\">Cluster Backlog Refinement<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\"><span style=\"color: #333333;\">Cluster Review<\/span><\/a><\/td>\n<td><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\"><span style=\"color: #333333;\">Cluster Product Owner<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\"><span style=\"color: #333333;\">Cluster System Engineer<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\"><span style=\"color: #333333;\">Portfolio Owner<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\"><span style=\"color: #333333;\">Portfolio Architect<\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\"><span style=\"color: #333333;\">Team Product Owner Group<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\"><span style=\"color: #333333;\">Team System Engineer Group<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\"><span style=\"color: #333333;\">Cluster Product Owner Group<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\"><span style=\"color: #333333;\">Cluster System Engineer Group<\/span><\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/ateamlevel\/\"><span style=\"color: #333333;\">Inspectable Results<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\"><span style=\"color: #333333;\">Team DoD<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><span style=\"color: #333333;\"><a href=\"http:\/\/p4dev.hardscrum.com\/usableknowledge\/\">Usable Knowledge<\/a> &amp; <a href=\"http:\/\/p4dev.hardscrum.com\/systemincrement\/\">System Increment<\/a><\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\"><span style=\"color: #333333;\">Cluster DoD<\/span><\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioproduct\/\"><span style=\"color: #333333;\">Systems &amp; Applications<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/applications\/\"><span style=\"color: #333333;\">System Platforms &amp; Variants<\/span><\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\"><span style=\"color: #333333;\">Organisation DoD<\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"System increments are partial or full integrations of system versions that are verified by internal or external tests and (depending on the degree of regulation) by user or market tests. System increments are often created at cluster level, i.e. by integrating sub-products from the various Teams in a Cluster. For the System increment, P4 has&hellip;","protected":false},"author":3,"featured_media":902,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,19],"tags":[],"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\/posts\/658"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=658"}],"version-history":[{"count":10,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/658\/revisions"}],"predecessor-version":[{"id":662,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/658\/revisions\/662"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/902"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=658"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=658"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}