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.21 Reviews

Guide to Product Ownership Analysis

Purpose

Reviews are used to demonstrate and inspect an increment of the solution with stakeholders to elicit feedback to determine if the solution being developed aligns with the need.

See section 7.15 of Agile Extension V2 and section 10.37 of BABOK® V3 for details.
In the context of product ownership analysis, practitioners can use reviews to verify work products or working solutions and elicit feedback to learn from stakeholders. Reviewing a working product increment is more relatable to stakeholders than evaluating the PBIs, user stories, or other product documentation. It also elicits better feedback than other forms of reviews.

Outcomes from reviews include:
  • A shared understanding of the evolving product,
  • Validation of product alignment with customer needs,
  • Identification of defects or possible resolutions to the defects, and
  • Determination of next steps or changes in priorities.
Reviews are equally important when looking at smaller incremental work, such as a user story or a small number of user stories. The work needs to be understood by key stakeholders, agreed upon, and delivered. The Developer, QA and the POA Practitioner form a triad. These key stakeholders evaluate the progress of the set of stories from planning to delivery. Such reviews are often referred to as the Three Amigos review.
POA Domain Reviews:
Applying Foundational Concepts
  • Reviewing work products involves assessing:
    • Product Strategies,
    • Roadmaps,
    • Team structure, and
    • Product concepts.
  • Rather than focusing on deciding whether a work product is right or wrong, reviews invite discussions and feedback.
Cultivate Customer Intimacy
  • Although reviews are often internal to the
    product team (that might not have customer representation), POA Practitioners present the customer perspective.
  • Additionally, customer reviews can be conducted to discover the nuances of customer needs that result in more aligned products.
Engage the Whole Team
  • Due to lack of time, reviews are often conducted with a small number of team members. However, reviews are meant to elicit feedback from the entire team.
  • POA Practitioners must ensure that the whole team is represented, and all the key stakeholders are present in a review meeting. The “three amigos” can represent various perspectives within the team and fulfill the role of key stakeholders.
Make an Impact
  • Reviews often accompany a demonstration of
    the working product that helps garner more attention and feedback from the participants.
Deliver Often
  • Reviews must be conducted, at least for each
    iteration of product increment, so that feedback from the team can be actioned through managing the product backlog.
  • It produces better alignment and de-risks the product from major surprises when released to the customer.
Learn Fast
  • Reviews ensure that learning from a delivered
    work product is immediate by eliciting first- level feedback from the team since they have the best understanding of the product.
  • The customer perspectives are added by the POA Practitioner in review sessions. By conducting reviews often, the risk of developing unwanted features is reduced.
Obsess About Value
  • POA Practitioners should ensure that reviews
    demonstrate the value of the work product in question.
  • The focus should be on the value delivered rather than the amount of effort spent, or the process of development, or any cross- dependencies etc., that digress the reviews from value discussion.