3 ms·
This is a good article, but I disagree that Scrum's major flaw is a lack of hierarchy on the development teams. I've worked on some great self-organizing teams,
by wpietri 8y ago
This is a good article, but I disagree that Scrum's major flaw is a lack of hierarchy on the development teams. I've worked on some great self-organizing teams, and they're more than equal to the product manager. They outnumber the PM, after all.
The problem only comes in an organizational culture of "whatever the boss says". In that context, teams rarely learn to self-organize. Instead, the previously existing control hierarchy stays in place. Before, developers built whatever spec landed on their desk. Now they build whatever is in JIRA. Developers in that world can't even conceive of pushing back.
It's my belief that if Scrum had had some strong counter-balance to that, like an Engineering Master, then it just wouldn't have been adopted. Scrum won out over the other Agile processes (of which there were several) not because it produced better results, but because it was the one most comfortable for medium- and large-company managers. It provided the feeling of transformation without actually changing anything important. They were doing waterfall before, which became untenable with the rise of the Internet. Now they do mini-waterfall, call it Agile, and imagine themselves kings of the world.
- ataturk 8y agoI don't know... I've come to just resent all of it. Scrum, JIRA (god, how I hate tickets), the whole works. It's a giant dumpster fire at this point. It was never good. Every place I have worked that did waterfall was a mess and every place I have worked that has done agile has been a mess one way or another.
- maxxxxx 8y ago"Instead, the previously existing control hierarchy stays in place." That's what happened at my place. Instead of having only product owners, scrum masters and Dev teams we now have project managers, business analysts, line managers plus product owners, scrum master and Dev team. And all of these roles have some level of authority and want their own personalised reporting. So instead of less management we now have more.
- fwip 8y agoAbout a year ago, we went from no-process to "agile?? I guess?" And let me tell you, a badly implemented process is a great way to turn self-driven developers into cogs that just do what's in Jira. Getting your tech decisions questioned by non-tech scrum masters during standup, requirements that don't arrive till midsprint, inability to deploy anything that hasn't been specifically inspected by the sole overworked product owner, etc. It's not intellectual laziness, it's a defense mechanism. You can't be emotionally invested in your work if the process makes things worse for everyone, at least not without a good therapist.
- srtjstjsj 8y ago> questioned by non-tech scrum masters during standup, Standup is for raising issues, not answering questions. Standup rules says to defer discussions to a separate meeting. > requirements that don't arrive till midsprint, Not scrum-specific, and scrum requires either (a) not doing that, or (b) negotiating a trade to remove another requirement. > inability to deploy anything that hasn't been specifically inspected by the sole overworked product owner Not scrum at all. Scrum deploys every month, as clockwork, with whatever is built so far.
- fwip 8y agoYes, these are all examples of process done badly.