The Agile method of IT project management has become increasingly popular over recent years, and rightfully so – it is a fantastic way of developing a new or improved technology. It’s incremental and iterative approach allows for quality deliverables at project completion.
This methodology, however, has caused many a headache for Change Management practitioners, who want to know what is coming when so that users may be prepared through communication, training, and other adoption techniques. The challenge for Change practitioners is that frequently (usually), our IT counterparts in on an Agile project are can’t commit to end product details, features, timelines, or seemingly anything else.
However, just as technology methodologies evolve, so do Change methodologies. As Change practitioners, we have learned to work in a world that is uncomfortable for us (yes, we eat our own dog food sometimes!). It does mean that we must do some things differently than we have with the past.
When it comes to communications, we can’t communicate what hasn’t been decided, but we can communicate what we do know. On training, we usually can’t develop detailed training artifacts with screenshots or other static content due to the dynamic nature of the technology in production, but we can build interactive training activities that will prepare users just as well. It’s just a different approach that when planned and executed appropriately can be very successful. In fact, some would argue that Change Management on an Agile project can actually be more effective than on a more traditional waterfall project.
There is a catch though – Change practitioners must be involved early, even at the outset, of an Agile project. While arguably this is no different than a waterfall project, it’s critical for an Agile project. Due to the iterative, constantly changing, definitional nature of Agile projects, Change practitioners can’t wait to start creating deliverables when everything is “figured out.” Change deliverables become more iterative than ever, and thus, Change practitioners must become an integral member of the project team.
Yes, Change Management can be done, should be done, and done well, for Agile projects. Engaging the right resources at the right time will go far in enabling a prepared user force will lead to what is sure to be a great overall implementation.
