For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
The Itil Community Forum: Forums
ITIL :: View topic - Relationship between DEPLOYMENT and RELEASE MGMT
Posted: Wed Feb 23, 2005 9:12 pm Post subject: Relationship between DEPLOYMENT and RELEASE MGMT
ITIL states that a relationship exist between DEPLOYMENT and RELEASE MGMT (in the ICTIM book par. 3.3.3 External interfaces). However, clarifications to explain this relationship seem to be missing in the paragraph. Can anyone further clarify this?
Thank you.
Joined: Oct 06, 2004 Posts: 77 Location: Bloomington, IL
Posted: Tue Mar 08, 2005 1:13 am Post subject:
The intro to ICTIM section 3.3 states that Deployment is best handled by Project or Programme Management. The relationship is not clear because the current version of ITIL does not delve into Projects very well. It relies on PRINCE2 and other project methodologies to handle projects.
I personally believe that project management should be a subset or discipline within the overall ITSM framework, not a separate disipline. If you think of it this way, projects fit well within the Change, Release and Config Function. Project requirements could then be provided through the SLM and Design processes. The purpose of a project then becomes to add, improve or sunset IT Service capability.
There are probably other opinions among the community...
Posted: Wed Mar 09, 2005 2:24 am Post subject: My two cents...
I would tend to agree that project/program management has to fit within the ITSM framework, and the main interface point is change/release management.
I would look at it like this:
-Problem management logs the initial request.
- Problem Management hands issue off to project team once size/risk/impact investigation reveals that the issue requires that that extra level of discipline be applied to deploying the solution.
- Project prepares to deploy based on schedules and guidelines established by Release Management (the actual "Change Implementors") group.
- Change Management ensures that project followed the established standards before approving deployment.
- Once release/change/patch/whatever your terminology is has been approved by Change Management, it is deployed by Release Management, who then follow up back to the Problem Management team (who it is assumed would assist in the post-implementation review with Change Management and the business users).
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum