Sunteți pe pagina 1din 6

Use NO MORE than 15 Features - there is no way a group can effectively compare more than that (and the

charts start to real

Product owner completes the following:


Feature - what do you call it?
Description: put as much detail so as to eliminate all ambiguity on both business & technical levels.
Understand the following types, adjust the multipliers if desired.
Value type
Revenue generating
Value Added proposition
Usability enhancement

Value multiplier
3
2
1

Value Score: 1 - 10 level of business impact, relative to other features of the same Value type.

Dev team completes the following:


Story Point estimate
Story Point rationale (if necessary)

Once all values have been completed by Product Owner & Dev Team you may:
Reorder the data

Select the completed rows ** (including titles) then:


Data > Sort
Select the "Header row" option, then choose your "Sort by" criterion.
The charts will reflect your changes.
** DO NOT select the entire Data sheet for reordering, it will choke!

Comments, Questions?
Author
Email:
Revision date:

Bryan Liff, Minerva Group PSC


bliff@minerva-group.com
Sept. 7, 2009

at (and the charts start to really extend)

Sort by" criterion.

ng, it will choke!

Feature
Feature I
Feature II
Feature III
Feature "X"
Feature V
Feature IV
Feature "Y"

Description

Value Type
Revenue generating
Value Added proposition
Value Added proposition
Revenue generating
Usability enhancement
Revenue generating
Usability enhancement

Value Score Story Pt Est. Story Pt. rationale


7
3
6
4
7
5
9
13
5
3
4
8
8
8

Business value : Dev. Effort


7.00
3.00
2.80
2.08
1.67
1.50
1.00

% identified value
21.21%
12.12%
14.14%
27.27%
5.05%
12.12%
8.08%

21.21%
33.33%
47.47%
74.75%
79.80%
91.92%
100.00%

Business value : Dev. Effort

% identified value

S-ar putea să vă placă și