How many people using change management for SDLC?Hi,

I am totally with you. ITIL V3 (and earlier) Change Request = Changing of 
configuration item (CI). That's it, period.
That's possibly the reason of including release management in 7.5. Frankly, if 
you look from the business side, the release management has very different life 
cycle than the change, although the terminology is very similar, Rational tools 
is very good example.

A release will require a change at some point.

So, stick with the ITIL def of the process. It is easier to design your own 
release management instead trying to deploy change for release purposes.

Change Request = Changing of CI. Any other use of change management is simply 
application abuse.

Regards,

Nicky Madjarov
phone: 973-202-4278
Find out how to bust your AR System performance @
http://www.SpeedUpARS.com
  ----- Original Message ----- 
  From: Lyle Taylor 
  Newsgroups: public.remedy.arsystem.general
  To: [email protected] 
  Sent: Tuesday, March 24, 2009 6:31 PM
  Subject: Re: How many people using change management for SDLC?


  ** 
  In my opinion, the Change Management module is not really appropriate for 
SDLC management.  In general, ITIL (at least V2) doesn't define much that 
relates to the SDLC except where it touches Change Management (requests that 
initiate a change in a system and to approving the deployment of those changes 
into the environment) and Release Management (which is concerned more with 
documenting the system, proper testing and deployment planning).  Everything 
else in between - i.e., actually developing the system and managing that 
development - is pretty much left alone, and the Change Management module in 
Remedy reflects that.  You could potentially use it to track enhancement 
requests or defects and then group those into a master Change, but that seems 
like a bit of a stretch to me and may be difficult to manage.

   

  At my last position, we looked at whether or not we should even use the 
Change Management module for both sides of the Change process (change 
initiation and then deployment) and felt that Remedy Change Management (and 
ITIL) didn't address the front side of that well enough.  While it does allow 
you to add an approval process to changes, the business review, justification 
and approval of new changes (those that would generally involve creating a 
project to address) is a significant enough process in and of itself, and 
Remedy didn't suit itself well to how we wanted to handle that process.  In 
addition, the people involved on the Business side are generally different than 
those that would review a change ready for deployment into the production 
environment.  At the front end, the people are primarily business people with 
some technical people for reference.  On the tail end, you have primarily 
technical people with business people for reference. So, in short, we 
essentially just skipped the first half of the Change process as implemented in 
Remedy and went more or less straight to the technical review and approval for 
deployment.  Other tools were used for evaluating the business justification 
for changes.

   

  Part of whether it would work for you may depend on what type of SDLC you 
follow.  However, I would lean toward tracking your enhancement requests and 
defects in a tool designed for that and then use those to generate Changes, 
where a Change represents a group of enhancements and bug fixes to be deployed 
to the production environment together.  Then, if you wanted, you could create 
a Change Request that contains all of the enhancements and bug fixes you 
propose to put out with a given release, get a business approval on that, 
implement those changes (managing any development specific items in another 
tool of your choice if appropriate), and then continue with the Change Request 
to get a technical approval for release.

   

  I'd be curious to know how other people are using it, too, though.

   

  Lyle

   

  From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Covert, Jack
  Sent: Tuesday, March 24, 2009 4:06 PM
  To: [email protected]
  Subject: How many people using change management for SDLC?

   

  ** 

  Hi guys.  How many of you are using ITSM 7/Change Management for SDLC?  
Anybody using release management?  Details would be great, thanks.

  Jack Covert

  Corporate IT

  Remedy Support Team

  Remedy Support Team Home Page

  http://collaborate.mckesson.com/sites/esm/remedy

  Remedy FAQ Sessions on Thursdays @ 10:30 AM PT

  Details on Remedy Support Team Home Page

  __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___



  NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.

  __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Reply via email to