New Page 1

If you want to buy the project management book mail [email protected] for more details or call any of our book shops MUMBAI-22078296/97/022-22070989, KOLKATA-22826518/19 HYDERABAD-24756967,24756400,BANGALORE-25587923, 25584641,AHMEDABAD-26421611,BHATINA(PUNJAB)-2237387,CHENNAI-28410796,28550491,DELHI/NEWDELHI-23254990/91,23325760,26415092,24691288.If you want to write to the author directly email at [email protected]

Home

(B) How did you manage change request in your project?

Note: - In all IT companies Change request is termed as CR. So do not get stunned by the word CR during project management interviews.

Below diagram 'CR procedure' shows in general how change request is handled. Let us try to understand the same in a detailed manner:-

Step 1:- The end user or the customer raises a change request.

Step 2:- The CR is analyzed by a group of people who understand the business. If they think its worth considering they give an approval saying please go ahead with a detail impact analysis in terms of changes and cost or else it’s either deferred or rejected. Many times end users raise change request which does not add much value addition to the business so it’s essential that it should once go through a formal review process.

Step 3:- Technical IT team does an impact analysis and also estimates how much time it will take to implement the CR.

Step 4:- Again a review process is done from the angle of cost and impact. Some times if the cost is too high it’s very much possible that the CR can be rejected or deferred.

Step 5:- If approved the technical team does the execution and goes ahead with the testing part. There can be two level of testing one is internally (internal testing) and other is from the end customer testing (Acceptance testing). If the acceptance testing goes fine its time to close the CR.

Figure: - CR procedure

Home

Hosted by www.Geocities.ws