o Change Management
o Sources of Software Change
o Objective of Change Management in SE
o SW Change Management Procedures
o Change Management Roles
o Change Management Process
o Tips to Make it seamless
Change management is the discipline that guides how we :
oSupport individuals to successfully adopt change
oIn order to drive organizational success and outcomes.
oBy assuring that all proposed changes are evaluated
oBy prioritizing changes
oBy requiring that all changes are thoroughly tested
oA back-out plan
oBy ensuring that the configuration management system is updated to reflect the effect of any
Working with changing requirements is like
trying to shoot a moving target!
oNo matter where you are in the system life cycle, the system will change
oThe desire to change it will persist throughout the life cycle
oThe services should be stable, reliable, and predictable.
oThe services should be able to change rapidly to meet evolving business requirements.
Source of Change in SE
New customer needs
New market conditions
constraints The performance or
Errors must be repaired
Objective of Change Management in SE
oTo maximize speed-to-competence at minimized
cost – this is the basic conundrum faced by
oTo effectively control risk – in people as well as
o To recognize resistance to formal change
management and to use activities within change
management specifically targeted to overcome
that resistance. This is a recursive approach which
is almost unique across the portfolio of everyday
Change Management Roles
Recognizes and identifies the need for changeChange Initiator
Risk and impact, implementation plan, progressChange Coordinator
Prioritizing, evaluating, outcomeChange Manager
Schedule a meeting with ,how to proceed
Approve or RejectApprover
Change Management Process
Creating a Request
Assessing a Request
Testing the Change
Creating a Change
Closing the Process
1 Creating a Request for Change
Incidents that necessitate the change
Description of how the change would be implemented
The impact that the change would have on all associated systems
A risk assessment
Contact information for everyone involved in the change
An outline of who will need to approve the request
A backup plan to follow in case the change is not successful
It provides accurate understanding of the implications of a proposed change.
Which helps the team make informed business decisions about which proposals to approve.
1- Understand the possible implications of making the change.
2- Identify all the files, models, and documents.
3- Identify the tasks and estimation of efforts.
Checklist of possible implications of a proposed change.
Checklist of possible software elements affected by a proposed change.
Estimating effort for a requirement change
Identify the sequence in which the tasks must be performed.
Determine whether the change is on the project’s critical path
Estimate the impact on project’s schedule and cost.
Evaluate the change’s priority by estimating the relative benefit, penalty, cost, and technical
risk compared to other discretionary requirements.
Report the impact analysis results
In most cases, this procedure shouldn’t take more than a couple of hours
Evaluate the request based on its priority , impact analysis
If requests relate to problems that have already been addressed.
Determine who would be responsible for fulfilling the request.
Implementers’ ability to dedicate time to making the change.
Resources that are needed to complete the change.
A timeline for implementation.
Test will demonstrate the procedure to be followed in case the change request is approved.
Testing the change gives you the opportunity to work out any problems in the procedures that
you have developed .
5 Creating a Change Proposal
Outlines the type of change.
The priority associated with a change request
The outcomes that could occur if the change is not made
6 Implementing Changes
Implementing a change is not a simple process.
Once the change has been made, tests must be done.
If the change is not successful , backup plan.
7 Reviewing Change Performance
Understand whether your change procedures are working as expected.
Determine the accuracy of estimates that were made before a request was fulfilled.
Reviewing change performance gives you the opportunity to fine-tune your change management
process for better results in the future
8 Closing the Process
You must be sure that the entire process has been documented in a database that all
stakeholders can access .
Thank You !
Hiba M. Ghannam
We do not need magic to change the world, we carry all the power we need inside ourselves already: we have the power
to imagine better.