Translating a Service Catalogue SLA to Projectized Work?
Anonymous
Has anyone created a service catalogue that listed what is typically projectized work as a service, and assigned an SLA to it? If so how did you go about it.
I am being asked to provide an SLA for projectized work that is currently un-defined. I.e. there is no clearly defined scope or charter, yet I need to provide a generic SLA that will encompase all possible projects that result from the Service Catalogue offering.
For Example, the Catalogue service offering is: "Analysis and re-design of exisiting application" - "Application" being any as yet un-specified app.
I can understand if your organisation wanted to create a service catalogue for services provided that do include SLA's a good example is the IT Service catalogue where it provides by department and functionality the scope, its responsibilities, what they do, turnround times hence the SLAs. Specifically to create a service catalogue for projectised work how is that going to work when each and every project is unique, and even if you were to generalise how accurate is the info likely to be. You may want to think in terms of Project Office and or Programme Management Office then put down the processes for undertaking projects for delivering as business solutions, this would be far more valuable as everyone concerned would follow the process when proposing potential projects that will go through PMO, who does what and by when etc. before assigning a Project Manager. Saving Changes...
