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.
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.