Yesterday’s Agile

Been thinking about what’s next for agile development…

TDD is still young, but not as young as it was.  BDD is creating greater artifact, process, and team unification opportunities for test-first programming in an agile process.  Some of tomorrow’s practices are already starting to appear, but there’s a possibility, as is usual with all things human, that today’s agile activists can either be tomorrow’s agile activists or tomorrow’s agile friction.

Agile development has only had one generation of progress.  If the second generation is just around the corner, then today’s agilists’ identification with the practices that they are known for may be the very weight that slows the transition.

The transition to the second generation of paradigms of any old thing in any old lifetime is a difficult transition.  The transition to a second generation paradigm is the event that brings people face to face with the impermanence of the ways and means that they may have likely become identified with in the first and only generation.  Getting to tomorrow’s agile will be as much or more of a process of letting go as it will be a process of acquiring additional – sometimes historically contradictory – knowledge and practices.

So, will today’s TDD celebrities in the .NET world be able to let go of the practice that has become a big part of their identities and move forward with an eye toward progressiveness as they did in 2001 when NUnit started many journeys into unit testing, TDD, and greater agile?

What will tomorrow’s agile practices be?  Will we have the energy to move forward with verve and vigor as we did back in the day?

This entry was posted in Agile, Commentary. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

Leave a Reply