4 ms·
I started working with agile since day one and it was fun back then. Why? Because it made projects so much more interesting. We were learning how to do things d
by bsvalley 8y ago
I started working with agile since day one and it was fun back then. Why? Because it made projects so much more interesting. We were learning how to do things differently and it was pretty cool. Unfortunately, it became more popular and upper management started looking at the benefits of Agile. “Tell me one reason why we should adopt agile in our company?”. Unfortunately, a good answer to that was the ability to track the progress and a large increase in delivery and productivity. Teams hate those words but management love them.
That’s what agile became today, tracking progress with constant status updates, charts and metrics that tell a team “clearly you did a really bad job this time” or “you’re late”. Management doesn’t even have to do the dirty job anymore. Meaningless meetings, less power for engineers, no creativity (ain’t got time for that!), etc.
It went from a cool way to do things to a perfect tool for factories. No offense to factory workers.
- JoeAltmaier 8y agoAnd the illusion of getting things done, because tickets! makes it seem like progress is happening even if churn is all that's happening. Last contract (I left) was 6 years into churning the same awful pile of spaghetti. I came on board to help break the logjam. Micromanaging Agile manager put me on fire fighting, just like all his other reports, just like the last 6 years of churning had done. Left after 6 months and it was obvious they were going nowhere.
- pjc50 8y agoExactly. Doing Agile properly requires a bi-directional mutually respectful communication between the development team and the product stakeholders. It's the complete opposite of traditional suspicion-based hierarchical management. That's why it has so much difficulty getting adopted.