Changes Management  Change Management is the process of developing a planned approach to change in an organization.  The...
Types of Changes  Scope changes (modify product documentation and      often project plan):             Requirements cha...
Evaluating Change Requests  All change requests are documented:      Emergency changes are documented after the fact.   ...
Change Management ProcessControl        Start        Detection        Diagnosis        Repair        Recovery       ...
First Level Approval                   of Change Requests  Usually provided by the project manager or a senior      team ...
Second Level Approval of Change              Requests  Usually provided by a Change Control Board (CCB):      Do the exp...
Change Control Board  A formally constituted group responsible for   approving or rejecting change requests.  Powers and...
Thank you6/20/2010   Author: Dr. Tomas U. Ganiron Jr   8
Upcoming SlideShare
Loading in …5
×

Change Management

559 views
489 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
559
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Change Management

  1. 1. Changes Management  Change Management is the process of developing a planned approach to change in an organization.  The objective is to maximize the collective benefits for all people involved in the change and minimize the risk of failure of implementing the change.  It is a procedure to ensure that proposed changes are merited and will not adversely affect other elements of the plan or interdependent plans.  Change must be realistic, achievable and measurable.6/20/2010 Author: Dr. Tomas U. Ganiron Jr 1
  2. 2. Types of Changes  Scope changes (modify product documentation and often project plan):  Requirements changes  Clarifications  Site emergencies  Work changes (modify project plan):  Resource changes  Modified approach  Corrective action6/20/2010 Author: Dr. Tomas U. Ganiron Jr 2
  3. 3. Evaluating Change Requests  All change requests are documented:  Emergency changes are documented after the fact.  Non-emergencies are documented before being considered.  Change requests should be documented by the requestor6/20/2010 Author: Dr. Tomas U. Ganiron Jr 3
  4. 4. Change Management ProcessControl  Start  Detection  Diagnosis  Repair  Recovery  Restoration6/20/2010 Author: Dr. Tomas U. Ganiron Jr 4
  5. 5. First Level Approval of Change Requests  Usually provided by the project manager or a senior team member:  Are the expected benefits significant enough to merit further investigation?  Implications:  Must have budget for this work!  Benefits may include cost avoidance  Organizational politics must be considered6/20/2010 Author: Dr. Tomas U. Ganiron Jr 5
  6. 6. Second Level Approval of Change Requests  Usually provided by a Change Control Board (CCB):  Do the expected benefits outweigh any negative impacts?  Implications:  Must have budget for this work!  Benefits may include cost avoidance  Organizational politics must be considered6/20/2010 Author: Dr. Tomas U. Ganiron Jr 6
  7. 7. Change Control Board  A formally constituted group responsible for approving or rejecting change requests.  Powers and responsibilities should be well-defined and agreed upon in advance.  On larger, more complex projects, there may be multiple CCBs.6/20/2010 Author: Dr. Tomas U. Ganiron Jr 7
  8. 8. Thank you6/20/2010 Author: Dr. Tomas U. Ganiron Jr 8

×