So it's lunch, and let's talk Agile and how it doesn't work in a vacuum.
1/
Now Agile is a great approach to productivity as it focuses on adaptability, communication, etc. Which is great.
Except it is of limited effect if the environment it's in doesn't have those things.
2/
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/
@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.
@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."