Project Change Management

Related Articles

What are the elicitation techniques using in a project?

9 hours ago

Business case document (Banking CRM System)

1 day ago

CRM for Banking Secter

1 day ago

Purpose:

The purpose of this blog to provide the overview on the Project Change Management process.

Objectives:

To improve the business value of the Organization, anytime CR will be identified by anyone and managed by the Project team.

The primary objectives of change management are>

1. Log the Change request details in CRF & CID Log and communicate the team
2. Evaluate the need of CR and provide the decision.
3. Follow the required steps to implement the CR
4. Track the CR in all phases

Acronyms used:

CR  – Change Request

CRF – Change Request Form

CCB – Change Control Board

CID – Change, Issues, Decision

CR Initiation:

CR initiator can be anyone from stakeholders can propose the change request during the execution of the project based on reviewing the application features or market trends or need of new features.

CR initiator has to provide the below information to record in CRF and distributes the form to the Project Manager/Project Sponsor.

Change Request Form (CRF) >

• Description of the change
• Description of the change
• Reasons
• Benefits
• Impacts
• Any supporting documentation

Process:

1. CR initiator has to provide the information of new change to record into CRF.
2. Project manager logs the CR details in CID Log.
3. Project manager reviews the CR and collects more info from the CR Initiator if need
4. Project manger distributes the CR details to CCB, Project Sponsor and all stakeholders.
5. CCB team gather the details below from the Project team
   1. benefit from the new change
   2. risk by the new change
   3. impact analysis ( budget, time, scope change, resources, quality)

 

6. CCB team discuss with the CR initiator to know the insights and need of the new CR
7. CCB team evaluates the new CR and provides the decision whether to implement now or later or never.
8. If new CR is approved, Project Manager inform the team to plan the new CR to implement in the project
9. Project manager updates the budget plan, resources plan and release plan accordingly. am
10. Project sponsor determine the priority of the CR and Project manager plans the release.
11. If new CR is rejected, all stakeholders will be informed with the rejection notes.
12. Project manager tracks the CR using CID log

Benefits:

1. Organization gets business value
2. Organization keep provides valuable features to the customers
3. CR may simplify the application and make it more user friendly

 Risks:

1. Project gets fail if impact analysis is not done properly
2. Organization may lose business if the required CRs are not implemented in time.
3. Technical architect, Dev and QA teams should be aware of the CR in advance to avoid the major design changes later

Conclusion:

Project team must evaluate the need of the CR with the help of impact analysis and every team member should be aware of the CR in advance. CRs should be tracked very carefully in all stages and need more attention in QA process.