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

5. The POA Framework

5.7 Obsess About Value

Guide to Product Ownership Analysis

Framework - Obsess about Value.pngProduct development and innovation are usually hard and complex. When new products are built, with each iteration the team must consider:
  • New features,
  • Scale, and
  • New challenges.
Innovation demands the product teams try new things. It is often a daunting task for the Product Owners to figure out exactly what needs to go into the product. Although there is no instruction manual to understand what the product should be like, the best place to start is knowing what the customer values.

Value from the customer perspective is usually a comparison between the benefits of a product and the cost. The cost can be the actual price, or reduction in effort, by using the product. The industry has spent considerable time and energy in managing the price, and less time understanding the value. The value can be difficult to pin down, and it evolves as expectations change over time.

Value is: "The worth, importance, or usefulness of something to a stakeholder within a context. Value can be seen as potential or realized returns, gains, and improvements. It is also possible to have a decrease in value in the form of losses, risks, and costs. Value can be tangible or intangible." - BABOK® Guide.

The definition of value is that it is context-driven and has an impact on stakeholders who can either be customers or organizations. Whether the value is tangible (cost-saving or revenue), or intangibles (reducing complexity or providing delight), it is difficult to define what is valuable. Customers and businesses are good at making choices rather than defining what they need upfront. Customers can choose an option that is compared to be more valuable. Product teams must be cognizant of two critical steps throughout the life of a product:
  1. Evolve the product: Provide valuable options to the customer by obtaining insights from the customers and other stakeholders quickly. Applying the learnings in the best way possible, so that the most valuable choices are integrated into the product.
  2. Optimize value delivery: Optimize the path taken for product development, that is quick to value, by optimizing processes involved in:
    • Product development,
    • Assessing the capabilities of the product team, and
    • Use of technology.