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.24 Stakeholder Lists and Maps

Guide to Product Ownership Analysis

Purpose

Stakeholder lists and maps assist the POA Practitioner in analyzing stakeholders and their characteristics. This analysis is important in identifying:
  • All possible sources of product requirements,
  • Methods of engagement,
  • The target market for the product.
See section 10.43 of BABOK® Guide v3 for details.
Stakeholder lists and maps are primarily used for identifying and analyzing stakeholders so that the right level of engagement can be achieved.

Traditionally the activity was directed internally to identify the sources of requirements. However, in the context of POA, stakeholder lists and maps can aid in segmentation, targeting, and positioning the product.

Apart from the typical stakeholder matrix, RACI, and onion diagrams, logically grouping customers and deriving customer personas provide better insights into how the product needs to develop and how the right messages can be communicated to customers.

Customer Grouping: Organizes information by identifying commonalities and uniqueness for a set of customers to guide segmentation that influences the design, solution, marketing, and promotional potential, including:
  • Demographic,
  • Geographic,
  • Psychographic, and
  • Behavioural trends.
Customer grouping can be a first step in identifying persona archetypes. Product features can be planned depending on customer groups and the analyzed preferences. A common scheme of customer grouping is:
Customer Grouping.png
POA Domain Stakeholder Lists and Maps and Customer Grouping
Applying Foundational Concepts
  • Product value is realized only when targeted
    customers use the product in a way that provides the desired experience and addresses their unique needs.
  • Correctly identified and analyzed information about the target customers leads to well- defined product scope that is aligned with the business strategy.
Cultivate Customer Intimacy
  • Customer grouping is the first step in identifying different market segments for the product. It helps the POA Practitioner understand if there are unique needs and ways to deliver value to each segment.
    • For example, an insurance company may want to engage customers through different channels if the customer grouping is along generational lines (e.g., Baby Boomers vs. Generation Z) since they will have different expectations.
Engage the Whole Team
  • Identifying customer groups requires multiple iterations and analysis from the entire product team.
    • For example, a tech-savvy member of the product team can provide insights on how certain customer segments will perceive the product.
  • Each member of the product team can provide valuable perspectives that lead to a better product.
Make an Impact
  • A product will generate the right impact when the customer derives value consistently or receives an unexpected but positive experience from the product, which the customer may not have thought about.
  • Customer grouping allows the team to assess multiple scenarios and uncover both explicit and latent needs that help increase impact for the targeted customer group.
Deliver Often
  • The primary customer groups seldom require a
    complete overhaul, but their characteristics and traits are reviewed often.
  • The persona representing a customer group may go through various updates to reflect a change in that persona's perception of the evolving product.
  • If the product scope evolves and is different from the original goals, it may result in a change of customer groups. The Practitioner needs to internalize the changes for more effective product decisions.
Learn Fast
  • Stakeholder analysis, from an external perspective, reveals how to address specific customer needs.
  • It can be used to compare, prioritize, and deploy features, as well as learn from feedback.
Obsess About Value
  • Customer grouping and analysis may reveal
    competing priorities and needs between different customer groups.
  • The team needs to decide and sequence PBIs in a way that provides the best value to customers.