Portfolio Backlog Refinement

Refinement of the Portfolio Backlog is the process of adding details to backlog entries, making estimates, splitting backlog entries, or changing the order of entries 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 entries. The entries are examined and revised as the Portfolio Backlog is refined. However, the Portfolio Owner can update or have the entries in the Portfolio Backlog updated at any time.

The Portfolio Backlog refinement is mainly used to prepare the next Portfolio Planning . The Portfolio Owner of the Cluster System Engineer Group (CSEG) presents new backlog entries and has them estimated. This is a prerequisite for the “pull” of the CSEG and is often referred to as definition-of-ready . In the case of unclear but highly prioritized backlog entries, the CSEG clarifies the System Requirements , possible System Concepts and capabilities . This can be worked out as a group or a corresponding backlog entry can be created as an order for one of the Clusters.

Estimation of the effort required to implement backlog entries

Estimates by the entire Cluster System Engineer Group are important for two reasons:

1. By jointly estimating, the CSEG analyzes the respective backlog entry from different perspectives and enriches it with information such as acceptance criteria and boundary conditions. The first ideas for implementation are also generated.
2. The result of the estimation is a number with which individual backlog elements can be evaluated, for example for prioritization. In addition, it is now easy to calculate how many backlog elements can be dragged into a cycle, namely by comparing the backlog elements completed in the last cycles ( organization velocity ).

The team uses the Planning-Poker ® methodology to estimate the effort .

Further suitable links:\r\n

Further suitable links: