| View previous topic :: View next topic |
| Author |
Message |
tomkin
Itiler
![]()
Joined: Jun 29, 2009
Posts: 48
Location: London
|
 Posted: Wed Sep 09, 2009 10:09 pm Post subject: Release Policy |
 |
|
What exactly is Release Policy ?
1. Is it Enterprise Release Policy (Guidlines for release in the enterprise) ?
2. Is it Release Policy per application/service ?
If it is both of the above then isn't naming a bit confusing for the people who are going to follow it ?
How do you guys maintain these two (assuming you require both) in your org ?
Thanks,
Tomkin |
|
| Back to top |
|
 |
MBU
Senior Itiler
Joined: Dec 18, 2008
Posts: 70
|
| Posted: Wed Sep 09, 2009 11:05 pm Post subject: |
|
|
Tomkin,
there's a detailed description of the content of a release policy on p. 215 in the red book ...
quote: A Release policy should include:
/quote
Hope this helps,
_________________
Michael B.
"I can't say it'll be better if it changes, but I can say it has to change to be good"
G.C. Lichtenberg (1742 - 1799) |
|
| Back to top |
|
|
MBU
Senior Itiler
Joined: Dec 18, 2008
Posts: 70
|
| Posted: Wed Sep 09, 2009 11:06 pm Post subject: |
|
|
BLUE book BLUE book BLUE book BLUE book
I'm getting old ... maybe I should read one of these new books with more fancy colours |
|
| Back to top |
|
|
tomkin
Itiler
![]()
Joined: Jun 29, 2009
Posts: 48
Location: London
|
| Posted: Wed Sep 09, 2009 11:39 pm Post subject: |
|
|
V2 ???
Unfortunately, i dont have access to those. Only v3.
How can I look at those, I just need a very high level view.
Thanks for your replies  |
|
| Back to top |
|
|
DYbeach
Senior Itiler
Joined: May 25, 2008
Posts: 413
Location: Sydney, Australia
|
| Posted: Thu Sep 10, 2009 9:33 am Post subject: |
|
|
some key words could be
• Release Unit
• Full / Package / Delta Releases
• Numbering
• Frequency
• Emergency Change
My invoice is in the post 
Seriously though, Google is your friend
_________________
DYbeach
ITIL V3 Release, Control & Validation,
ITIL V3 Operation SUpport & Analysis
PMI CAPM (R)
"In times of universal deceit, telling the truth will be a revolutionary act." George Orwell |
|
| Back to top |
|
|
UKVIKING
Senior Itiler
Joined: Sep 16, 2006
Posts: 3590
Location: London, UK
|
| Posted: Thu Sep 10, 2009 3:52 pm Post subject: |
|
|
tomkin
so if you have access to v3 bokks then it should be easy then
service transition page 24 25
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter |
|
| Back to top |
|
|
thechosenone69
Senior Itiler
Joined: Jun 06, 2007
Posts: 268
|
| Posted: Thu Sep 10, 2009 6:12 pm Post subject: |
|
|
UK,
I thought you havent read the V3 books. |
|
| Back to top |
|
|
UKVIKING
Senior Itiler
Joined: Sep 16, 2006
Posts: 3590
Location: London, UK
|
| Posted: Thu Sep 10, 2009 7:45 pm Post subject: |
|
|
I have them
I have not read them
I looked up the section by looking at the table of contents
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter |
|
| Back to top |
|
|
DYbeach
Senior Itiler
Joined: May 25, 2008
Posts: 413
Location: Sydney, Australia
|
| Posted: Thu Sep 10, 2009 8:09 pm Post subject: |
|
|
Hey hey, my my
Version 2 will never die
(thanks Neil) 
_________________
DYbeach
ITIL V3 Release, Control & Validation,
ITIL V3 Operation SUpport & Analysis
PMI CAPM (R)
"In times of universal deceit, telling the truth will be a revolutionary act." George Orwell |
|
| Back to top |
|
|
tomkin
Itiler
![]()
Joined: Jun 29, 2009
Posts: 48
Location: London
|
| Posted: Thu Sep 10, 2009 9:35 pm Post subject: Re: Release Policy |
|
|
| tomkin wrote: | What exactly is Release Policy ?
1. Is it Enterprise Release Policy (Guidlines for release in the enterprise) ?
2. Is it Release Policy per application/service ?
If it is both of the above then isn't naming a bit confusing for the people who are going to follow it ?
How do you guys maintain these two (assuming you require both) in your org ?
Thanks,
Tomkin |
Guys, I understand what a release policy contains. And V2 and V3 contain the same content basically. And I think its bit vague and gives you more freedom.
But if you can help me with what do YOU guys do as best practice ? The question above still needs to be answered |
|
| Back to top |
|
|
MBU
Senior Itiler
Joined: Dec 18, 2008
Posts: 70
|
| Posted: Thu Sep 10, 2009 10:14 pm Post subject: |
|
|
Tomkin,
I (consultant) work NEVER nor do I use best practice, I only recommend to my customers what they should do ...
e.g. when implementing a Release policy I guide them exactly to the topics on p.215 (I LOVE v2); look whatelse is existing in the company and add/remove topics. For this ITIL is a frame and you should apply what exists in YOUR company( sh.., this could be a best practice)
Or do you not understand what a policy is in general? Or how to make it "alive"?
The maintenance of these policies are under control of Change Mangement.
Hope this helps?
_________________
Michael B.
"I can't say it'll be better if it changes, but I can say it has to change to be good"
G.C. Lichtenberg (1742 - 1799) |
|
| Back to top |
|
|
UKVIKING
Senior Itiler
Joined: Sep 16, 2006
Posts: 3590
Location: London, UK
|
| Posted: Thu Sep 10, 2009 10:24 pm Post subject: |
|
|
tomkin
Well. The short answer is it depends
As Release is the terminology for implementing all approved changes, the policy for release may be both or merely against the area where it and change management is used
it all depends on things
for example if you dont deploy code, your policy will be different than if you do
it all depends on the it business in question
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter |
|
| Back to top |
|
|
tomkin
Itiler
![]()
Joined: Jun 29, 2009
Posts: 48
Location: London
|
| Posted: Thu Sep 10, 2009 11:52 pm Post subject: |
|
|
| Thanks guys, you are indeed helpful lot |
|
| Back to top |
|
|
rpmason
Senior Itiler
Joined: May 25, 2007
Posts: 105
Location: USA
|
| Posted: Fri Sep 11, 2009 1:43 am Post subject: |
|
|
| Quote: | | Unfortunately, i dont have access to those. Only v3. How can I look at those, I just need a very high level view. |
Sorry, Tomkin. We could provide you with 2 or 6 or 10 Release Management policies but they wouldn't apply to your business or fit your ITSM processes.
Here's my advice:
1. Scan (at least) the books you have
2. Apply that knowlege to your environment
3. Work with your business people and with your ITSM process managers
4. Devise a plan that fits your business
5. Consider how that plan affects your IT folks
6. Implement it
7. Figure out the "gotchas" and improve the process.
8. Repeat.
If you can't do that, spend $$ on a consultant who can.
_________________
Ruth Mason
USA |
|
| Back to top |
|
|
Diarmid
Senior Itiler
Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh
|
| Posted: Thu Sep 24, 2009 7:26 pm Post subject: Re: Release Policy |
|
|
| tomkin wrote: | | tomkin wrote: | What exactly is Release Policy ?
1. Is it Enterprise Release Policy (Guidlines for release in the enterprise) ?
2. Is it Release Policy per application/service ?
If it is both of the above then isn't naming a bit confusing for the people who are going to follow it ?
How do you guys maintain these two (assuming you require both) in your org ?
Thanks,
Tomkin |
Guys, I understand what a release policy contains. And V2 and V3 contain the same content basically. And I think its bit vague and gives you more freedom.
But if you can help me with what do YOU guys do as best practice ? The question above still needs to be answered |
No one seems to want to tackle the question head on.
Release policy is release policy.
In simple terms it is both 1 and 2 but there is nothing confusing in the naming because it is not a name but a policy. Policy is addressed in procedures and procedures don't get confused anyway.
However, 'simple terms' is not good enough.
From the perspective of the infrastructure, you only want one all-embracing release policy. Specific apps etc. may have release strategies that adhere to that policy and hence they may have separate procedures.
Of course, you might have sections in your policy for (e.g.) hardware and software and firmware if you think you need them. But it is hard to conceive of a situation where there was not an overarching aspect of the policy concerning the integrity of service within that infrastructure.
If you want to call lower level entities policies then they would refer upwards to the parent policy. you still should not have naming confusion because these elements will have context (e.g. "Server Release Policy" rather than "Release Policy")
I'd better stop there. I've a lot of catching up to do.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718 |
|
| Back to top |
|
|
|
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
