Recently many orgs inside our BigCo have been through couple years of the best Agile/Lean/Scrum/<whatever crap> the money can buy. It was a zombie-like horror show and a spectacular failure across the orgs. And one wonderful day the management and PMs just seem to have waken up and just magically forgot all these words. We're back to normal planning and developing features like nothing happened in those 2 years. Magic.
As someone said "you can't successfully run marathon by running a series of sprints". One can try him/herself to run even a couple of miles by running it as a series of sprints to understand the foundational principle from systems analysis about the cost of low latency and synchronicity (normally one would expect that software engineers are aware about it without self-mutilating experiments, yet here we're ... to really feel the pain make somebody tell you, strictly each 20 seconds, where to run the next sprint) - those being the 2 main paramount features of Scrum ( note : Agile,insisting on low latency while relaxing somewhat the requirement of synchronicity, is a little bit less disastrous on its own, ie. when isn't attached to Scrum).
On the teams that I ran, we relied on a weekly meeting, lasting about 30-45 minutes to go over what we did last week and what the plans are for this week. The rest is handled perfectly well with ad-hoc communication. Those teams were far more "agile" than any of the Agile teams I've seen, since people expended all their effort on achieving the goals as opposed to figuring out what they're going to say in the next standup.
Plans are made with broad brush strokes and are expected to be fluid and details are figured out during development. Planning sets goals, and are used to time box the work (even if the boxes are different sizes, so no adherence to stupid 2-week one size fits all sprints). Pre-planning makes it easy to get stakeholder buy-in without having to go into deep philosophical development notions. Ad-hoc communications and gasp my involvement with the teams covers 90% of the rest and if major problems occur, the appropriate parties are pulled into a meeting to discuss and resolve.
My teams are pretty consistently the most productive performers in my organization, use the fewest people and resources, and produce the highest quality product at the end of the day. As a result, my teams are consistently in demand to work on things, and once they're out of my hands and back into some scrummaster's their performance goes back to normal.
I've noticed an inverse correlation on all of these metrics the more "Agile/Scrum" the teams seem to be. Between standups, retrospectives, scrums, and whatever activities the other groups get mired down in, the consistent complaint is that nobody seems to have time to actually get anything done.
The problem is that Agile is supposed to be about liberating teams from process and tools and documentation and so on and focus on people and product. However, the Industry that's exploded around "Agile" has simply created another pile of rigid processes that bring everybody back to square one again. Even worse, most people in the industry are so young they think this is better than what the old fuddy-duddies greybeards used to do and don't have the perspective to realize they've just become trapped in another set of process ceremonies that get applied to everything without regard to the nature of the task at hand.
I just got out of sitting in another team's sprint planning meeting and they spent 2 hours trying to figure out how to fit O&M and R&D into their next sprints...30 minutes of which was spent figuring out how to model the Epics.
Agile is a great idea in theory. Agile in practice is a terrible one.
I think that's a lazy argument.
If you don't like the word 'sprint' use another term to denote a period of time.
> natural cycle of plan, design, implement of the stuff slated into the next release (ie. the dirty word of "waterfall").
Actually, if it's in small units of time/work, then it's pretty close to agile.
The problem with waterfall is the big upfront planning where you try to estimate how long it'll take to implement things months ahead of time.
E.g I can run a mile in x minuets flat out but to last for 26 I need to target x+y minutes per mile.
I've done 5 and I've never had a plan hold after the 20th mile.
1. Agile: when stuff works ,it's agile. When stuff fails, its not agike.
2. Not-Agike: when stuff works, its not agile. When stuff fails, it's agile.
The agile debates are just shows of tribal colors, not substantive analyses.
This certainly mirrors some of the horror stories of "agile" adoption I've read online. With most of those, either an executive read a book and forced change on everybody, an over-priced consultant tried to force change on everybody, or some combination of the two.
Counter those exmaples with my own experience in an organization adopting scrum. My current employer started that process 3 years ago and it has been reasonably positive. There were growing pains, but the company invested in training to alleviate FUD, there way buy-in across the board, etc.
Based on this one article, it really sounds like the executive team failed to get buy-in from the broader management team and then doubled-down on the failure by not providing the employees with enough training to overcome FUD-induced panic.
The executive reads the book and then hires the overpriced consultant(s).
Would it be incorrect in saying that agile has an implicit position of "if you don't trust this developer, fire them"? Which I think is much more of an option in a startup than some politicized offices.
I do think it's incorrect to state "if you don't trust this developer, fire them." At least, it's no more true in an agile environment than any other.
And related to that, do you encounter the "no one on the agile team is empowered to remove this blocker" (because it's too many departments away and that team has no stakeholder/ownership close enough to the agile team)? If so, how does that play?
2. No, we don't usually encounter that.
That said, when we do run into long-running problems, we do need to escalate. One of our systems had some serious performance problems and it did take VP involvement (daily 15 minute standup with the players involved) to keep things moving towards a resolution. It's annoying when it happens, but I'm not sure it's completely avoidable in a large org. Perhaps I've been lucky, but management has always had my back - we def have a culture of servant-leadership, at least in my division.