Almost two decades ago a group of software engineers met in Utah to figure out a way to speed up and simplify development methods based on their own experiences. They outlined four values that state:
- individuals and interactions are more important than tools or process,
- achieve a working solution rather than drown in documentation,
- be collaborative with your customers rather than limited by contracts, and
- put the focus on responding to change rather than massive, complex plans that are impossible to implement without pain
I am paraphrasing here, but you get the idea. These values are human-centred, they are about how people function. Who wants to drown in documentation? Not a single business leader or a single IT developer that I have ever met.
At the time I was really encouraged and excited. These same folks created the Agile Manifesto, which expands on the four values. A dozen principles that I firmly believe will help you know what to do to make your change work regardless of your preferred methodology.
12 principles of Agile
Here is how I captured the 12 principles of Agile in my notebook years ago:
1. Deliver value early
Satisfy the people through early and continuous delivery of value.
2. Harness change
For the organization’s competitive advantage.
3. Shorter timescales
Emphasize a preference for a shorter timescale.
4. Work together
Business people and solution developers must work together.
5. Build projects around motivated individuals
Individuals who have the support they need, and trust them to get the job done.
6. Convey information to and within all teams
Do this in (virtual) face-to-face conversation.
7. Working solution
Whether the solution is software or other - this is the primary measure of progress.
8. Promote sustainable development
The sponsors, the project people and all the people are able to maintain a constant pace with no risk of burn out.
9. Technical excellence and good design
Keep attention on technical excellence and good design to enhance agility
10. Simplicity
The art of maximizing the amount of work not done — is essential.
11. Self-organizing teams
The best requirements and designs emerge from self-organizing teams
12. Reflect regularly
Reflect on how to become more effective, adjust behavior accordingly starting in project teams.
Here we are twenty years on and delivering real breakthrough results from a portfolio of projects is still cause for clenching teeth and crossing fingers. Or am I wrong? Change management is now mainstream in many organizations and yet it feels as though change management and agile are not integrated in a way that lets new value emerge.
Just considering these 12 points it is clear that the role of change management becomes more involved when working with agile projects. Change management cannot be a resource the project team calls on; change management is core and must be involved at every step from the very earliest step.
How does Agile work in practice for Change Management
“...change management should be experienced as both a salve (not as much pain as previous experiences) and an accelerant.”
The change management team will gather the legacy change data, the stakeholder mapping and the impacts, and people risks; however they need to be agile too. The analysis and diagnostic efforts should be complete enough to provide useful insights that will help from the very first sprint planning. As the insights grow, so they will create more value for the project team. Working across functions the data can be shared to ensure that where the rubber hits the road leaders can guide people to improved self-awareness, self-management, social awareness at the same time as clearing the way and setting the stage operationally for a successful implementation and adoption.
Change management should not be a drag on adoption because there is a need to wait to complete some change management activities. Instead, change management should be experienced as both a salve (not as much pain as previous experiences) and an accelerant. Many will tell you it can’t be done. I say, let’s give it a try using the 12 principles of the agile manifesto to guide our choices and decisions.