Definition of "impediment" #21
Closed
DominikMaximini
started this conversation in
Ideas
Replies: 4 comments 1 reply
|
Thank you for bringing this up, @DominikMaximini |
1 reply
|
"Is anything" is a bad idea imo. Do you track people as impediment? Mindset? Culture? An impediment is "dependency, process, budget constraint, or tool/code" to me at least. Maybe I miss some, but "anything" it's not. |
0 replies
|
Hi folks, thank you. We will consider the ideas and critiques from here for the September 2025 update. Many thanks. |
0 replies
|
Is addressed in the next release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The chapter "People and Change" defines the term "impediment" as follows: "An impediment in Scrum
is anything that blocks or slows down progress"
I learned a slightly different definition. The definition above defines the word "problem". If the problem can be solved by the Developers & Product Owner alone, then it just is a problem and subject to self-management. If it canNOT be solved by the Developers & PO, it becomes an impediment and the responsibility of the Scrum Master. These impediments can range from team-building, to missing test servers, or organizational processes.
Therefore, I recommend changing the sentence above as follows: "An impediment in Scrum
is anything that blocks or slows down progress and cannot be solved by the Developers & Product Owner alone."
All reactions