become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 8 ■ Continual Service Improvement<br />
autoremind action owners before the milestone dea<strong>dl</strong>ines and will send out automated<br />
reports as per the crystal reporting structure.<br />
8.5 Baselines<br />
When you develop reports on performance achieved or any other similar reports, it<br />
is important to have a threshold defined. The performance threshold acts as a point<br />
of <strong>com</strong>parison, and it helps provide the context for the improvements or downturns.<br />
This threshold is called a baseline in ITIL. We use baselines in a number of processes<br />
in ITIL, such as creating configuration baselines in the service asset and configuration<br />
management process.<br />
In CSI lifecycle phase, the baselines play an important role in measuring the level of<br />
improvement that was brought about through the undertaken improvement initiatives. It<br />
provides a basis for the extent of the improvements applied.<br />
When a baseline is drawn, it needs to be documented, circulated, and agreed upon<br />
by all involved stakeholders to achieve transparency and agreement of the <strong>com</strong>parison<br />
marker. Baselines <strong>com</strong>e in different levels: strategic, tactical, and operational baselines.<br />
When baselines are created, they need to be examined at all three levels.<br />
If a baseline is not obtained before embarking on an improvement project, the<br />
extent of improvements achieved will be questioned, and the measurements taken<br />
postimprovements will be set as the baseline for up<strong>com</strong>ing improvements.<br />
8.6 Types of Metrics<br />
The performed improvements need to be measured to determine whether they have<br />
ac<strong>com</strong>plished their intended purpose. This is achieved through metrics, which is defined<br />
in ITIL CSI as a scale of measurement defined in terms of a standard (well-defined unit).<br />
Let’s say that you have performed an improvement initiative to reduce the overall<br />
number of incidents. How do you measure it? Through metrics. For this example, the<br />
number of incidents logged in a calendar month is the metric that provides the needed<br />
measurement to vet whether the improvement has been effective. Generally speaking,<br />
metrics provide the quantitative view of the activity or the process or anything that needs<br />
to be measured.<br />
Metrics are generally tailor made for the activity you are trying to measure. A metric<br />
defined for one activity cannot be readily used for another activity. Let’s say that you have<br />
another requirement for a metric to measure the percentage of failed changes in a month.<br />
You cannot use the incident metric to measure this.<br />
For failed changes, you need a separate metric:<br />
Percentage of failed changes in a calendar month<br />
= (failed changes / overall changes) × 100<br />
However, there are some generic metrics, such as number of incidents, number of<br />
changes, and percentage of service uptime, that can be used across the board.<br />
217