change management slides

7/27/2019 Change Management Slides

http://slidepdf.com/reader/full/change-management-slides 1/36

FEL JUN PALAWAN



What is Change Management???



change management

is the process of requesting, determining attainability, planning, implementing,

and evaluating of changes to a system.



Software

ConfigurationManagement(SCM)

for software



Hardware

ConfigurationManagement(HCM)

for hardware



supporting the processing of changes

enabling traceability of changes

goals of change management



why need for change?



Lehman’s laws of software evolution: the law of continuing change

(i.e. systems that are used must change or automatically become less useful)



satisfy "customer needs"



increasing and worldwide competition



technological advances



bug fixes



problems on change



Lehman’s laws of software evolution: the law of increasing complexity

(i.e. through changes the structure of a system becomes ever more complex

and more resources are needed to simplify it).



ruin the system (eg. scope creep)



mixing up the change administration (eg. multiple developers)



more funds and work is needed



the change management roles



Project manager



Change committee



Change builder



the change management activity



Identify potential change

•Require new functionality•Encounter problem

•Request change



Analyze change request

•Determine technical feasibility•Determine costs and benefits



Evaluate change



Plan change

•Analyze change impact

•Create planning



Implement change

•Execute change•Propagate change

•Test change

•Update documentation

•Release change



Review and close change

•Verify change•Close change



change request



is a document containing a call for an adjustment of a system

is declarative, i.e. it states what needs to be accomplished, but leaves out

how the change should be carried out



• problem reports that identify bugs that must be fixed, which forms themost common source

• system enhancement requests from users

• events in the development of other systems

• changes in underlying structure and or standards (e.g. in softwaredevelopment this could be a new operating system)

• demands from senior management

• unclear understanding of the goals and the objectives of the project.

sources of change request



is a formal process used to ensure that changes to a product or system are

introduced in a controlled and coordinated manner.

it reduces the possibility that unnecessary changes will be introduced to a

system without forethought, introducing faults into the system or undoingchanges made by other users of software.

change control



minimal disruption to services

reduction in back-out activities

cost-effective utilization of resources involved in implementing change

goals of change control



END



http://en.wikipedia.org/wiki/Change_control

http://en.wikipedia.org/wiki/Change_request http://en.wikipedia.org/wiki/Change_management_(engineering)

Sources

http://www.teamtechnology.co.uk/changemanagement.html

http://searchcio-midmarket.techtarget.com/definition/change-management http://www.adb.org/Documents/Information/Knowledge-Solutions/fast-effective-change-management.pdf

http://changingminds.org/disciplines/change_management/change_management.htm

http://en.wikipedia.org/wiki/Lehman%27s_laws_of_software_evolution

http://en.wikipedia.org/wiki/Software_configuration_management


http://en.wikipedia.org/wiki/Change_request

http://en.wikipedia.org/wiki/Change_management_(engineering)


http://searchcio-midmarket.techtarget.com/definition/change-management

http://www.adb.org/Documents/Information/Knowledge-Solutions/fast-effective-change-management.pdf




http://en.wikipedia.org/wiki/Lehman's_laws_of_software_evolution



http://en.wikipedia.org/wiki/Lehman's_laws_of_software_evolution


















http://en.wikipedia.org/wiki/Change_management_(engineering)

http://en.wikipedia.org/wiki/Change_request
