Solution Vision

Drive down uncertainty of HOW, refine the WHAT, and learn fast
Identifying and evaluating options and making the right architecture and design choices help to create a competitive edge while maximizing throughput and impact. During Solution Vision, we are iterating between Solution Definition and Solution Design to develop a shared understanding and high-level implementation for the problem defined in the epic. This provides us with a Solution Vision​​​​.

Do we have a clear enough solution that is de-risked enough to work on?

Solution Definition

Purpose

  • ​Define Epics for Initiatives
  • Validate business intent & epic viability

Inputs

  • Portfolio Road Map
  • Desired Business Outcomes Defined
  • Prioritized Opportunities
  • Capability Assessments
  • Target list of Epics based on Strategy/Value
  • Preliminary Business Case
  • Technology Impact Assessment
  • Solution Hypothesis Options
  • Customer Journey Mapping
  • Empathy Map
  • Proto Personas – assumptive personas
  • Epic Problem Statement
  • Desired Outcomes & Success Criteria 
  • Business Risks
  • Mapped Capabilities
  • Market Assumptions​

Activities

  • Validate Epic & Constraints
  • Identify work to address risks and dependencies
  • Product Discovery and Product Validation
  • Story Mapping
  • Refining Business Case​

Definition of Done

  • Product Discovery and Product Validation validated with customers
  • Epic Brief 
    • Epic Problem Statement finalized
    • Epic Acceptance Criteria finalized
    • ​Business Outcomes defined
  • ​Cost Estimate
  • Updated Business Plan – Cost Case
  • Updated RIDA
  • Financial Evaluation
  • Technology Impact Assessment Completed
  • Portfolio Roadmap Updated
  • Portfolio Roadmap Updated
  • Signoff  – Initiative/Epic

RACI

  • ​R – Product Category Team, Product Line Team
  • A – Product Category Team
  • C – Product Manager, SMEs
  • I – Delivery Team

Solution Design

Purpose

  • Develop high-level solutions and validate their viability​

Inputs

  • Customer Journey Map
  • Stakeholder Analysis Diagram
  • Empathy Map
  • User Persona
  • Solution Hypothesis
  • Evaluative Research
  • Feature Map
  • Feature priority, Order of Magnitude (Kano, MoSCoW, etc) 

Activities

  • Complete Feature Brief
  • Perform Technology Assessments
  • Identify solution options
  • Identify work to address risks and dependencies
  • Update Product Backlog

Definition of Done

  • Completed Feature Definitions​
  • Product Backlog Updates
  • High-Level Design
  • UX Design
  • ​Test and Validation Strategy Defined
  • Risk and Dependency Assessment
  • Architecture Impact Assessment 

RACI

  • R – Product Line Team
  • A – Product Architect
  • C – ​Delivery Team, SME’s, Stakeholders, Product Category Team, Test Lead
  • I –  Product Category Team, Stakeholders