Agile methods CAN work better than non-Agile methods in a non-Agile environment. In fact, it often makes problems VERY visibile. But this makes Agile a struggle.

3/

This is why, over my . . . oh, gods, 13+ years of using Agile when I hear "Agile failed" I hear "my overall environment sucks."

Agile is all about PRODUCTIVE approaches. If you have a hard time applying them, it says something about the big picture.

4/

So like it or not if you do Agile in a non-Agile environment you WILL inevitably have to protect yourself from, build an interface to, or change the non-Agile parts.

It will happen ANYWAY.

5/

This makes me think I should rally a few of my fellow Agilists to do a book on this. Because we COMPLAIN enough about it.

6/6

@StevenSavage As I have tried to explain multiple times, Agile doesnt solve your problems, It exposes your problems like a raw nerve. Its up to you and your team to then experiment to fix them. Anything other than that then you are doing it wrong.

@StevenSavage My department at work is Agile but the company as a whole is not. Leadership spends a lot of effort communicating to folks outside our org about how we work, and shielding us engineers from the chaos outside our gates. But.. we deliver consistently and have built trust with our stakeholders and as they gradually buy into the process our way of working tends to catch on in other places.

@ScionAltera oh we should talk. I'd love to hear more! Want to connect on LinkedIn?https://linktr.ee/thestevensavage

@StevenSavage I'd love to chat about Agile. I've got a few stories. I'm on LinkedIn but I don't use it much.

@ScionAltera My linktree has my profile, connect up! We'll chat.

@StevenSavage I'd also add something I used to say to my team all the time, but not so much anymore: "The process serves the team, not the other way around. If it's not working, we can change it."