Don’t wait until you have your Service Catalogue “closed”: that’s not happening (if you do things the right way…)

Moses introducing Service Catalogue v1.0

While reviewing a few requests for change to be submitted to the weekly CAB meeting, I told my manager about 2 of them in which there was no affected service recorded; well, in fact there was something written in the field “Affected Service”, but it was not present in the Service Catalogue.

My boss didn’t want to change it for one of the services that actually exist in our Service Catalogue as he says “the Service Catalogue is not closed yet”. I thought he meant our current Service Catalogue was only a draft pending of validation or whatever, but he didn’t: what he meant is that our Service Catalogue has not been carved in stone yet, if you let me put it that way. That’s what he means with “closed”. Well I’m afraid I have to tell him that’s never happening, if we do things the way God dictates…

Read the rest of this entry »

APMG announces ITIL V3 Master certificacion

At last, the APMG has announced the ITIL V3 Master Certification.

Now, let’s wait and see who’s first achieving it…

ITIL wants YOU!

When launching ITIL V3 back in June 2007, the OGC announced the establishment of a cyclical program to update its core guidance books, to take into account the latest developments in Service Management best practices.

Now, the OGC and the Stationery Office are recruiting participants to update the five core publications (the Service Lifecycle books) and the “Introduction to the ITIL Service Lifecycle” book. The participants will be two kinds: authors and reviewers.

Check out for the official announcement. It’s not quite clear what you get in return, aside from prestige of being credited in the books. Hey, it would be OK and more than enough for me. Maybe they could even handle out an all-inclusive invitation to the next ITSMF congress… it would be worth the effort (they could think of an exotic destination next time, Barcelona is not really appealing to me…).

What about you? Would you like to participate? Do you think a public announce is a good step on broadening ITIL scope and incorporating new trends (and, more important, new realities) to its core books? Please share your thoughts on the comments.

Service Portfolio and Service Catalog: Zombie Killers

I smell your abandoned Sharepoint site from here...

I read on CA on Service Management blog a funny post by Dave Wilt remarking how important is continuous Service Catalog and Service Portfolio management, and the need to keep them up to date to avoid what Dave Wilt calls “zombies” in our organizations: those IT assets or CIs no longer needed that wander around our datacenters. According to Dave’s definition of “zombie” in an organization:

Where are the zombies in your enterprise?  How about virtual machines that were quickly and easily spun up but are no longer needed or used?  SharePoint sites?  File shares, intranet pages, user desktop software?  User accounts? How about entire business or IT services?

Dave Wilt thinks of Service Catalog as a weapon to fight zombies, with a closed-loop approach on provisioning using a Service Catalog. One of the points he insists the most is “cost transparency”, that means: whether or not a formal chargeback model for IT services provisioning exists, users that request a service (and their managers) must be informed of the cost of delivering that service through time. It might be tough for some IT shops who are just starting to deal with their very first Service Catalog to think of setting up Financial Management, but I believe that, unlike IT jargon, money is a universal language that everyone in the company will understand.

Nobody wants to be expensive; nobody wants their department to top the Big Spenders list at their organization; so let them know how much a new virtual machine costs when someone asks you to spun up “3 or 4“. I don’t mean you should use bills to frighten away the beggars, but you must collaborate on making them become conscious about what they are asking and maybe rethink if they really need that many and that big.

It’s quite interesting to read the full post, just in case you need one more reason to be convinced that Service Catalog is the cornerstone of healthy IT Service Management.

You can read it here.

Root cause maps: aren’t they sexy???

Cause Map - ain't it hot???

The guys from ThinkReliability are offering an Excel template that can be used to track and document any problem investigation, including the tools needed to draw a root cause and process map -yes, in Excel. As they say:

Most people think of Excel as only an application for creating spreadsheets, but it’s an excellent tool for capturing each element of a complete root cause analysis. By changing the way details are documented, a facilitator can improve the entire investigation process. The drawing tools are simple, flexible and Excel is probably already on your computer.

I must add to that: you don’t even need Excel on your computer, you can use Google Docs -it’s free and a solid tool for work teams.

It’s not specifically addressed to deal with IT problems, but it’s not really that important; after all, IT problems are problems anyway. The main advantage to me of this template is it can be used to draw a cause map easily in a few clicks; on a tab you can find a lot of basic shapes (boxes and connectors), you copy them to the tab labelled “Cause map” and you’re done. Detailed instructions can be found in the template. Worth having a look at it.

You can download The Cause Mapping Template in Microsoft Excel here for free (no money and no registration required), and the list of advantages using MS Excel brings according to ThinkReliability.

