Requirements Engineering and Management for Software Development Projects by Murali Chemuturi

Author:Murali Chemuturi
Language: eng
Format: epub
Publisher: Springer New York, New York, NY

c.If the construction of the component is completed but not implementing the current CR would render the component a bottleneck for other components, it would be implemented immediately.

Once the analysis and strategy for CR implementation are decided, the CR would be implemented in line with the analysis and implementation strategy decided by the CCB or the PM.

Changes can cause disruption to the flow of project execution regardless of whether it begins as a smooth flow or a chaotic path. When a CR is received, in many cases, it would impact an artifact that is already completed. This causes severe impact. In rare circumstances the impact would be on an artifact that is yet to be completed. If the impact is only to the current artifact, the impact will tend to be less severe. Regardless of the scenario, artifacts like requirement documents, design documents and others will have to be reviewed and may have to be revised which will impact the project execution flow.

The phase of development at which the CR is received also determines the severity of the impact. For example, a CR is received just after the requirements phase will tend to cause the least severe impact as compared to a CR for the same item received when the project is in the system testing phase.

Table 8.2 summarizes the severity of the impact of CRs on project execution flow. But one thing is certain; CR does impacts project execution flow.Table 8.2Severity of the impact caused by CRs

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.