I am a member of the Quality Services Team in our IT department. We are wanting to develop a document that explains a process for doing an Impact Analysis. We expected to find a great deal of information about the process of doing an Impact Analysis on the Internet, but this has not been the case. Does anyone on these forums have any specific information that you could share.
(e-x) Assume that you want to carry out an impact analysis for the Change request from the Client on the ongoing project which is in the devleopment phase.In this case you can carry out an impact analysis on the change request received with the concerned team(Say Delivery Manager,Program Manager ,Project Manager etc..) and then to cateogorise the change as whether it's a major(will have major impact on your earlier agreed schedule and time lines) or minor(not much schedule variation).
If the change request is a major then it need to taken up with senior management/Client for getting an approval to re estimate the effort and cost.If the change is minor then this can be taken up with minor alterations on effort and schedule.
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 a shambles.
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?