Rethinking Agile: Why Agile Teams Have Nothing To Do With Business Agility

by Klaus Leopold

I actually find this extremely funny: “We are going to implement a waterfall project to become agile.” But don’t let me get ahead of the story.

The problem in many companies is they have a lot of work in process that doesn't make any progress. It's at a standstill, so to speak. That's why I started using "Work in Process" consistently because it better describes the reality within the organization.

A project or initiative would only be considered "Finished" if it had achieved what it was supposed to achieve. And in order to determine this, metrics must be employed and feedback from the customers and users of a product must be gathered. It's possible that adjustments are necessary after receiving feedback. That's why this company had three additional columns after development on the strategy board: "Measure & Improve Success", "Adjust & Improve" and "Result (not) Achieved".