Keep up-to-date with ITIL news. Low volume to-the-point bulletins...
  2. Service Transition
  3. Release & Deployment Management

ITIL v3 Suggested Release and Deployment KPIs [1 comment]

ITIL General
ITIL Practitioner
ITIL Foundation
ITIL Guru
ITIL Manager
KPIs for ITIL v3 Release and Deployment
At ITILnews.com we are committed to providing value to the Service Management marketplace.  This article provides those of you responsible for Release & Deployment a suggested set of KPIs that you can utilise.
 
Number of software defects in production
Number of bugs or software defects of applications (versions) that are in production.
% of successful software upgrades
Percentage of successful software upgrades (excludes full installations).
Number of untested releases
Number of untested releases i.e. not tested and signed-off.
Number of urgent releases
Number of urgent releases.
Average costs of release
Average costs of release. Costs are most likely based on man-hours spent.
We have sourced the above from http://kpilibrary.com. If you have any further KPIs then please feel free to share them with us...
 
 

1 VISITOR COMMENT

2013-06-04 by "tsz"

For a percentage value a base is needed. I wonder what the base of "% of successful software upgrades" may be. I assume it is the number of all releases including the ones that were rolled back.

Beside of this, the number of defects in production for software needs a clear definition. Defects reported by customers usually include change requests as well. Defects found by ourselves could be features in the next release.

Finally a defect could just be a deviation from requirements and specification. But even the requirements and specification could be incomplete - if they exist at all and if they are up to date. There are implicit requirements in almost every software.

If the requirements are not clear, how could the software be and how could the KPI be finally?

I have finally found an additional KPI that tells about the average duration of major deployments from clearance until completion - Duration of Major Deployments.

If some continuous delivery comes into game, the proportion or percentage of automatically rolled out software could be interesting as well.

YOUR COMMENTS...

Please submit any comments you have about this article.

Your feedback will help add value to the content for other ITILnews.com visitors and help us develop the content for the benefit of all.

You will need to provide and verify your e-mail address but your personal information will not be published or passed on to others. To identify each post we take the part of your email address before the @ sign and use that as the identifier, so if you are john.smith@itilnews.com your post will be marked "by john.smith".

NB: We respond personally to every post, if it calls for it.

If you prefer to respond without posting your comment please use our contact form.


Click the REVIEW button below to preview your comments.

Other articles in the same section;
 
Tags; ITIL v3,Release and Deployment KPI,Service Management,Release & Deployment
 
This article has been viewed 29259 times.
NB: This page is © Copyright ITILnews.com and / or the relevant publishing author. You may copy this article only in it's entirety, including any author bio and / or credits, and you must link back to www.itilnews.com.

Keeping up-to-date with ITIL...

Keep up-to-date with ITIL news. Low volume to-the-point bulletins...