[switchbak]

If you really find the agile processes you're using are adding tedium, why don't you do the agile thing and tailor them to your specific context?

But I imagine we're probably using the same word to describe very different things.

[spaetzleesser]

The current implementation of Agile in most cases is pretty much the opposite of agile as described in the agile manifesto.

In my team we have reduced the process to having a simple backlog which we work through. But I have seen other teams where you spend enormous amounts of time on planning but it’s frowned upon if you think any further than the next sprint. Just check off tasks without any thoughts about long term architecture or strategy. Basically just a sweatshop with replaceable “resources” (the company doesn’t hire “people” anymore but “resources”)

[switchbak]

There is no current implementation of Agile though, Agile was an umbrella term for a variety of different practices. I don't think you can blame it if it's been poorly implemented.

Granted, that is most of what I see: poorly implemented agile everywhere, usually half embracing SCRUM. I think that has more to do with the typical command and control nature of upper management though.