4 Tips to Increase Velocity in Your ITIL-Based Change Process
September 10, 2012
Russ Miller
Share this

For those of us who handle IT change requests on a daily basis, the process can seem as onerous as a Sisyphean task. In this case, rather than a boulder rolling back down the hill, it is the backlog of RFCs that seem to grow every time you complete a request. Let’s face it - the requests are not going to stop coming. The business is trying to change faster, so they need IT to implement change faster. In the end, it is all about doing as much as you can with what you have. Following ITIL best practices and using a solid change management tool goes a long way, but how can the whole task be made less Sisyphean?

The answer may come from borrowing some of the lessons learned from application development. It turns out that many of the same agile practices adopted by programmers over the last decade can greatly improve the continuity, speed and predictability of your organization's IT Change Management – leveraging, not replacing, your existing ITIL best practices and tools.

When you view the never-ending flow of RFCs as roughly equivalent to the flow of feature requests that an application development team receives, and recognize that the goals are the same - to implement the changes as quickly as possible, as close to the user’s expectations as possible, and in a predictable amount of time - then it becomes clear there is much overlap between processing change requests and turning around new features in a software application.

Of course, some of those change requests are for application development, and those clearly lend themselves to agile practices. But as it turns out, agile methodology can help IT manage all types of requests.

It is possible to apply agile practices to the flow of IT change requests and see these same benefits. Here are some specific ideas on how to implement agile methodology without abandoning ITIL best practices or your current change management tool:

1. Use CAB Meetings to Prioritize Backlog

Take an agile methodology mindset to CAB. Instead of holding weekly or monthly CABs, have daily scrums to prioritize change requests. Place the less urgent and non-routine requests on a backlog. Let the responsible teams decide how much of the backlog they can achieve in a short period of time, say two weeks.

In your Change Management tool, create views that clearly indicate which requests are on the backlog, and which are in process.

2. User Stories with Story Points help Document RFCs

Scrutinize the change requests to ensure they are properly broken down, the same way agile software developers break down feature requests into User Stories with Story Points assigned and weighted.

Leveraging the customizability of your change management tool, re-label the Description field as User Story and add a field to contain the Story Points. For most IT organizations, the change requests are relatively short lived and independent of each other. But if your organization has enough large, complex requests that are related to a given system or project, following the agile technique of grouping them into a sprint may make sense. You may even consider forming two teams, one team that manages the shorter lived requests as a constant stream, perhaps using a Kanban approach; while the larger requests flow into a team using a scrum approach.

3. Change Manager becomes Scrum Master

The Change Manager acts as the Scrum Manager, overseeing quick daily standup meetings to talk about progress on the tickets in process. The Scrum Master’s mantra: plan a little, do a little, test a little - create a tight feedback loop.

In a larger organization, where the Change Manager cannot possibly have the bandwidth to be the Scrum Master for all of the supported services, the technical owner of a business service may need to act as the Scrum Master, with the Change Manager overseeing the various business Scrum Masters.

It is important that someone fills the role as Scrum Master in order to insure that the amount of work in process is always minimal (agile methodology is all about finishing what you start and delivering each item before you bite off another). As such, it is critical for the Scrum Master to monitor the batch of changes in progress on a day-to-day basis and be available to help clear roadblocks for those implementing the changes.

4. Continuous Improvement to Optimize Agility

By assigning a size in the form of Story Points and by minimizing the amount of work in progress at a given time, you can judge the velocity of successful changes and provide more transparency into what the bottlenecks are.

As requests are completed, the Story Points assigned to the requests represent a quantity of work completed. The average rate of delivering Story Points over time is the velocity. By charting changes in velocity over time, you can better manage your team’s bandwidth and better predict the time required to work down the backlog of requests.

