Last week I gave a talk on property management windsor ca v Service Management at the IT Service Management Forum’s Conference here in Singapore. It wasn’t the best presentation I’ve done in recent years but the topic was a relevant one.
My most recent project, in the manufacturing sector, lasted 18 months and was not my most challenging from a project perspective. However it did highlight several areas that I come across on many projects, more vividly, than most.
The interface between Project Management and Service Management as it relates to the IT world, is broken. Yes, I know, we all know it, we’ve all known it for a long time too. In most cases Project folk like to maintain their unique role as special function and not be seen as art of a “service” organization.
Hey, I was like that too many, many years ago. It’s nice to be different from the crowd, have different responsibilities, and to be on a high profile job, like a major project. Well that’s all fine but it’s not good for the organization investing in the project and it’s a very inefficient way to operate. And here’s why:
Project Management v Service Management
Without a clear definition of the project deliverables that include the service management needs;
- customers requirements may not include support requirements resulting in the project delivering products and services that will not meet service and support needs.
- integration of change process between the two organizations is prone to problems and risks if not operated as one. This can and often does lead to clashes and delays as two organizations attempt changes relating to common infrastructure and operations.
- strategic business decisions that may influence the support model may not be fed into the project solution.
- project outcome may satisfy the initial requirements but be a nightmare for support services to manage and therefore prove a poor long term investment and not deliver to the business strategy 100%.
- handover of the project into an operational environment will prove more of a challenge than it needs to be.
- lack of “synchronization” between project management and support management will cause delays and increased costs against the project.
- Many process and procedures that the project organization need to use or interface with are inefficient for project work or are created specifically for the project and don’t interface or leverage the operational procedures that they need to become part of.
If you look at the ITIL model, the approach to the Service Life Cycle almost emulates the Project lifecycle at high level, in Prince 2. This is no accident. In business the strategies are discussed and presented. The design of a solution to deliver that strategy is worked out and then the solution is built. Once the new solution is in place, well, someone has t support it, don’t they?