Definitions: the word “developers” in the following questions refer to anyone on the team that builds the product (coders, testers, analysts, architects, UX analysts, etc.); while this may not be the same as your organization’s definition, it is the one we use in Scrum and throughout this assessment.
Instructions: answer each question honestly; evaluate your current situation, don’t answer where you would like to be; do not go back and change an answer once you’ve answered; read each question and answer it before moving on (initial reactions are important).
Note: all responses are confidential and used ONLY for summary reporting purposes and research. Names, emails, IP addresses, and other identifying information is neither collected nor stored.
THANK YOU!!!!
Quiz Summary
0 of 176 Questions completed
Questions:
Information
You have already completed the quiz before. Hence you can not start it again.
Quiz is loading…
You must sign in or sign up to start the quiz.
You must first complete the following:
Results
Results
Time has elapsed
Categories
- Not categorized 0%
- alignment 0%
- collaboration 0%
- cost-focused 0%
- goal-focused 0%
- lean 0%
- product ownership 0%
- psychological safety 0%
- quality-focused 0%
- self-managing 0%
- technical skills 0%
- value-focused 0%
-
Thank you VERY much for your participation. We’re going to review your anonymous responses with everyone else’s in your organization and put together a plan to help you create an amazing work environment!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 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
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
- 131
- 132
- 133
- 134
- 135
- 136
- 137
- 138
- 139
- 140
- 141
- 142
- 143
- 144
- 145
- 146
- 147
- 148
- 149
- 150
- 151
- 152
- 153
- 154
- 155
- 156
- 157
- 158
- 159
- 160
- 161
- 162
- 163
- 164
- 165
- 166
- 167
- 168
- 169
- 170
- 171
- 172
- 173
- 174
- 175
- 176
- Current
- Review
- Answered
- Correct
- Incorrect
-
Question 1 of 176
1. Question
My team’s DONEness definition is aligned with other teams on the same product
-
Question 2 of 176
2. Question
I know what other teams are working on and how their work relates to my teams’ work.
-
Question 3 of 176
3. Question
I find out what other teams on my product are doing when something breaks or has to be redone.
-
Question 4 of 176
4. Question
Release goals are communicated to the Development Teams without our input.
-
Question 5 of 176
5. Question
Release goals are set realistically; based on team capability and capacity.
-
Question 6 of 176
6. Question
I look for opportunities to expand my skill set in ways that supports my team’s success.
-
Question 7 of 176
7. Question
I feel that if someone can’t do the job its not my job to help them learn how.
-
Question 8 of 176
8. Question
If someone on my team needs help I help only if I have time and know what to do.
-
Question 9 of 176
9. Question
My team mates regularly check to see if anyone needs help.
-
Question 10 of 176
10. Question
Team members are assigned PBIs and work independently.
-
Question 11 of 176
11. Question
I work side-by-side (in-person or virtually) with my teammates.
-
Question 12 of 176
12. Question
I work by myself checking in with the team as needed.
-
Question 13 of 176
13. Question
Its best if the best person for a task works on that task.
-
Question 14 of 176
14. Question
Work on my team passes from person to person depending on the skills needed.
-
Question 15 of 176
15. Question
People on my team frequently don’t have enough to do because they are waiting on other team members.
-
Question 16 of 176
16. Question
Work is handed off from one person to another on its way to getting done.
-
Question 17 of 176
17. Question
My team’s Sprint Reviews include an evaluation of the product and what we need to do to stay on schedule.
-
Question 18 of 176
18. Question
It is easy to identify when a product backlog item was originally created for the customer.
-
Question 19 of 176
19. Question
My team works on product backlog items that are more than two years old.
-
Question 20 of 176
20. Question
The output of my team’s Sprints works and is production quality; even if not yet valuable enough for the customer.
-
Question 21 of 176
21. Question
My team does not work on product backlog items that are not clearly and completely defined.
-
Question 22 of 176
22. Question
My team is OK working on a product backlog item that we don’t completely understand.
-
Question 23 of 176
23. Question
My team works with the product owner to trade off functionality for schedule.
-
Question 24 of 176
24. Question
My teams finds that Sprint Goals make a big difference keeping the team focused.
-
Question 25 of 176
25. Question
My team uses Daily Scrums to ensure that we are always tracking toward the Sprint Goal.
-
Question 26 of 176
26. Question
My team uses Sprint Goals with every Sprint
-
Question 27 of 176
27. Question
My teams product goals are reviewed and updated in Sprint Review.
-
Question 28 of 176
28. Question
My team plans only what we know we can complete in a Sprint.
-
Question 29 of 176
29. Question
My team has more than one product backlog item left incomplete by the end of the Sprint.
-
Question 30 of 176
30. Question
If a work item cannot be done for reasons beyond our control; we renegotiate the iteration content with the product owner.
-
Question 31 of 176
31. Question
My team finishes everything they planned in Sprint Planning.
-
Question 32 of 176
32. Question
My team shortens or lengthens Sprints when necessary.
-
Question 33 of 176
33. Question
My team lengthens Sprints when necessary.
-
Question 34 of 176
34. Question
The team creates a Sprint Goal at Sprint Planning.
-
Question 35 of 176
35. Question
The team celebrates successful Sprints and successful goal achievement.
-
Question 36 of 176
36. Question
Team members help each other out frequently.
-
Question 37 of 176
37. Question
The team is focused on getting everything done that we planned into the Sprint.
-
Question 38 of 176
38. Question
My team creates a comprehensive sprint plan during Sprint Planning.
-
Question 39 of 176
39. Question
During Sprint Planning my team identifies risks and potential blocks and creates plans to mitigate them.
-
Question 40 of 176
40. Question
My team uses Sprint Planning primarily to identify which backlog items will be completed during the Sprint.
-
Question 41 of 176
41. Question
My team’s Sprint Planning events don’t run longer than one hour.
-
Question 42 of 176
42. Question
During Sprint Planning my team identifies how vacations and holidays might effect the Sprint.
-
Question 43 of 176
43. Question
During Sprint Planning my team identifies who owns each product backlog item included in the Sprint.
-
Question 44 of 176
44. Question
My team’s Sprint Reviews consist of a review of metrics for the Sprint.
-
Question 45 of 176
45. Question
Each sprint contains something from the previous retrospective to help my team improve our outcomes.
-
Question 46 of 176
46. Question
As long as we are getting the job done; management is happy.
-
Question 47 of 176
47. Question
Retrospective plans are dropped in order to get more work done in the Sprint.
-
Question 48 of 176
48. Question
My team’s Sprint Retrospectives provide one or two action plans for improvement.
-
Question 49 of 176
49. Question
The team is always looking for ways to get more done in a Sprint.
-
Question 50 of 176
50. Question
My team’s improvement actions are tied to metrics that easily tell us how we are doing.
-
Question 51 of 176
51. Question
My team has plans to improve; but we have no idea how effective those plans have been.
-
Question 52 of 176
52. Question
The documentation my team creates is absolutely necessary
-
Question 53 of 176
53. Question
My team creates only the documentation that is needed.
-
Question 54 of 176
54. Question
My team creates a lot of documentation that isn’t used by anyone.
-
Question 55 of 176
55. Question
My team usually has more than five PBIs in progress at the same time.
-
Question 56 of 176
56. Question
My product owner understands the market in which our product is sold.
-
Question 57 of 176
57. Question
My product owner has no special knowledge of the customers or market my team serves.
-
Question 58 of 176
58. Question
Our product owner does a good job of managing relationships with the stakeholders.
-
Question 59 of 176
59. Question
Stakeholders are not invited to my team’s Sprint Review events.
-
Question 60 of 176
60. Question
My product owner checks in with me at least once a day.
-
Question 61 of 176
61. Question
I don’t see my product owner during the day.
-
Question 62 of 176
62. Question
My product owner is available to me every day.
-
Question 63 of 176
63. Question
I never have to wait more than a few hours to ask my product owner a question.
-
Question 64 of 176
64. Question
My product owner always discusses functionality in terms of the user and what the user needs to accomplish.
-
Question 65 of 176
65. Question
My team has little useful information about our users.
-
Question 66 of 176
66. Question
My team runs experiments whenever the right solution is not immediately obvious.
-
Question 67 of 176
67. Question
When my team makes a mistake; we correct it and then figure out how to keep it from happening again.
-
Question 68 of 176
68. Question
When my team makes a mistake; we tend to keep it to ourselves and solve it before anyone finds out.
-
Question 69 of 176
69. Question
I feel that management does not tolerate mistakes.
-
Question 70 of 176
70. Question
If a work item cannot be completed because of a mistake by the team; we are expected to do our best and take steps to ensure that the problem can’t reoccur.
-
Question 71 of 176
71. Question
I feel encouraged to speak up when something could be improved.
-
Question 72 of 176
72. Question
Pointing out why a process doesn’t work gets you yelled at by management
-
Question 73 of 176
73. Question
My thoughts on how to improve a process or procedure is eagerly heard by my team.
-
Question 74 of 176
74. Question
I feel encouraged to try new things even if I make little mistakes along the way.
-
Question 75 of 176
75. Question
I have no problems asking questions when I don’t know how to do something.
-
Question 76 of 176
76. Question
I will be made to feel foolish if I suggest something that can’t or shouldn’t be done.
-
Question 77 of 176
77. Question
I don’t enjoy working with my team mates; they tend to be angry and short tempered with me.
-
Question 78 of 176
78. Question
Everyone on my team is willing to help me when I ask.
-
Question 79 of 176
79. Question
Senior members of my team are always willing to help the more inexperienced team members.
-
Question 80 of 176
80. Question
I can speak openly with other employees and they feel comfortable being open with me.
-
Question 81 of 176
81. Question
Management treats my teammates and me fairly.
-
Question 82 of 176
82. Question
Everyone on my team is treated fairly.
-
Question 83 of 176
83. Question
It is often held against you if you make a mistake on this team.
-
Question 84 of 176
84. Question
Members of this team are able to bring up problems and tough issues.
-
Question 85 of 176
85. Question
People on this team sometimes reject others for being different.
-
Question 86 of 176
86. Question
It is safe to take a risk on this team.
-
Question 87 of 176
87. Question
No one on this team would deliberately act in a way that undermines my efforts.
-
Question 88 of 176
88. Question
Management supports my team by providing tools resources and advice.”
-
Question 89 of 176
89. Question
My team avoids debates about solutions; they just turn angry and loud.
-
Question 90 of 176
90. Question
My team calmly; fairly; and professionally debates potential solutions.
-
Question 91 of 176
91. Question
I feel encouraged to try to identify opportunities for innovation
-
Question 92 of 176
92. Question
Innovation is expected to come from management; my team does as we are told.
-
Question 93 of 176
93. Question
Processes exist for a reason; my job is to follow them.
-
Question 94 of 176
94. Question
My team encourages unusual ideas and suggestions to see what can be learned from the discussion.
-
Question 95 of 176
95. Question
I feel valued by my team and supervisor as an important member of the team.
-
Question 96 of 176
96. Question
My ideas are valued by my team and my supervisor.
-
Question 97 of 176
97. Question
Titles don’t mean anything on my team.
-
Question 98 of 176
98. Question
The higher your title the more respectfully you are treated by others.
-
Question 99 of 176
99. Question
Working with members of this team; my unique skills and talents are valued and utilized.
-
Question 100 of 176
100. Question
My team has a DONEness definition.
-
Question 101 of 176
101. Question
My team uses our DONEness definition during Sprint Planning and throughout the Sprint and checks it during Review.
-
Question 102 of 176
102. Question
My team’s DONEness definition is routinely reviewed and updated.
-
Question 103 of 176
103. Question
Product backlog items are either DONE or NOT DONE by the end of the Sprint; we don’t discuss “almost” DONE.
-
Question 104 of 176
104. Question
My team splits unfinished product backlog items into the done and not done portions at the end of the Sprint.
-
Question 105 of 176
105. Question
My team holds Backlog Refinement events during the Sprint.
-
Question 106 of 176
106. Question
When my team slices a backlog item into smaller pieces each piece is clearly demonstrable by the end of the Sprint.
-
Question 107 of 176
107. Question
During Sprint Reviews my team demonstrates only product backlog items that we deem DONE.
-
Question 108 of 176
108. Question
Work is often added during the sprint when the developers are asked to do something we hadn’t planned to do.
-
Question 109 of 176
109. Question
Standards exist for what I do and they are carefully followed.
-
Question 110 of 176
110. Question
Artifacts aren’t checked in until tests (or other inspections) are completed and successful.
-
Question 111 of 176
111. Question
Features are not considered complete unless all of their tests run successfully.
-
Question 112 of 176
112. Question
My team has 10 or fewer developers on the team
-
Question 113 of 176
113. Question
My team has at least 3 members on the development team
-
Question 114 of 176
114. Question
During Sprint Planning my team figures out how we plan to work together to complete the forecasted work.
-
Question 115 of 176
115. Question
My team has a voice in selecting new members.
-
Question 116 of 176
116. Question
My team has a voice in removing team members who aren’t working out.
-
Question 117 of 176
117. Question
My team determines our iteration length.
-
Question 118 of 176
118. Question
My team changes iteration length when necessary.
-
Question 119 of 176
119. Question
My team uses pairing (pair programming; pair testing; etc.)
-
Question 120 of 176
120. Question
My team uses test-driven development (tdd)
-
Question 121 of 176
121. Question
My team does code reviews
-
Question 122 of 176
122. Question
My team writes automated unit tests.
-
Question 123 of 176
123. Question
My team writes automated acceptance tests.
-
Question 124 of 176
124. Question
My team runs tests continuously.
-
Question 125 of 176
125. Question
Management communicates clear organizational goals and how my team is expected to contribute to those goals.
-
Question 126 of 176
126. Question
It is difficult to ask other members of this team for help.
-
Question 127 of 176
127. Question
My team can holds calm debate about solutions when we disagree. We usually find a good compromise solution.
-
Question 128 of 176
128. Question
My team just does a product demonstration during the Sprint Review and then we move on to the Retrospective.
-
Question 129 of 176
129. Question
A core group from my team does the Sprint Planning.
-
Question 130 of 176
130. Question
A core group from my team does the backlog slicing.
-
Question 131 of 176
131. Question
During Sprint Reviews my team demonstrates in an environment (nearly) identical to a customer environment.
-
Question 132 of 176
132. Question
When a defect is found it becomes my team’s number one priority to correct it.
-
Question 133 of 176
133. Question
Defects are addressed and corrected during the Sprint in which they are found.
-
Question 134 of 176
134. Question
My team has times during the week in which no emails; text messages; or meetings are permitted.
-
Question 135 of 176
135. Question
Tasks often take longer than they should because of unexpected interruptions.
-
Question 136 of 176
136. Question
The development team estimates all work items that they are expected to build.
-
Question 137 of 176
137. Question
My team achieves at least 80% code coverage with our automated tests.
-
Question 138 of 176
138. Question
My team does regular refactoring of our code.
-
Question 139 of 176
139. Question
My team uses Sprint Planning for the product owner to tell us what we are going to build this Sprint.
-
Question 140 of 176
140. Question
Our product is rebuilt and retested at least once a day.
-
Question 141 of 176
141. Question
My team builds high value work before bothering with low value work.
-
Question 142 of 176
142. Question
My team does not build low value work until nearly all of the high value work is done.
-
Question 143 of 176
143. Question
Everyone on my team plays one and only one role (Scrum Master; product owner; Development Team Member)
-
Question 144 of 176
144. Question
Requirements are best communicated through documentation.
-
Question 145 of 176
145. Question
My team discusses requirements thoroughly before determining a solution.
-
Question 146 of 176
146. Question
The Development Team considers multiple solutions and then decides upon the best solution under the current circumstances.
-
Question 147 of 176
147. Question
My team does not have the skills that they need to get the job done.
-
Question 148 of 176
148. Question
If the product owner asks for a change to the work item; the Development Team members knows that they can decline if the Sprint goal could be affected.
-
Question 149 of 176
149. Question
My product owner determines the value of new items during refinement and reprioritizes appropriately.
-
Question 150 of 176
150. Question
My team slices large product backlog items into the types of work we have to do (e.g. coding and documentation)
-
Question 151 of 176
151. Question
During Sprint Review incomplete product backlog items go back to the Product Backlog for planning.
-
Question 152 of 176
152. Question
Work comes to my team only through the product owner.
-
Question 153 of 176
153. Question
During Sprint Review incomplete product backlog items are carried over to the next Sprint.
-
Question 154 of 176
154. Question
My team slices large product backlog items during Sprint Planning.
-
Question 155 of 176
155. Question
During Sprint Reviews my team presents our status using a Powerpoint slide deck.
-
Question 156 of 176
156. Question
My product owner’s Product Backlog is prioritized by whomever yelled the loudest most recently.
-
Question 157 of 176
157. Question
My product owner clearly identifies the value of the work that my team plans to do.
-
Question 158 of 176
158. Question
My team takes what the specifications say over what the product owner wants.
-
Question 159 of 176
159. Question
Product Backlog Items are clearly identified in terms of business value.
-
Question 160 of 176
160. Question
During Sprint Review my team and our stakeholders focus on the outcomes we produced.
-
Question 161 of 176
161. Question
My team cannot easily tell the difference between high value and low value work.
-
Question 162 of 176
162. Question
My product owner’s Product Backlog is prioritized by business value.
-
Question 163 of 176
163. Question
My product owner knows why a product backlog item needs to be done.
-
Question 164 of 176
164. Question
My product owner knows the value of their product backlog items.
-
Question 165 of 176
165. Question
During Sprint Review my team and our stakeholders focus on the velocity we achieved.
-
Question 166 of 176
166. Question
The developers work with the product owner every day to check the work done so far and to answer questions.
-
Question 167 of 176
167. Question
During Sprint Planning my team identifies multiple solutions for a backlog item and chooses the best one.
-
Question 168 of 176
168. Question
During Sprint Review my team and our stakeholders review progress and make decisions about what to do next.
-
Question 169 of 176
169. Question
The product owner modifies the content of my team’s Sprint.
-
Question 170 of 176
170. Question
My team uses an artifact management system in which we store code; specifications; etc.
-
Question 171 of 176
171. Question
My team checks artifact changes into the artifact management system several times a day.
-
Question 172 of 176
172. Question
My team changes what we are doing if a better approach is identified.
-
Question 173 of 176
173. Question
My team modifies Sprint content when they believe they can improve outcomes without affecting the Sprint Goal.
-
Question 174 of 176
174. Question
The product owner supports the developers during iteration planning by answering questions about the work item.
-
Question 175 of 176
175. Question
The developers decides which work items fit into the iteration.
-
Question 176 of 176
176. Question
The entire team determines which work items need to be done next.