Scrum team Maturity assessment
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
DimensionTopic
Level of agreement
Score
2
Problem solvingProblems are openly adressed and discussedFully agree5
3
Problem solvingThe Scrum Master does not need to address problemsNeutral3
4
Problem solvingThe Scrum Master does not need to solve problemsDisagree2
5
CollaborationTeam members focus on shared team objectivesFully agree5
6
CollaborationActivities and collaboration is centered around customer valueFully agree5
7
Collaboration
Team members only discuss collaboration, not individual contribution
Disagree2
8
CollaborationThe team has removed all handover waiting pointsDisagree2
9
CollaborationTeam members contribute outside their specializationNeutral3
10
Getting things Done
Unfinished work does not accumulateDisagree2
11
Getting things Done
Team members pull new items only when something is DoneDisagree2
12
Getting things Done
Developers care about limiting Work in ProgressStrongly disagree1
13
Getting things Done
Team members solve blocks instead of picking up new itemsNeutral3
14
Getting things Done
Blocks get resolved quickly and effectivelyAgree4
15
Process changeThe team makes significant experiments with their process.Fully agree5
16
Process changeWe can not define our process, because it changes too quickly.Fully agree5
17
Process changeTeam members know where their process has bottlenecks.Neutral3
18
Process changeBottlenecks are actively resolvedFully agree5
19
Process changeProcess change happens anytime, even spontaneouslyFully agree5
20
Process changeTeams go new ways instead of perfecting a well-known processDisagree2
21
InteractionTeam members engage in difficult conversationsFully agree5
22
Interaction
Everyone (including Product Owner and Scrum Master) is available when needed
Fully agree5
23
Interaction
The Product Owner's opinion on results is known before the Review
Disagree2
24
InteractionTeam members discuss what they could do differentlyNeutral3
25
Ceremony - DailyDevelopers don't "report" during Daily ScrumFully agree5
26
Ceremony - DailyDevelopers talk about team goals during the Daily Scrum.Disagree2
27
Ceremony - DailyDevelopers are prepared for the Daily Scrum.Strongly disagree1
28
Ceremony - DailyDevelopers want to have a Daily Scrum.Disagree2
29
Ceremony - Refinement
Developers are aware of the subsequent Sprint content it starts.
Disagree2
30
Ceremony - Refinement
The Product Owner is aware of significant risks before Planning.Strongly disagree1
31
Ceremony - Refinement
There are no unpleasant surprises during Planning or delivery.Agree4
32
Ceremony - Refinement
PO, business and developers agree on backlog items before Planning.
Disagree2
33
Ceremony - Planning
Developers do more talking than the Product Owner during Planning.
Agree4
34
Ceremony - Planning
Developers focus on creating an effective plan.Agree4
35
Ceremony - Planning
Developers ask difficult questions.Agree4
36
Ceremony - Planning
Developers share a deep understanding of backlog items.Agree4
37
Ceremony - Planning
Developers can name the customer value of each backlog item.Agree4
38
Ceremony - ReviewStakeholders are excited to attend the Review.Disagree2
39
Ceremony - ReviewStakeholders use the Product during the Review.Disagree2
40
Ceremony - ReviewDevelopers learn from stakeholders during the Review.Disagree2
41
Ceremony - ReviewThe Review adds valuable learnings for the team.Disagree2
42
Ceremony - ReviewThe Review focuses on the product, not any support tool.Disagree2
43
Ceremony - ReviewThe Review is well-prepared.Fully agree5
44
Ceremony - RetroDevelopers reflect on themselves and their actionsDisagree2
45
Ceremony - RetroDevelopers challenge their processDisagree2
46
Ceremony - Retro
The Retrospective drills down to the root cause instead of fixing symptoms
Disagree2
47
Ceremony - RetroChanges proposed during a Retrospective are controversialDisagree2
48
Ceremony - Retro
Developers take risks to gain significant improvement opportunities
Disagree2
49
Ceremony - RetroDevelopers are prepared for the RetrospectiveDisagree2
50
Ceremony - RetroDevelopers take ownership of change initiativesDisagree2
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...
 
 
 
Assessment
Graph
Calculator
Map