Skip to main content

Agile Change Management

I always hear people say ‘Don’t like the weather, wait an hour it will change’.  The one constant in our lives is change. In business today, customers, users and stakeholders all have the expectation that as IT service providers we can and should be able to handle change requests at an ever-increasing pace.  Yet they still have the expectation that an appropriate response to all requests for change entails a considered approach to assessment of risk and business continuity, change impact, resource requirements, change authorization and especially to the realizable business benefit. For us to be able to do change management in an Agile environment, does that mean we must give up those requirements for speed and agility?

The purpose of Change Management is to control the life cycle of all changes enabling beneficial changes to be made.  I was once told by a very wise thought leader ‘Being agile is a state of mind.  It’s more perspective than prescription.’  Why can’t we have a change management process that includes in its perspective being customer-centric, lean, adaptive, measurable and results-oriented, all agile qualities?  

If you think about it, the goal of being agile is to enable your change management process.  The idea isn’t to control changes to customer requirements, but to allow them to be recorded in a way that increases flow. This allows the customer to be engaged throughout, thereby shortening and amplifying the feedback loop and by creating policy around repeatable changes where we employ the understanding that repetition and practice is the prerequisite to mastery.

The reliance on IT services and underlying information technology is now so complex that considerable time can be spent on assessing the impact of business change on IT and analyzing the impact of a service or IT change on the business.  By engaging scrum and its iterative and incremental approach we can reduce the need for large complex changes which in turn reduces risk, costs and time constraints.  By employing lean practices, we can eliminate the need for overly cumbersome and time-consuming activities. Remember simplicity – the art of maximizing the amount of work not done.

Change management challenges are not eliminated by the introduction of Agile methods. There may be any number of reasons why we engage Agile methods, either because of external market space forces or the introduction internally of a DevOps philosophy. Agile provides a disciplined, streamlined way to manage the unending array of changes that are needed to remain competitive and relevant. Agile iterations provide working systems earlier, enabling owners and users to recognize and address needed changes earlier. Change management in Agile environments engage a shift left mentality.  Changes don’t just come at the end of the development cycle.  Agile methods give you a way of acknowledging that change management is certain and that both development and operational teams need to facilitate its incorporation early in project / service / process lifecycles.

To see Certification Training and Workshops: www.itsmacademy.com/agile

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi