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.22 Risk Analysis and Management

Guide to Product Ownership Analysis

Purpose

Risk Analysis and Management identifies areas of uncertainty that could negatively affect value and analyzes and evaluates those uncertainties. It also develops and manages ways of dealing with the risks.

See section 10.38 of BABOK® Guide V3 for details.
In the context of product ownership analysis, risk analysis and management are a continuous process for a longer duration than a time-boxed project. The Product related risks often fold in the components of market and business environment risks that are long term. Careful identification and mitigation are required to address product risks. Risk categories, from a product point of view, include:
  • Delivery and Execution Risk: Relates to risks involved in the development of the product involving cost, schedule, resources, as well as the risk of developing unintended features that do not create value.
  • Market Risk: Relates to the risks where the product does not generate the right outcomes for the business or customers.
While practitioners are familiar with delivery and execution risks, the market risks are mitigated by:
  • Additional customer research (e.g., ethnography),
  • Right-sized product launches (e.g., MVP),
  • Phased rollouts (e.g., Alpha and beta launches),
  • The sequence in which chunks of features are delivered,
  • Customer acceptance of features (e.g., A/B tests),
  • Functional Research (e.g., Spikes, PoC), and
  • Metrics and Key Performance Indicators (KPIs).
POA Domain Risk Analysis:
Applying Foundational Concepts
  • Risk analysis and mitigation is inherent to product development effort and starts with the identification of customer needs. This requires analysis of organizational capabilities.
  • Challenges to organizational capabilities may come from team competencies, including:
    • Delivery capabilities, and
    • Organizational support mechanisms.
  • In this domain, risk analysis and management are applied to uncover and plan for any systemic challenges to product development.
Cultivate Customer Intimacy
  • The market risk component can be mitigated by
    a deeper understanding of customers, and whether the product is fulfilling customer needs.
  • Risk analysis and management requires Practitioners to apply their customer knowledge while identifying any risks and applying risk mitigation approaches.
Engage the Whole Team
  • Identification of risk and the associated management practices need to be discovered as a team.
  • The POA Practitioner may suggest, and bring in, the customer perspective for risk identification. However, the entire team needs to highlight any delivery and execution-related risks.
Make an Impact
  • Risk management techniques need to be impactful so that the business and customer outcomes are not severely affected.
  • In the life of the product, there are product decisions that may make or break the product and cause irreversible consequences. Such decisions must be weighed with detailed analysis and an appropriate mitigation plan.
Deliver Often
  • Risk analysis and management must be conducted often to keep the risk register current.
  • The product team conducts the risk analysis and management exercise at least once an iteration to reflect the current state.
Learn Fast
  • Unmitigated risks are the primary cause of failed products.
  • The product team must conduct the risk analysis and management exercise to uncover all risks that may potentially cause issues.
  • Fast customer feedback, appropriate metrics, and analyzing KPIs help the team better manage risks.
Obsess About Value
  • Even if delivery and execution risks are carefully managed, the product may still not be successful if it does not generate the desired business outcomes or provide enough customer value.
  • Market risks are considered in detail when risks are analyzed in a product context.