Requirement change management process

Requirements vary and changes in requirements can occur at any time during the life of a project.  As far as the requirements in the lifecycle are removed, the more impact there is on the project.  Rather than seeking what that changes will not happen, or expecting that any kind of initial requirements will be "so good" that no changes will be required, it is better that a project manager is ready to handle the requests for change  .

  Project cost, schedule and quality.  The requirement change can be 40% of the total cost [22].  Due to the potentially large impact of requirement changes on the project, a different process is often employed to deal with them.

  The change management process defines a set of activities to be done when there are changes in some new requirements or changes in existing requirements.  This process can be used to change the requirement, major bug fixes for any major changes such as design changes or deployment in one system.  The following steps are in the change management process.

  • Log changes

  • Impact analysis on work products

  • Estimated impact on efforts and schedule

  • Review impact with relevant stakeholders

  • Work Work Products

  A change is initiated by a change request.  A change request log is maintained to track changes requests.  Each entry in the log includes a change request number, a brief description of the change, the effect of the change, the status of the change request, and the key dates.  The effect of a change request is done by analyzing the effect analysis.

  Impact analysis involves identifying work products and configuration items that need to be changed and each has to evaluate the amount of change;  Reconsider the risks of projects by re-thinking on the risk management plan;  And evaluate the overall effect of the changes for effort and schedule estimates.  Once a change is reviewed and approved, it is applied, i.e., all items are changed.  The implementation of the change request can be controlled by the actual tracking configuration management process, which has been discussed above.  One danger of necessity change is that even though each change is not big in itself, but the cumulative effect of changes on the life of the project is huge.

Software Configuration Management Process




from Technology development http://bit.ly/2VoqeSj

Comments

Popular posts from this blog

New best story on Hacker News: Ask HN: What startup/technology is on your 'to watch' list?

New best story on Hacker News: Ask HN: What's the most valuable thing you can learn in an hour?