Analysis: Common Scaling Methods of Decision Ownership
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Product Ownership Explored
2
Scrum/Scaling Oriented Methods
Tactical StrategicVoice of the Customer
3
1LeSS HugeArea Product OwnerProduct Owner- undefined -
4
2Scrum@ScaleProduct OwnerChief Product Owner- undefined -
5
3NexusProduct Owner HelperProduct Owner- undefined -
6
4Scaling Scrum with ScrumTeam CaptainBusiness OwnerProduct Champion
7
5SAFeProduct OwnerPortfolio Manager (and many more)Epic Owner
8
6Generic AgileTeam LeaderExecutiveChampion
9
7Enterprise ScrumProduct OwnerBusiness Owner- undefined -
10
8DADProduct OwnerKey Stakeholder- undefined -
11
9The Scrum HandbookTeam CaptainBusiness OwnerProduct Champion
12
10The Scrum GuideProduct Owner- undefined - - undefined -
13
11The Scrum Primer- undefined - Product Owner- undefined -
14
12Business Sloppy SpeakManagerDirectorSales
15
Summary Comments of Each Agile Method
Source
16
Large Scale Scrum (LeSS) relies on large stories to avoid scale and LeSS Huge is one layer up.
https://less.works
17
Scrum@Scale uses the word chief to add higher fractal layers i.e. CCPO, CCCPO
https://scruminc.com
18
Nexus does not appear to offer scale beyond one layer; there is only one Product Owner.
https://scrum.org
19
Scaled Agile Framework (SAFe) uses mutliple roles with various names to build a hierarchy.
https://www.scaledagileframework.com
20
Generic Agile is not really a method, there are many methods using a hodge podge of names.
(all over the web)
21
Enterprise Scrum uses the word Product Owner and adds-on in Business Owner.
https://enterprisescrum.com
22
Disciplined Agile Delivery relies on a key stakeholder or a 'Gold Holder"
https://disciplinedagiledelivery.com
23
The Scrum Handbook avoids a named Product Owner role and focuses on accountable decision making.
https://scrumzone.org/nine-zones-of-scrum
24
25
Summary Commnet
26
The table roughly summarizes how various methods have tried to address the concerns of Product Ownership. In all cases they have sought to address deficiencies in the descrptive language that causes confusion when implementing and the need to scale (up or down) arises.
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
Main menu