{"id":1248,"date":"2019-10-14T21:06:16","date_gmt":"2019-10-14T19:06:16","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1248"},"modified":"2023-08-09T22:13:54","modified_gmt":"2023-08-09T20:13:54","slug":"portfolioimprovementbacklog","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/portfolioimprovementbacklog\/","title":{"rendered":"Organisation Improvement Backlog"},"content":{"rendered":"

The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant group, self-organized. A rule that describes how much work the group spends on improvements (e.g. 10-20%) helps to keep the predictability of other Backlog Items high.<\/span><\/span><\/p>\n

The Improvement Backlog is the planning and structuring tool of the <\/span><\/span>Scrum Master<\/span><\/span><\/a>. <\/span>There are Improvement Backlogs on all three levels of the P4 framework (<\/span><\/span>Team<\/span><\/span><\/a>, <\/span><\/span>Cluster<\/span><\/span><\/a>, <\/span><\/span>Organization<\/span><\/span><\/a>).<\/span><\/span><\/p>\n

Each Team<\/a> that identifies more improvements than can currently be implemented stores these improvements in their <\/span><\/span>Team Improvement Backlog<\/span><\/span><\/a>, which the <\/span><\/span>Team Scrum Master<\/span><\/span><\/a> prioritizes <\/span>with the <\/span><\/span>Team<\/span><\/span><\/a> .<\/span><\/span><\/p>\n

The sum of the improvements of a Cluster<\/a> is located in the <\/span><\/span>Cluster Improvement Backlog, <\/span><\/span><\/a>which the <\/span><\/span>Cluster Scrum Master<\/span><\/span><\/a> prioritizes <\/span>with the <\/span><\/span>Team Scrum Master Group<\/span><\/span><\/a> . <\/span>The <\/span><\/span>Cluster Improvement Backlog<\/span><\/span><\/a> is mostly fed by the Teams’ suggestions for improvement.<\/span><\/span><\/p>\n

The total of an Organization’s improvements is in the Organization Improvement Backlog<\/strong>, which the <\/span><\/span>Organization Scrum Master<\/span><\/span><\/a> prioritizes <\/span>with the <\/span><\/span>Cluster Scrum Master Group. <\/span><\/span><\/a>The Organization Improvement Backlog<\/strong> is mostly fed from the Cluster’s suggestions for improvement.<\/span><\/span><\/p>\n

.<\/span><\/span><\/span><\/p>\n

 <\/p>\n

\n

Further suitable links:<\/p>\n\n\n\n\n
Events<\/td>\nRoles<\/td>\nGroups<\/td>\nArtifacts<\/td>\n<\/tr>\n
Portfolio Planning<\/a><\/p>\n

Organisation Sync<\/a><\/p>\n

Portfolio Refinement<\/a><\/p>\n

Portfolio Review<\/a><\/p>\n

Organisation Retrospective<\/a><\/td>\n

Portfolio Owner<\/a><\/p>\n

Portfolio Architect<\/a><\/p>\n

Organisation Scrum Master<\/a><\/td>\n

Cluster Product Owner Group<\/a><\/p>\n

Cluster System Engineer Group<\/a><\/p>\n

Cluster Scrum Master Group<\/a><\/p>\n

Organisation Management Circle<\/a><\/td>\n

Team Improvement Backlog<\/a><\/p>\n

.<\/span><\/p>\n

Cluster Improvement Backlog<\/a><\/p>\n

.<\/span><\/p>\n

Portfolio Backlog<\/a><\/p>\n

Systems & Applications<\/a><\/p>\n

System Platforms & Variants<\/a><\/p>\n

Organisation DoD<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"The Improvement Backlog describes the supply of improvements and is integrated into the work planning by the relevant group, self-organized. A rule that describes how much work the group spends on improvements (e.g. 10-20%) helps to keep the predictability of other Backlog Items high. The Improvement Backlog is the planning and structuring tool of the…","protected":false},"author":3,"featured_media":1432,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[20,23,34],"tags":[363],"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\/1248"}],"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=1248"}],"version-history":[{"count":17,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1248\/revisions"}],"predecessor-version":[{"id":2771,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1248\/revisions\/2771"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1432"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=1248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}