A project may be:
· A set of tasks/activities whose aim is to deliver a changed (new/modified/deleted) set of functionality (otherwise known as a release).
· A project lifecycle starts in the planning and requirements stage and ends when all project tasks are completed and the deliverables are released into production.
Benefits of the CM Levels
The CM levels provide a structure that will allow you to best align the CM tasks to where you get the most benefit. To determine where you will get the most benefit, identify the target audience of the CM task.
Before beginning a CM implementation effort, it is important to determine the level since it will improve your chances of successful implementation and deployment. To identify the level, consider the following:
Identify if the CM task and its deliverable is expected to live the duration of an organization, an application, or project. With the results of the bullet item above, who in the organization level, application level, or project level is the primary beneficiary of the task or deliverable and who may help the SCM professional best ensure adoption of the deliverable or completion of the task?
For example, the CM implementation involves establishing a CM policy. First, identify if the CM policy is to live throughout the life of the organization, an application, or a project. Then identify who the CM professional needs to work with to get this accomplished. If the CM policy is only for an application (application lifecycle), then the CM professional should work with the owner of application (a.k.a., product manager) and the CM implementation should be conducted at the application level. However, if the CM policy needs to live the duration of an organization, then the CM professional needs to work with senior management to ensure adoption of the CM Policy within the entire organization.