A service undergoes many forms in its lifecycle, and Professor P. Ross S. Wise delves into the intricacies of four of those forms in a post at his blog. His particular selections center around turning suggested services into officially authorized services that meet clearly defined objectives. Are you sweating with excitement yet? Because I obviously am.
Four States of the Service
At “define,” you plainly want to identify desired business outcomes, and of course the specific function of the service itself. The context in which the service operates should be explained as well, so its impact will be best understood. The “analyze” status needs more of a team effort. Wise says it requires a specialized group, often including engineers, architects, and managers, to evaluate a potential service. The aim of their efforts is to collect the most data about the service using the least intrusive means.
Once all the data has been collected, management, customers, and executives can get together in the “approve” status to decide if the service is feasible. There end up being several rounds of approvals, each with their own set of priorities. And finally, with “charter,” Wise states:
This is a document authorizing the work to begin. It has defined objectives, outputs, schedules and expenditures. Charters are usually used to initiate the design stage of a project or change. The charter ensures that all development, testing and deployment staff have a common understanding of what is to be built, by whom, a schedule of when and a budget of how much it will cost…The charter will typically include an overview, scope and objectives, assumptions, sponsorship, deliverables, resources, risks, schedules, controls and authorities.
It takes a vast amount of time and resources to get a new service off the ground in the best possible way. Anything less could be a risky proposition. You can read the original post here: http://www.itsmprofessor.net/2014/11/the-status-of-service.html