Print Page | Contact Us | Report Abuse | Sign In | Join
The ITSM View
Blog Home All Blogs
This blog, written by itSMF UK leaders and guest contributors, offers service management thought leadership and discussion of industry trends. Please feel free to comment on these posts (you will need to be logged into the website as a member). We look forward to hearing from you.

 

Search all posts for:   

 

Top tags: ITSM16  PSMF  ITSM  Q&A  Service Catalogue  SIAM  business change  Career  DevOps  Podcast  problem management  Release Management  Service Transition  SITS16  Are we the wrong people in IT  Automation  BCS  CGI  Digital Transformation  Event  EXIN  IOE  IOT  ISACA  IT4IT  ITIL  ITSM15  Managing Complexity  Organisational change  Scopism 

ITSM16 Q&A: Matt Hoey, Transition SIG Chair

Posted By Matt Hoey, 24 October 2016

In the lead up to ITSM16, we'll be posting blogs from various people answering a simple Q&A about ITSM16 and why they'll be attending this year.

Matt Hoey, Chair of the Transition SIG, follows Richard Horton and Anthony Oxley.


What are you most looking forward to at ITSM16?
It's got to be the networking, meeting old faces and new, and the range of presentations on offer this year.

What have you got out of attending previous ITSMF UK conferences?
Not wanting to go all British Cycling or Team Sky, but it's marginal gains! Whilst we've got established Service Management processes and I've never come away thinking I must re-write my Change Management or Incident Management processes, the opportunities to get tips, tweaks and good advice through the presentations and networking provides a wealth of invaluable improvement opportunities.

Why are you attending the conference this year?
I'm presenting on the ten things you should know about service transition with the Service Transition SIG which should be a great, fast moving presentation and going solo presenting advice on building services in an agile manner.

 I'm also looking to get lots of takeaways from the other presentations, recruit new SIG members and celebrate reaching the Thought Leadership award finals with the Service Transition SIG.


What’s been one of the biggest changes in the ITSM industry in the past 25 years?
Can't comment on the full 25 years (sadly ITSM hadn't made it on to the school National Curriculum back then), but within the recent years it has definitely been the expansion of agile frameworks beyond the traditional use in software development.

What are you most looking forward to in the future of ITSM?

Seeing how the best practice frameworks evolve to take on the challenges of lean, agile, DevOps and cloud. Also seeing the new ideas and movements that will arise from the younger generation as they move into the industry.

What excites you most about companies embracing PSMF?
I agree with Tony - proper recognition for the ITSM professional. This'll surely provide motivation to those in the industry and appeal to those outside to join it.

In ten words or less, what does being an ITSMF UK member mean to you?
Access to help, advice, resources and fantastic like minded people.


ITSM16 is less than a month away. Book now, or call us on 0118 918 6500.

Tags:  ITSM16  Q&A  Service Transition 

Share |
PermalinkComments (0)
 

Release Management - Delivering More and Breaking Less

Posted By Richard Horton and The Transition SIG, 30 June 2016
Updated: 30 June 2016

 

If you want a one-line summary of the challenge faced by people delivering IT services, you could do worse than “How to deliver more and break less”.

 

Given that there isn't a limitless pile of money available to throw at this problem, and that there are constant pressures to reduce costs, clearly we need to improve our practice if we are going to reduce the breakages.

 

The good news is that there is room for improvement. Despite years when change and release management have been viewed as core ITIL processes, likely to get an organisation’s attention before many others, we still haven’t got these essential elements cracked. Much is spoken about agile and DevOps, but when push comes to shove, many people are still taking a more ‘traditional’ approach to release management, if they have got that far.

 

At a recent Service Transition SIG meeting, we took a look at the sort of challenges that face us in deciding how to do release management, and a range of approaches we can use in addressing them. 

 

We started with our hosts Arqiva, who outlined to us the complexities that they face as they serve customers with competing demands. They have to balance their requirements on a shared infrastructure. And if they mess up, they are acutely aware that the nation will know, as their mistakes have the power to bring down television or radio transmission. Arqiva explained how they have delivered impressive increases in the reliability of change implementation, but still face some challenges in release management.

 

So what sort of models could be applied? There isn't a ‘one size fits all’ here. Some organisations, we discovered at the meeting, focus their release management more at the technical level, while others opt for an implementation scheduling approach. Others might want more of an enterprise overview, coordinating the dependencies which projects look after. We looked at the challenges faced in each case and the potential role conflicts inherent to each approach.

 

We then considered how to bundle releases, whether going for the ‘small and often’ or the ‘big and occasional’ approach (or a mixture). We considered the possible constraints in both cases and what kind of a release plan you might put in place to help alleviate these limitations.

 

Smaller and faster projects tend to be linked with agile, but this isn't necessarily the case. Those using the traditional ‘waterfall’ approach can learn from agile here. On the other hand, if attempts to be more agile are too eager, there is a danger of relaxing the waterfall controls without recognising that agile has controls too. Basically there isn't a shortcut. If you want to improve you have to work at it.

 

Planning is an important area. We considered the factors that can torpedo what might look like a good plan, complete with plenty of contingency, as projects still end up getting put back and put back, with huge overruns resulting.

 

So, now we have set ourselves up to deliver more. Great... but only if it works. How do we reduce the fallout? Approaches to testing are key. A measured approach comes in handy here. Things don't always work first time so why do we assume they will? We want a well thought through approach to testing, including awareness of the risk/opportunity equation, so that we are not just doing endless testing for the sake of being bullet proof, but delivering too late to be of any use.

 

If we understand the importance of good testing we will prepare our scenarios in advance, consider where automation can help (bearing in mind the pay-back period) and, where we are not automating, assign people to perform testing who have both the right skills and the will to do it. And it would be really helpful if we could ensure our environments match as well, so that we are testing like for like and can see the wood for the trees.

 


 


If you would like to find out more about the Service Transition SIG’s work on release management, why not attend one of their regular events which you can find on our event calendar.

 

ITSMF UK also run a series of workshops and masterclasses covering many topics including Release Management.

 


               

 

This article first appeared in the Spring 2015 issue of Service Talk

Tags:  ITSM  Release Management  Service Transition 

Share |
PermalinkComments (0)
 

Premier Gate
21 Easthampstead Road
Bracknell
Berks RG12 1JS

Tel: 0118 918 6500

Fax: 0118 969 9749

Contact Us