Scrum is
Alexey Krivitsky’s blog (by the way, I highly recommend) has a curious note on whether Scrum is a tool or something more .
Lesha believes that Scrum is not a tool. Scrum for Alexey is a combination of values, principles, good development practices, modern leadership approaches and the very framework itself.
So what is Scrum - a tool or something more?
Scrum was originally a very simple and understandable framework. It was formulated by Schwaber in the book Agile Software Development with Scrum and then slightly corrected and supplemented in the book Agile Software Management with Scrum.
')
The simplicity of Scrum has both good and bad sides. On the one hand, the smaller the rules, the easier it is to follow them. The extra rules contribute to the dogmatism of the methodology. Well, like, you have to do it this way, and not otherwise, because it is written in the book. But dogma is what we seem to be fighting with :-)
Ken Schwaber believes that no new rules need to be added to Scrum. He is actively opposed; see his article on the Scrum Alliance website :
He says: "The context, the players, and the situation should be unique, too . "
The main disadvantage is that the described number of Scrum rules is not enough for real project work. The industry comes up with new approaches, practices and rules, mutates roles and so on. This includes new methodologies (for example, kanban), which also bring something to Scrum.
Trainings are conducted by those who work with real teams. They do not teach Scrum as such (because it is very small, the training would take less than an hour), but rather a set of well-established and effective development practices. So, what they teach is also changing in time. The evolution of such a “Scrum” was summarized by Dan Rawsthorne on his blog . True, this is his “personal” evolution, just one of the options, although it seems to be (by feeling) somewhere in the general trend. :-)
It turns out that the methodology that most people call Scrum, strictly speaking, is not a scram.
Since we are talking about tools here, I will give this analogy. You bought a chainsaw and delighted. However, other users believe that the chainsaw sucks and does not work. You listen to the complaints of people with their fingers cut off. Explain what gasoline is and where to get it. You struggle with the popular belief that chainsaws work only for small trees. Solve problems with loggers when switching from an ax to a chainsaw. You have created a training, successfully trained one hundred and five hundred teams to work with chainsaws and wrote the book "The Philosophy of Chainsaws" ..
And here you meet in someone's blog a record that a chainsaw is a tool and your soul does not stand up ... :-)
Askhat Urazbayev
Lesha believes that Scrum is not a tool. Scrum for Alexey is a combination of values, principles, good development practices, modern leadership approaches and the very framework itself.
So what is Scrum - a tool or something more?
Scrum was originally a very simple and understandable framework. It was formulated by Schwaber in the book Agile Software Development with Scrum and then slightly corrected and supplemented in the book Agile Software Management with Scrum.
')
The simplicity of Scrum has both good and bad sides. On the one hand, the smaller the rules, the easier it is to follow them. The extra rules contribute to the dogmatism of the methodology. Well, like, you have to do it this way, and not otherwise, because it is written in the book. But dogma is what we seem to be fighting with :-)
Ken Schwaber believes that no new rules need to be added to Scrum. He is actively opposed; see his article on the Scrum Alliance website :
He says: "The context, the players, and the situation should be unique, too . "
The main disadvantage is that the described number of Scrum rules is not enough for real project work. The industry comes up with new approaches, practices and rules, mutates roles and so on. This includes new methodologies (for example, kanban), which also bring something to Scrum.
Trainings are conducted by those who work with real teams. They do not teach Scrum as such (because it is very small, the training would take less than an hour), but rather a set of well-established and effective development practices. So, what they teach is also changing in time. The evolution of such a “Scrum” was summarized by Dan Rawsthorne on his blog . True, this is his “personal” evolution, just one of the options, although it seems to be (by feeling) somewhere in the general trend. :-)
It turns out that the methodology that most people call Scrum, strictly speaking, is not a scram.
Since we are talking about tools here, I will give this analogy. You bought a chainsaw and delighted. However, other users believe that the chainsaw sucks and does not work. You listen to the complaints of people with their fingers cut off. Explain what gasoline is and where to get it. You struggle with the popular belief that chainsaws work only for small trees. Solve problems with loggers when switching from an ax to a chainsaw. You have created a training, successfully trained one hundred and five hundred teams to work with chainsaws and wrote the book "The Philosophy of Chainsaws" ..
And here you meet in someone's blog a record that a chainsaw is a tool and your soul does not stand up ... :-)
Askhat Urazbayev
Source: https://habr.com/ru/post/82701/
All Articles