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.<\/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 Team Improvement Backlog<\/strong>, which the\u00a0 <\/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>\u00a0<\/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 <\/span><\/span>Organization Improvement Backlog<\/span><\/span><\/a>, which the <\/span><\/span>Organization Scrum Master<\/span><\/span><\/a> prioritizes <\/span>with the <\/span><\/span>Cluster Scrum Master Group<\/span><\/span><\/a> . <\/span>The <\/span><\/span>Organization Improvement Backlog<\/span><\/span><\/a> is mostly fed from the cluster’s suggestions for Improvement.<\/span><\/span><\/p>\n <\/p>\n Further suitable links:<\/p>\n
\n