Live data from Hacker News

How do I prevent Scrum from turning great developers into average developers?

workplace.stackexchange.com

21–22 of 22 posts

Re: How do I prevent Scrum from turning great developers into average developers?

#21

Is it just me, or is it the case that in discussions about Scrum, most of the responses are “then you’re not doing it right”, “no true Scotsman”-style?

I once heard that described as "the non-falsifiablility of religion surfacing".

You might have noticed that the answer is never "maybe your situation calls for trying these small tweaks to the vanilla scrum process..." even though Scrum claims to be about retrospectives and continuous process improvement.

Re: How do I prevent Scrum from turning great developers into average developers?

#22

Poor scrum. It gets so maligned. If you have a high functioning, well gelled team with well developed communication habits and rituals, you don't need scrum. But, guess what, those are few and far between, and scrum is an excellent starting point. Whenever I see a complaint it's usually because someone involved has violated some part of scrum. It's run by the developers. They set what they're planning to work on. No…

Where I work, we can choose what we work on, as long as it's one of the backlog tickets the product owner wants done for the next release. The way they are formulated means there is very little room for solving hard problems (of the type that could result in fifty tickets not being necessary anymore), let alone making prototypes for things if they aren't guaranteed to releasable results for any of the tickets.

So your product owner doesn't understand their role in scrum. It's a fairly common pathology.
Post reply on HN