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

3. Understanding Product Ownership Analysis

3.2 Integrating Agile Business Analysis and POA

Guide to Product Ownership Analysis

Agile business analysis is:

"The practice of business analysis in an agile context with an agile mindset."

POA is a discipline that realizes the core principle of agile business analysis in product development, while applying agility at all levels, from product vision to daily work plans.

The seven principles of agile business analysis help develop the mindset required for building successful products:

•   See the Whole
•   Think as a Customer
•  Analyze to Determine What is Valuable
•   Get Real Using Examples
•   Understand What is Doable
•  Stimulate Collaboration and Continuous Improvement
•   Avoid Waste
Agile.png

These principles also support team collaboration and communication as the team works to deliver value that resonates with customers.

POA derives value for organizations and customers through the creation and delivery of high-value products.

The fundamental objectives that support value delivery include:
  • Gain Deep Understanding of Customers:
    • Identify customer problems
    • Understand the severity of customer problems
    • Identify opportunities to delight customers
  • Engage Key Stakeholders: Engage the team, customers and any other stakeholders that impact the success of the product.

  • Design Solutions for Impact: Design the solution that maximizes value delivery within a given business context and constraints (business and technical) while balancing value, feasibility, and strategic considerations.

  • Create and Deliver Product Value: Constantly deliver value through an incremental build of product features.

  • Learn and Adapt: Analyze value delivery based on regular customer feedback, supplemented with quantitative analysis.

  • Optimize Product Value: Make timely, informed decisions to remove impediments and continually improve the team's ability to develop the evolving product.

Effective POA
  • Requires adopting the right balance of agile and traditional practices for product development.
  • Emphasizes:
    • Sharing a clear and engaging product vision to build understanding for all stakeholders.
    • Maintaining support from key stakeholders in understanding business context and solution viability.Making effective decisions to prioritize needs and value delivery.
    • Ensuring transparency all the time through the Product Backlog.
    • Validating value throughout product build activities.
    • Willingness to quickly learn and adapt.
    • Developing a supportive and transparent relationship within the product team(s).