Skip to main content

Change in an Agile Environment


Project Management and change go hand in hand from the planning phase onwards. Shifts in schedules leaving businesses unable to accommodate the changes, and constant uncertainty leaving change practitioners powerless to develop plans and keep stakeholders engaged. With organisational change management seemingly pushed to the margins. As project managers we cannot work in isolation, there must be an understanding on how projects affect change, so working with change managers is almost mandatory, and hence necessary to understand. Hence, Agile Change Management is a set of principles, not a one size fits all approach. The following are some lessons learnt and observations made that will help prepare to better manage change in an agile environment:
•    Change Impacts are still essential; it’s vital for informing people of the landscape, risks, dangers and opportunities. However, don’t be wedded to it. As soon as you start delivering you are going to need to iterate this. There is a gap between the strategy and what the people can do. Known as the ‘execution gap’. To stay relevant your ‘gap analysis’ will need to be done multiple times to ensure you’re all still on track.

•    Trust is key; Trust and transparency go hand in hand. Open doors to stakeholders and instead of concentrating on, training, coms or stakeholder plans, engage them. Give them regular feedback and updates, giving them visibility of the process. Being transparent will ensure that communication lines are kept open which will ensure that mistakes, progress and failures are all identified and shared.
 
•    ‘Think like a Military Commander’; you are a pair of eyes focused on identifying potential risks, threats and danger. You must communicate these to your troops to let them know what could happen, guiding them onto contingent courses. It’s not ‘reworking’ it’s readjusting to where we are now. As a leader you are constantly asking ‘Is this relevant anymore?’ ensuring not to move too quickly because then there is room for error. In this agile landscape this journey isn’t yours it’s everyone’s.

•    Fail fast; ever heard of the age-old phrase; ‘Try to fail, don’t fail to try?’ Well, this is highly applicable in an agile landscape. It’s ok to fail if you are doing something about it. You need to be constantly reassessing and asking ‘what am I doing wrong?’ and ‘what is no longer relevant?’ If you identify risks then confront them early so that you might ‘fail fast’ you will alter the change roadmap and lead to a smoother engagement, adoption and embedment.

Whether you are currently delivering change on an Agile project, or in a more conventional Waterfall delivery, embracing these 4 Agile change principles can assist you to becoming more customer focused, adaptable, effective and integrated. 

Comments

Post a Comment

Popular posts from this blog

Revisiting Managing Stakeholders, how to Nurture and thrive the relationship.

  Stakeholders can make or break projects, in order to ensure project success, effective stakeholder management is required. Identifying key stakeholders, dealing with difficult ones and creating a management plan can be overwhelming if you don't know where to start. Building positive relationships with stakeholders and proactively meeting their expectations can make the life of a project manager much, much easier.
Post a Comment
Read more

How to Resource Plan

When managing a project or a project portfolio, it’s critical that resources and workload for each are intelligently distributed. Without proper resource allocation, projects can quickly get out of control in terms of expense and duration. With the right resource planning techniques, effective planning and management of resources in any industry can set you up for success. But before the break down on how Projectmanagementcompanion.com provides the perfect tools for resource planning and management, there must be a firm understanding on what resource planning is and how to compose a resource plan. Resource planning is one of the steps required when writing a business plan where all the resources in a proposed project are identified. This is achieved by creating a summary for managing workload that is comprehensive enough to make sure all the resources that are needed to complete the project are clearly identified. This summary is going to help get a buy-in from the sponsor an...
Post a Comment
Read more

The difference between a Project Manager and a Scrum Master

By the nature of the work that Project Managers and Scrum Masters do, the two are not particularly closely aligned, even if it seems at first glance that they are. Managing a project is not the same as being a Scrum Master. Scrum Masters have the role of mentoring, teaching, coaching and facilitating, while the role of the Project Manager is to ensure that the project runs to time and budget. This means that the Scrum Master relies on more of the so-called “soft skills” involved with helping people to move forward, while the Project Manager takes a more methodical, and arguably more of a “hard skills” approach. While both roles have an interest in ensuring a high level of team performance and driving efficiency within the team, the ways in which they go about this are very different. The Scrum Master facilitates and coaches, while the Project Manager assesses risk and manages issues and conflicts.  Looking closer at what Project Managers and Scrum Masters do in terms of ...
Post a Comment
Read more