During a leadership peer-to-peer session, we recently discussed the planning and execution of software projects and how the term “Agile” has become a running joke within some technology teams. This is largely due to its misuse in larger corporations as they attempt to shoehorn existing processes and culture into a state suitable for modern business rather than by taking a holistic approach that starts by fostering the correct culture. Throwing the word “Agile” off the cuff is now the equivalent of walking into a guitar store and playing Stairway to Heaven.
Our conversation explored why this tends to happen, the unique nature of software development, and how taking an agile approach depends on the nature of the project or business. We all agreed that the prerequisite for an Agile approach is “unknown” or “changing requirements”, - but if those requirements are static, Agile might not be what you need.
One analogy we discussed was that of building a bridge across a river. For instance, a …
Keep reading with a 7-day free trial
Subscribe to Paul Clegg to keep reading this post and get 7 days of free access to the full post archives.