Impact analysis
From Wikipedia, the free encyclopedia
 |
This article may require cleanup to meet Wikipedia's quality standards. Please improve this article if you can. (July 2007) |
 |
This article does not cite any references or sources. (July 2007) Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed. |
Impact Analysis is a brainstorming technique that helps users think through the full impacts of a proposed change. As such, it is an essential part of the evaluation process for major decisions.
More than this, it gives the ability to spot problems before they arise, so that companies can develop contingency plans to handle issues smoothly. This can make the difference between well-controlled and seemingly-effortless project management, and an implementation that is seen by your boss, team, clients and peers as total mess.
Impact Analysis Checklist for Requirements Changes
Implications of the Proposed Change
Identify any existing requirements in the baseline that conflict with the proposed change. Identify any other pending requirement changes that conflict with the proposed change. What are the consequences of not making the change? What are possible adverse side effects or other risks of making the proposed change? Will the proposed change adversely affect performance requirements or other quality attributes? Will the change affect any system component that affects critical properties such as safety and security, or involve a product change that triggers recertification of any kind? Is the proposed change feasible within known technical constraints and current staff skills? Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments? Must any tools be acquired to implement and test the change? How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan? Will prototyping or other user input be required to verify the proposed change? How much effort that has already been invested in the project will be lost if this change is accepted? Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees? Will the change affect any marketing, manufacturing, training, or customer support plans?
