Change Impact Analysis

Objectively understand the implications of change requests to evaluate proposals up-front and contain threats.

Conducting impact analysis up-front increases your success rates in implementing changes. Impact analysis is highly beneficial in that it identifies the potential scope and consequences of an initiating change, enabling you to produce a realistic data-based estimate of what is involved to accomplish the change. With impact analysis, scheduling, budget, and risk will be known quantities prior to the decision to implement changes, rather than a surprise afterwards.

While Vivid Trace doesn't have an explicit impact analysis feature, it does provide a key mechanism integral to discovering the scope of proposed changes: Traceability Impact Analysis. All that is required is a body of project artifacts in JIRA, cross-linked and within traceable range of Vivid Trace.

  • Automatic Discovery: Manually determining what and who is affected by a change is time consuming and error-prone. Vivid Trace automates the bulk of the exploratory effort instantly and accurately.
  • Change management: Understanding the impact of a change enables teams to better evaluate and respond to change requests while gaining control over the scope of change.
  • Compliance: Frequently employed in safety-critical and mission-critical projects in industries such as healthcare, aerospace, and automotive, and by high performing teams adhering to CMMI and ISO 15504 SPICE general practices, to ensure that the changed deliverables can still satisfy compliance requirements.
  • Conflicts and risks: Prevent scheduling conflicts and curtail risk when it is less expensive to do so.
  • Customer satisfaction: Enhance your ability to manage customer expectations, deliver on approved change requests, and maintain customer loyalty and satisfaction.
  • Determine Scope: Analyse relations between requirements and specifications, code and other design elements, and tests to determine the scope of the proposed change.
  • Domino effects: Flush out unanticipated snags that might be hiding behind even simple change requests.
  • Implementation: Identify associated code and other design elements that need to be created, modified, and removed, including files, models, and documents.
  • Project and budget oversight: Develop an objective understanding of the implications of changes and to produce reliable estimates, allowing you to make informed business decisions about which proposals to approve and to contain threats to your budget and schedule.
  • Requirements and specifications: As a core aspect of requirements management, impact analysis helps you identify the requirements, specifications, customer feedback, and marketing inputs that might need revisiting.
  • Scale Return on Investment: Impact analysis pays dividends in proportion to the size of the change and the project: As larger projects escape memorization by team members, up-front impact analysis pays off in developing reliable estimates and reducing risk.
  • Testing: Identify the specific set of requirements, features, and story acceptance criteria that need to be retested.


Operational Stability