7 Rs of Change

Management
TEAM-3
Who raised the change?

Identify authority who has done the change and restrict change by
authorisation
Centrally system of records can be maintained to track the
change
Useful during audits
What is the reason for the change?

If this change is worth the risk to benefit to the business

Question asked and change must be assessed on agreed upon
portfolio
Can help prioritize changes and manage IT resources
What return is required from the
change?
Understand the return of the change specially financial
Objective returns must be evaluated to measure the financial
impact of the change
Help in better priortizaton of the change and more focus for it
What are the risks involved in the
change?
What type of risks are the avoidable or just have to bear
Identify the impact of the risk and finding the solution for the worst
Also consider the risk of not making the change
Asssess the severity of risk and evaluate the best and worst tha could
happen
What resources are required to
deliver the change?
People and IT assets required for the change
What skill are needed ? Are the present in current workforce.
What IT infra is needed.
What would be the time delay in such preparation
How would it impact the other projects.
 Who is responsible for the build,
test, and implement portion of the
change?
Traceable, enforceable and actionable responsibilty to build, test
and implement change
Should be in compliance and appropriate in auditing requirement
The change should be manageable from request to delivery
What is the relationship between
this change and other changes?
Find the relationship between other changes for minimum
downtime of the functions
Change scheduling and sequencing can help maintain proper
discipline.
change impact analysis and relationship mapping from an
integrated configuration management database helps in
monitoring and maintain change relationship.
THANK YOU
QUESTION AND FEEDBACK!!!