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.2 Business Cases

Guide to Product Ownership Analysis

Purpose

A business case provides justification for a course of action, based on the benefits to be realized by using the proposed solution, compared to the cost, effort, and other considerations to acquire and live with that solution.

See section 10.7 of BABOK® Guide V3 for details.
In the context of product ownership analysis, business cases provide value and benefits that are realized continuously over a long period, as opposed to a project context which is a one-time event. Although the business cases are prepared by the product management function, the POA Practitioner provides significant input in the preparation of a business case regarding:
  • The roadmap,
  • The sequence of features, and
  • The customer perspective.
A business case often takes the form of a product plan that is more comprehensive and may include:
  • Product vision,
  • Product strategies:
    • Strategy assessment of needs,
    • Target market,
    • Competitive assessments, and
    • Industry analysis.
  • Business value and benefits (e.g., value propositions),
  • Financial assessments (e.g., ROI mapped to product lifecycle),
  • Key strategy and product metrics,
  • Product roadmap,
  • Business model,
  • Go-to market strategies, and
  • Risk, constraints, and assumptions, etc.
POA Domain Business Cases
Applying Foundational Concepts
  • Created upfront and iteratively developed into a
    fully developed product plan.
  • Without the right foundational thinking that explores strategic product alignment, team capabilities, and the organization’s resources, it will be difficult to position product build activities for success.
Cultivate Customer Intimacy
  • Created from the enterprise viewpoint.
  • Most organizations recognize that customer value is a critical driver for business success. The business case for a product must be created with a customer lens.
Engage the Whole Team
  • Requires contribution from many cross-functional teams, including:
    • Product management,
    • Product Ownership,
    • Marketing, and
    • Technology functions.
  • It requires significant collaboration and engagement skills for a POA Practitioner to synchronize with different teams to create a business case.
Make an Impact
  • It is the first step towards creating a significant
    impact within internal stakeholders of an organization.

  • Without the right articulation of value, a business case is likely to fail, especially when a product is not available for demonstration to decision-makers.
Deliver Often
  • A product plan that evolved from a business
    case is a live artefact that drives product development. It is kept current to reflect the prevailing product and market situations.
Learn Fast
  • A tool for:
    • Securing investment,
    • Learning about market conditions, and
    • Assessing whether the value and the timing of product build activities are justified.
  • The analysis required to create a comprehensive business case unlocks multiple areas of learning and feedback that is used to evolve the product offering.
Obsess About Value
  • The team must be aware of the organization’s
    value to create an effective business case.

  • The business case for products is no longer unidirectional justification for revenue, cost, or schedule. It encompasses different value metrics. For example:
    • A product strategy may involve rapid onboarding of users, which sacrifices funds for getting better customer lifetime value.