2 ms·
My experience has been that specifying in great detail HOW to do things (as SCRUM does for s/w development) doesn't work as well as specifying WHAT to do and le
by gruseom 18y ago
My experience has been that specifying in great detail HOW to do things (as SCRUM does for s/w development) doesn't work as well as specifying WHAT to do and letting people figure out how to do it, but holding them accountable for results.
This description of Scrum is so wrong that it couldn't get wronger. Scrum says: the product owner says what they want, the team decides how much they can deliver in a month, then they go off and do it however the hell they choose. After a month they come back and demonstrate what they got done, in the form of working software and only working software. The stakeholders then get to decide whether they like the progress that's been made and whether or not to continue for another month. Nobody gets to interrupt the team while they're working and nobody gets to tell the team how to do their work. That's the heart of Scrum. You can see it's much closer to the opposite of how you described it.
But then I noticed that you were merely responding to this, which is obviously where the wrong idea came from:
The development team is run by a project manager. His role is to move the top priority user stories from product backlog to the sprint backlog and break them in atomic tasks that are distributed to your developers
This is risible. If that's what they're calling Scrum, I fully share your skepticism. It's the essence of the failed approach that Scrum was a reaction against.