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 the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…