The idea of the scrum framework is to organize a development process to move through the different project cycles faster. But does it always incentivize the right behaviours doing so? Many of the users who joined the debate around the question on Stack Overflow have similar stories of how developers take shortcuts, get distracted by their ticket high score, or even feign productivity for managers. How can one avoid these pitfalls?
That the question has been migrated from our workplace exchange to the software engineering one shows that developers consider concerns about scrum and its effectiveness larger than the standard software development lifecycle; they feel its effect on their workplace as a whole. User Qiulang makes a bold claim in their question: Scrum is turning good developers into average ones.
Could that be true?
Via Comment at Hacker News [1], “Does scrum ruin great engineers or are you doing it wrong? - Stack Overflow Blog [2]”
Despite Betterid ge's Law of headlines [3] I'm inclined to answer “yes.” Especially since it appears to me to involve processes and tools over individuals and interactions [4] …
[1] https://news.ycombinator.com/item?id=27461280
[2] https://stackoverflow.blog/2020/06/29/does-scrum-ruin-great-engineers-
[3] https://en.wikipedia.org/wiki/Betteridge's_law_of_headlines