|
|
|
|
|
by tannhaeuser
2938 days ago
|
|
That sounds ridiculously similar to people hanging on to communism/socialism: "the principles are sound, it just hasn't been implemented as intended". Except, just like communism, Scrum has never and will never be implemented "as intended" because that's contrary to our collective evolutionary gifts, and against a developer's desire to find satisfaction in good craftsmanship. A project management methodology building on utopian altruistic ideals and delusions wrt people's motives is just propaganda. |
|
And there are other organizations who can make any agile method work for them.
So, it's not really Scrum's fault when it fails (at least not always). And it's not really (or not only) Scrum's achievement when it succeeds.
As a friend of mine, Samir Talwar, once said: "To be good at software development, you need an organization that's optimized for software development. Most organizations are optimized for something else."
Anyway, if you implement a process, but ignore even the very short (22 pages) guide that summarizes the process, but instead cherry-pick what you think will work well in your org, then don't blame the process when it does not work.
As I wrote in my book: "But changing Scrum so it works within your company will not make you more agile – It will make Scrum less agile!"