PS: have a look at their blogs, plenty of useful examples on how to perform an RCA and its deliverables.

Send in the poka-yokes

While dabbling around with some Six Sigma papers this afternoon, I stumbled upon a funny term: poka-yoke. You can read about it here. A poka-yoke device is any mechanism that either prevents a mistake from being made or makes the mistake obvious at a glance, such as an USB connector which can be plugged one way only. It’s an error control mechanism oriented to avoid human mistakes when operating it.

There are plenty examples of poka-yoke devices and how to implement them on manufacturing chains and industrial processes, but I wonder: could they be useful on IT processes and procedures and how could they be implemented?

It’s important as many incidents raise in an organization due to human error; frequently, some RCA on those incidents conclude that an operator hit the wrong key or inserted the wrong tape on a drive… So, as to me poka-yokes look like a sound error-control mechanism, I’m looking for ideas on how to implement them on our IT Operation.

Problem Management: your customers deserve a (reasonable) explanation

I read on  The Opposite of Luck blog a post about a forensic report explaining the cause of an incident that caused an outage at Fisher’s Plaza Technology Complex in Seattle and took down many websites hosted there.

Like them, I applause how transparently Fisher’s Plaza have dealt with this incident, specially regarding their tenants, as they really deserve an explanation.

You can read the full report here.

Your users also deserve an explanation when an IT service goes down; you don’t have to give them a 12 page report for every problem you manage, but you can’t simply shrug your shoulders and tell them “shit happens”.

Urgent changes: WTF?

Excuse me if I’m rude, but many idiotic things have happened around at my office: we’ve finally launched our new service desk tool, after 9 months developing it (average time spent at other clients was 1 or 2 months). Though it was meant to be ITIL compliant and so support the adoption of the framework, our IT manager has decided to, er, redefine some ITIL terms, specially those regarding change management and SLAs.

So, he has introduced a new type of change: urgent changes. Nothing to do with emergency changes: urgent. What’s an urgent change? A change to be done ASAP. But not in an emergency case, ie: a project manager wants to deploy his new version of app X, and he wants it now. This new version doesn’t solve a major issue with the previous release or adds functionality that the business imperatively needs due to legal issues or whatever reason you can think of for an emergency change, because, and that’s the point, it’s not an emergency. Usually, it will just be a project deadline too close and a project manager unwilling to take the blame for the delay of the release (why take the blame when you have the IT crowd to take that blame as “they won’t deploy the app until next week”?).

Where I see nothing but fighting what a best practices framework dictates, my manager and his mates think they’ve had a great idea because with urgent changes they show how customer oriented they are. Bullshit.

And WTF, where the hell have they read on ITIL core books the term “urgent change”???

Spanish trends on quality management: downgrading quality

Sometimes the best work meeting is the one that never took place

I’m back from one of the most surreal work meetings I’ve ever attended, with my boss and a fellow worker, to plan the moving of three branches to a single building. I had my list of topics to be covered at the meeting, including which changes we would have to do at our servers and network configurations (and the changes we would have to raise to our external providers) in order to get everything up and running by the end of the 4-days time frame we’ve been allocated to complete the moving, that is: for all applications and services to be running at normal levels for all users.

But my boss has told me to put it aside and we wouldn’t talk about it at the meeting, because he prefers to deal with other issues of the process of moving (such as connecting users’ computers and relocating an incredibly vintage -but resilient- AS400 server). About those other things on my list… he wouldn’t worry a bit; once the users begin their work at the new building, they would report us what’s wrong and what they miss and what app is crashing or won’t print or won’t connect to the database server, and then we’d get fixing and changing all those configurations we could have made in advance.

That’s a deathly strike for anyone aiming to reach high quality levels at his work, as he’s asked to put aside his will of continuous improvement and work on downgrading the quality level of the IT services instead.

Sadly, I must admit this is not the first time I’m faced with such an awful attitude at other jobs I’ve had, and I wonder if this need to turn down quality for no reason, this need of continuously claim the need to change “something” to improve but, when the chance to effectively do something to improve comes, do nothing, is just an Spanish syndrome or it’s pandemic.

XXth Century Banks

I’m planning my summer holidays these days, and mainly doing it through the Internet, from the flights to the museum tickets, but trouble has come down when booking an appartament for our stay, not really because of the agency (Isabelle has been very nice and collaborative until now), but because of the pains my bank is inflicting me.

I switched my bank account to Caixa Galicia early this year, as it looked like a modern savings bank: no fees for domestic or international transfers or cash withdrawal at any cash point, automatized phone service, and what seemed, at first, a solid online banking system.

Read the rest of this entry »