Posted: Tue Jan 29, 2013 5:35 am Post subject: ITIL and SCM
I am a SCM (software configuration management) specialist.
From what I see, most of large organizations have a line between development area and production/operation area, due to many reasons, historical or outsource, etc. So there are a set of SCM processes (version control, build and deploy, change & release mgmt) for the development area, and another set for production, e.g. production change control.
Traditionally, the SCM specialists are working in the development area most of time, doing version control, change request, sort of things, util the software is relesed to production for operation.
My understanding of ITIL is more for production operational control. Therefore, as a SCM specialist, I haven't met with ITIL until today. However, we start to talk about things like continuous delivery which stretch all the process all the way to production. Now my question is how shall we deal with ITIL from SCM point of view? Merge? How?
Joined: Sep 16, 2006 Posts: 3320 Location: London, UK
Posted: Tue Jan 29, 2013 6:11 am Post subject:
ITIL is a set of better practices.
That is it.
It is not exactly as you state.
The ITIL process set covers the entire life of a IT project from the concept to the installation and then on to the support
I am a Release Manager. I used to be a Change Manager and a Change / Release ./ Configuration mgr.
There are couple of posts in here where I talk about the SDLC and how it fits in ITIL
Here is the short version
Release Management is concerned with the building, deployment and testing of a release. A Release can be vendor patch, h/w, s/w, firmware or bespoke developed code.
All Releases would go from the development environment to the System Test, Integration, Quality Assurance / Acceptance test environment before it is put into Production.
As the RM, I define the rules and process for getting from Dev to QA/ and Production for that matter. Who does, who approves, what is recorded, they get defined more stringently as the release gets closer to Production.
As such, I exhert little oversight - good word - over developmenmt, a little more over ST and SIT, a lot over QA / AT. and full control over the production release.
In addition, I work with the Environment manager and I oversee all work done to the environment that is generic- system stuff, server stuff but not code dev stuff.
As the RM, I have delegated authority to the Design & Buidl projectlead to manage the dev --- etc.... to QA / AT.
I work with the S/W Config mgmt team (me as I own the tool set providing appplication source code control, version and defect mgmt) and the development team leads to define how the code is checked in when etc and how the packages are made.
I work for / along side / with the CHange Manager. I provide key data and help provide the guidlines that must be met in order for releases to go to production. the CM manages the approval process.
THe key guidlines - NON PROD QA first, and then the same in PROD
That is IT Service Management using ITIL _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
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