Increasing the velocity becomes the challenge. Agile prescribes various approaches to eliminate the bottlenecks preventing a faster velocity. The best approach for a handling a continuous stream of requests, where they are not batched into sprints, is likely a cumulative flow diagram. However, if you are batching your requests into sprints, then a scrum approach using a burn down chart may work better.

Either of these approaches can be diagrammed in Excel by exporting the data you collect in your change management tool.

In summary, the best way to attack that seemingly always growing backlog of RFCs requires an ability to expose the bottlenecks that are impacting your ability to increase the speed and predictability by which the requests can be implemented. One way, is to borrow agile software development techniques and overlay them on your existing ITIL processes and tools.

ABOUT Russ Miller

Russ Miller is the CTO of SunView Software, Inc., an ITSM tools vendor he co-founded. He has more than 20 years of experience leading software product development from concept to delivery for companies like IBM, Compuware, Quark, and Intuit. He was an early advocate and adopter of agile software practices and has been immersed in ITIL over the last decade as part of developing the ChangGear ITSM solution.

Related Links:


Share this

The Latest

December 11, 2019

As the New Year approaches, it is time for APMdigest's 10th annual list of Application Performance Management (APM) predictions. Industry experts offer thoughtful, insightful, and often controversial predictions on how APM and related technologies will evolve and impact business in 2020 ...

December 10, 2019

Enterprises with services operating in the cloud are overspending by millions due to inefficiencies with their apps and runtime environments, according to a poll conducted by Lead to Market, and commissioned by Opsani. 69 Percent of respondents report regularly overspending on their cloud budget by 25 percent or more, leading to a loss of millions on unnecessary cloud spend ...

December 09, 2019

For IT professionals responsible for upgrading users to Windows 10, it's crunch time. End of regular support for Windows 7 is nearly here (January 14, 2020) but as many as 59% say that only a portion of their users have been migrated to Windows 10 ...

December 05, 2019

Application performance monitoring (APM) has become one of the key strategies adopted by IT teams and application owners in today’s era of digital business services. Application downtime has always been considered adverse to business productivity. But in today’s digital economy, what is becoming equally dreadful is application slowdown. When an application is slow, the end user’s experience accessing the application is negatively affected leaving a dent on the business in terms of commercial loss and brand damage ...

December 04, 2019

Useful digital transformation means altering or designing new business processes, and implementing them via the people and technology changes needed to support these new business processes ...

December 03, 2019
The word "digital" is today thrown around in word and phrase like rice at a wedding and never do two utterances thereof have the same meaning. Common phrases like "digital skills" and "digital transformation" are explained in 101 different ways. The outcome of this is a predictable cycle of confusion, especially at business management level where often the answer to business issues is "more technology" ...
December 02, 2019

xMatters recently released the results of its Incident Management in the Age of Customer-Centricity research study to better understand the range of various incident management practices and how the increased focus on customer experience has caused roles across an organization to evolve. Findings highlight the ongoing challenges organizations face as they continue to introduce and rapidly evolve digital services ...

November 26, 2019

The new App Attention Index Report from AppDynamics finds that consumers are using an average 32 digital services every day — more than four times as many as they realize. What's more, their use of digital services has evolved from a conscious decision to carry around a device and use it for a specific task, to an unconscious and automated behavior — a digital reflex. So what does all this mean for the IT teams driving application performance on the backend? Bottom line: delivering seamless and world-class digital experiences is critical if businesses want to stay relevant and ensure long-term customer loyalty. Here are some key considerations for IT leaders and developers to consider ...

November 25, 2019

Through the adoption of agile technologies, financial firms can begin to use software to both operate more effectively and be faster to market with improvements for customer experiences. Making sure there is the necessary software in place to give customers frictionless everyday activities, like remote deposits, business overdraft services and wealth management, is key for a positive customer experience ...

November 21, 2019

For the past two years, Couchbase has been digging into enterprises' digital strategies. Can they deliver the experiences and services their end-users need? What pressure are they under to innovate and succeed? And what is driving investments in new technologies? ...