Recently I attended the Agile 2010 show and was lucky enough to sit through the Tom Grant, PhD talk. Dr. Grant presented a myriad of statistics and used an analogy from French History about adoption patterns moving from Radical/Fanatical to Pragmatic.
One example of this is in the US DoD or Federal space. With the new legislation brewing around Section 804 [note to readers: I will write an article that will do a deep dive on this later] the US Government has dictated from a Policy perspective that ‘users’ are now part of team. In hearing this, most all of the Agile players are cheering (and hoping other governments follow suit), but those who’ve been doing this for a while understand that Agency culture may trump policy.
In other words, although US Government legislation is moving to include business users on software development projects, agencies and systems integrators will still have the flexibility to maneuver around these laws using cultural norms as the justification. This isn’t to say that those of us who’ve been working with governments to implement Scrum and Agile as a means to a better end (user experience) shouldn’t be jumping for joy.
Let’s not make any bones about it, this is a big deal. But in all the celebration let’s not forget that localized cultural change still needs to be part of the transformation even though the policy change has already occurred.
CollabNet will be hosting and sponsoring a conference in Washington DC later this year dedicated to helping Government officials better understand how all development efforts – from contract writing to delivery to hosting and maintaining applications will be changing with these new regulations.
So I will leave you with this to think about, does it matter if Policy change or localized cultural changes happen first? Is there a necessary order to these organizational communication patterns? Do we need both?