Re: How many people using change management for SDLC?

2009-03-25 Thread Stan Feinstein 
How many people using change management for SDLC?Yes, release management is 
very different from change management.  You all might be interested in our AR 
System-based ActionProgram Manager.  (This is an ad, in response to this 
thread).

A release is usually made up of a large number of bug fixes and enhancements.  
The critical question is: will each one be completed by the release date?  That 
means date tracking and ActionProgram Manager includes a critical path method 
date calculator (and Gantt charts and resource charts, etc.) which 
automatically recalculates the finish dates (actually it tracks 10 dates for 
each task) of each task in the project.  Because it's Remedy based, you can 
incorporate this program management functionality into your business processes.

ActionProgram Manager also includes a template capability.  If you have a "bug 
fix template" and an "enhancement template," the tasks in the project plan are 
automatically generated.  This means incorporating a version of your SDLC into 
ActionProgram Manager or the template.  ActionPortfolio Manager sits in front 
of ActionProgram Manager and includes a proposed project stage-gate approval 
process.

For demonstration purposes, we created a form that tracks versions of 
applications.  The demo starts with a request for an enhancement for a specific 
application and a requested finish date.  The person who gets it assigns it to 
a release.  The request is approved (or not).  If approved, a project record 
along with the pre-defined tasks are automatically generated.  All of the dates 
have been calculated.  You can click on the Gantt chart and see the Gantt 
chart.  You can add this project to a "pool" or "program" (i.e. a group of 
projects) for the release and see the status of all of the bug fixes and 
enhancements, each small project, associated with the release in one Gantt 
chart.  The demo goes on from there to track actuals.  

By the way, you can also assign people to tasks, and see how busy they are at 
that time.  ActionProgram Manager includes a robust resource management 
capability, including charts that show how busy a person is each day.  You can 
put your cursor on a cell in the chart and see the project and tasks that make 
up the time for that day.

This is one version of the demo. Another version incorporates ActionPortfolio 
Manager's proposed project stage-gate approval process.

These applications can be used for all types of projects, so if you want to 
incorporate your SDLC, you can.  One of our users integrated ActionProgram 
Manager with their help desk and change management applications to create a Bug 
Fix application. Another integrated ActionProgram Manager with Asset Management 
to manage scheduled and unscheduled asset outages.  Very cool.

Please call me at 310-230-1722 if you'd like to see a demo or talk about this 
functionality.  Our web site is www.pri-us.com.

Thanks.

Stan.
w. 310-230-1722.

  - Original Message - 
  From: Pierson, Shawn 
  Newsgroups: public.remedy.arsystem.general
  To: arslist@ARSLIST.ORG 
  Sent: Wednesday, March 25, 2009 7:38 AM
  Subject: Re: How many people using change management for SDLC?


  ** 
  We are using Remedy for that, with mixed success.  I had to highly customize 
the approval processes, make some customizations to the Change Management 
application, and change our development processes to fit the app better.

   

  In our situation, BMC had promised us that Change Management was the perfect 
tool for SDLC, and our management believed them and forced us to do it.  There 
was a lot of headaches in getting it to work, but we are using it now.

   

  Personally I would rather use a custom developed application (which we were 
doing in the past successfully) that integrates with Change Management.  I also 
hope that BMC sales have stopped telling people that Change Management is the 
appropriate place for tracking software development work.

   

  Shawn Pierson

   

  From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Covert, Jack
  Sent: Tuesday, March 24, 2009 5:06 PM
  To: arslist@ARSLIST.ORG
  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___

  Private and confidential as detailed here. If you cannot access hyperlink, 
please e-mail sender. __Platinum Sponsor: RMI Solutions ARSlist: "Where the 
Answers Are" html___

__

Re: How many people using change management for SDLC?

2009-03-25 Thread Pierson, Shawn 
We are using Remedy for that, with mixed success.  I had to highly customize 
the approval processes, make some customizations to the Change Management 
application, and change our development processes to fit the app better.

In our situation, BMC had promised us that Change Management was the perfect 
tool for SDLC, and our management believed them and forced us to do it.  There 
was a lot of headaches in getting it to work, but we are using it now.

Personally I would rather use a custom developed application (which we were 
doing in the past successfully) that integrates with Change Management.  I also 
hope that BMC sales have stopped telling people that Change Management is the 
appropriate place for tracking software development work.

Shawn Pierson

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Covert, Jack
Sent: Tuesday, March 24, 2009 5:06 PM
To: arslist@ARSLIST.ORG
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___

Private and confidential as detailed here: 
http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the 
link, please e-mail sender.

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

Re: How many people using change management for SDLC?

2009-03-24 Thread Nicky Madjarov 
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: arslist@ARSLIST.ORG 
  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:arsl...@arslist.org] On Behalf Of Covert, Jack
  Sent: Tuesday, March 24, 2009 4:06 PM
  To: arslist@ARSLIST.ORG
  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

Re: How many people using change management for SDLC?

2009-03-24 Thread Jason 
I agree, Remedy Change Management isn't designed to handle SDLC. The release 
management process at my current contract is mostly external to Remedy. Once 
all of the development, testing, and training are complete. A change request is 
created, all of the documentation is added to it, sent through the approval 
process to approve the implementation of the release, and then reviewed and 
closed by the change manager during the next change review board meeting. 


Jason





From: Lyle Taylor 
To: arslist@ARSLIST.ORG
Sent: Wednesday, March 25, 2009 1:31:15 AM
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:arsl...@arslist.org] On Behalf Of Covert, Jack
Sent: Tuesday, March 24, 2009 4:06 PM
To: arslist@ARSLIST.ORG
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"

Re: How many people using change management for SDLC?

2009-03-24 Thread Lyle Taylor 
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:arsl...@arslist.org] On Behalf Of Covert, Jack
Sent: Tuesday, March 24, 2009 4:06 PM
To: arslist@ARSLIST.ORG
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.



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

How many people using change management for SDLC?

2009-03-24 Thread Covert, Jack 
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


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