We get this question about granularity a lot. James at the Coast Guard asks:
Service Catalog granularityWe just started gathering our service info and I'm running into a problem deciding on the level of granularity I need. I suppose it boils down to deciding which activities really are services and not just processes of a service.
For example, one of our divisions listed desktop support as a service, with various activities under that like patch management, user additions/deletions. Where do you draw the line and say "This is a service," or "This is a process under a service?" Are there some reasonable rules of thumb to help decide this?
I've written about this here and on "Using Components in a Service Catalog."
So I invite you to help out the Coast Guard with their service catalog
Comments