Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

6. POA Techniques

6.29 Visioning

Guide to Product Ownership Analysis

Purpose

Visioning is concisely worded to determine the desired outcome for an initiative.

See section 7.24 of Agile Extension V2 for details.
In the context of POA, visioning is used as a technique to derive a cohesive, integrated, and aspirational view that captures the essence of why the product should exist. It describes the value provided (value proposition) to a specific group of stakeholders (target market) that satisfy their unmet needs.
POA Domain Visioning
Applying Foundational Concepts
  • A team exercise can be conducted with relevant stakeholders to formulate a guiding statement aligned with the organization's vision and product vision.
  • Shared often and used as a tool to develop shared understanding for the product team.
  • Visioning exercises are open-ended discussions.
  • The exercise must be undertaken often so that product vision remains aligned to the direction a product is taking.
    • For example, products after the initial launch usually need to be re-evaluated to determine if the product is still solving the right problem. The product visioning exercise must be conducted every time a product pivots.
Cultivate Customer Intimacy
  • Product vision is the synthesis of customer needs.
  • A clear understanding of vision is critical to the product team, and customers often strongly relate to a well-crafted product vision.
  • An emotional connection is built with the product if customers are influenced by it, which aids in building the right brand.
Engage the Whole Team
  • Visioning exercises cannot be performed in isolation.
  • The vision represents the enterprise and product team's perspective about the problem the product is solving.
  • The team needs to be motivated by the vision and should have their ideas heard when formulating the product vision.
Make an Impact
  • Product vision communicates the purpose of the product now and in the future.
  • The product vision is about making a statement that has far-reaching consequences and creates a lasting impact.
Deliver Often
  • Delivering the product often is a way to test the product against the vision that was originally crafted. This philosophy is consistent with good agile practice so a product can take the most efficient path to deliver against the product vision.
  • Visioning does not have a significant role in ensuring timely deliveries and is not required to be conducted as often.
Learn Fast
  • Most of the strategic, market and delivery assessments are conducted with the product vision as the centre of focus.
  • Learning from key stakeholders and customers can be used to improve product-market fit. The product vision can be updated as needed to align with and drive appropriate product changes.
Obsess About Value
  • The product vision is the guiding statement that drives the whole product team to obsess about what value needs to be delivered so that the product vision can be fulfilled.
  • It can also be used to assess the value delivered through each product increment and identify changes that are needed.