_edited.jpg)
Purpose: Evaluate proposed changes.
Description:
-
Analyze new needs and solutions.
-
Ensure alignment and assess impact.
-
Trace changes back to needs.
Considerations:
-
Strategy, value, time, risks.
Outcome:
-
Supports decision making.
Inputs
-
Proposed Change: Strategy, stakeholders, regulations.
-
Requirements: Assessed for impact.
-
Designs: Evaluated for change impact.
Elements
-
.1 Assessment Formality:
-
Based on data, significance, governance.
-
Predictive: Formal; adaptive: less.
-
-
.2 Impact Analysis:
-
Evaluates changes' effects.
-
Factors: Benefit, Cost, Impact, Schedule, Urgency.
-
-
.3 Impact Resolution:
-
Stakeholders decide.
-
Document and communicate impacts.
-
Guidelines & Tools:
-
Change Strategy: Sets direction and identifies key components.
-
Domain Knowledge: Uses expertise for assessment.
-
Governance Approach: Guides decision-making and roles.
-
Legal/Regulatory Info: Considers laws impacting changes.
-
Requirements Architecture: Analyzes relationships for impacts.
-
Solution Scope: Considers solution boundaries.
Techniques:
-
Business Cases: Justifies changes.
-
Business Rules Analysis: Assesses policy changes.
-
Decision Analysis: Facilitates assessment.
-
Document Analysis: Examines documents for impact.
-
Estimation: Determines change size.
-
Financial Analysis: Estimates financial impacts.
-
Interface Analysis: Identifies affected interfaces.
-
Interviews: Understands stakeholder views.
-
Item Tracking: Tracks issues.
-
Risk Analysis: Assesses change risks.
-
Workshops: Group understanding.
Stakeholders:
-
Customer: Value feedback.
-
Expert: Organizational insight.
-
End User: Activity impact.
-
Support: Operational assistance.
-
Manager: Project adjustments.
-
Regulator: Compliance check.
-
Sponsor: Scope guidance.
-
Tester: Impact evaluation.
Outputs:
-
Requirements Assessment: Change recommendation.
-
Design Assessment: Design change recommendation.
