Service life cycle in a nutshell

Effective service governance requires that you understand the complete service life cycle. A service starts life as a proposal.This fledgling service is to caputured by the governance group to ensure that it's unique and also has the potential to be reused by many users. The next stage requires the proposal to be fleshed out and a project plan begins its development. Keeping track of and publishing the scheduled services is important for resource planning and also allowing other consumers or the prospective consumers to see what is to be expected. Next the service goes into development. And the service governance group may well want to inspect the development of predefined quality quotes. At the early stages of the service rollout, the group may also want to provide active design support for these projects. If all goes well the service will go into production. As it is now widely available, its details should be published, for instance, in a repository. The server group will also be advised to track the consumers, the usage and the performance of the service. These metrics can be used to monitor the performance of the program as a whole. The group also need to deal with change management and incident management. At some time, the sevice needs to come out of production. It's advisable first to set a duplicated state and notify all users that the service may need to be retired. This may cause disputes and these need to be resolved. Finally, the service is retired and all references to it and registries in the repository need to be removed. This is just the lifecycle of one service. You have to remember however  that there are many duifferent services being developed, each with different projects each of which have their own life cycle. To manage this complexity, you have to have good governance processes in place and also the corresponding tools to be able to maintain or complete the service life cycle.