Value score
×
Driver weight
→
Driver BVP
Σ
=
Total BVP
// 01 · Value driver
Derived from values
Drivers come from the agreed business values and the enterprise assurance objectives — the eight, in opsasto's case.
// 02 · Value score
0 – 5
0 the feature does not support this driver. 5 it completely supports it.
// 03 · Driver weight
0 – 9
0 weightless for this organisation. 9 ultra-heavy — the kind of priority you would not skip.
A famous quote from Peter Drucker says "There is nothing so useless as doing efficiently that which should not be done at all "
Businesses do not always have a clear and uniform apporach for prioritsing features in a product backlog.
Business Values Points can help to rationlize the feature priotisation decision making process.
- Value drivers are derived from an agreed set of business values ,- and enterprise assurance objectives
- BVP can easily be calculated by answering a few questions, for each value driver we ask how much the proposed feature is supporting the value
- The BVP is calculated by multiplying the value score (0 does not support <-->5 completely support) with value driver weight (0 weightless<-->9 ultra heavy
BVP on their own are good to compare feature request with each other. BVP standalone do not offer collateral to asses the costs of investment or to evaluate the economic return. However You can set BVP of against costs to create a "heatmap".
- Define criteria for Low Risk , Low costs Features that the workstream can decide to pick-up by themselves (? irm ok, no arch impact, high business value, L&R needs)
- Reserve a percentage of the budget to support this