Home / BA / Change Request

Change Request

Change Request

In a project, change request generally are come across since the client needs changes or additions to the deliverable which where agreed upon.
The reasons for the change request could be
• Details which were not provided in the requirement gathering stage
• Due to the change in market dynamics
• Any regulatory changes
• Any new of products launched by the client
• Due to change in the preferences, trends etc over a period of time
When a change request (CR) is received, the same needs to be captured in a CR register. This would be captured in a spread sheet or software like PMP. CR register would become main tool to track all the change request resolution
Change Request is handled through
• Feasibility study
• Impact Analysis: Determine the impact of the change to customers, business units, processes, people, systems and documents. Validate the impact of the change with other stakeholders and team members
• Effort & Cost Estimation: Determine the cost of implementation, estimated duration and the number of resources needed to implement the change

Usual Steps followed when a change request arise are
• Record the change the change request
• BA has to analyze whether it is really change request or a defect. Seek approval from Project Manager if CR needs to be further analyzed. BA needs to make stake holders understand impact of the change request or a negative effects due to that particular change
• To check if the CR is a complex one or a minor change. Any Complex change request shall gross impact the scope of the project and lead to increase in project cost and delivery time
• The change request shall be allocated to one or more team members as per the PM
• The team would do the required coding which would be governed by the coding guidelines for the project
• Team would review the changed code to ensure efficiency of execution.
• Once approved would undergo regression testing by testing team to ensure that all functionalities request in the change request are correctly working and no other functionality is effected by the implementation
• Then the change request is closed and recorded in Change Request Register

The CR normally contain the following details
• The CR Id, which could be a serial number
• The CR description
• Date on which the CR is received
• Allocation details for Analysis including date of allocation, completion date, to whom it is allocated
• Allocation details for Approval of CR including date of allocation, completion date, to whom it is allocated
• Allocation details for Resolution of CR including date of allocation, completion date, to whom it is allocated
• Allocation details for peer review including date of allocation, completion date, to whom it is allocated
• Allocation details for regression testing including date of allocation, completion date, to whom it is allocated
• Status – open, closed or under analysis / approval / resolution / peer review / regression testing
• Date on which CR is closed

About S. Parimal Kumar

Check Also

Role of BA in Agile/Srum

Business Analyst should act as he owns the product on behalf of company, and should …

Leave a Reply

Watch Dragon ball super