BAT Certified Pragmatic Product Owner/Product Manager

Overview: The “BAT Certified Pragmatic Product Owner/Product Manager” program by Business Agility Tune Up (Pvt) Ltd is a 3-day, highly practical course designed to build essential skills for Product Owners and Product Managers. This course covers key aspects of product ownership, including market and environmental analysis, stakeholder engagement, writing functional requirements, backlog management, and prioritization techniques. With a strong emphasis on activities, case studies, and discussions, participants will gain hands-on experience in defining, developing, and managing products effectively.

Key Takeaways:

• Understand market trends and perform competitor analysis.
• Analyze external (PESTEL, Porters 5 Forces) and internal (SWOT, Value Chain) environments.
• Learn techniques for identifying and articulating customer needs.
• Develop a product vision using frameworks like Vision Boards, Elevator Pitch, and Postcard from the Future.
• Master user journey mapping, empathy interviews, and user personas creation.
• Write high-quality user stories using the INVEST and 3C frameworks.
• Prioritize and estimate backlog items with techniques like MoSCoW and WSJF.
• Manage backlog progression with techniques such as progressive elaboration, acceptance criteria (Gherkin), and splitting user stories.

Who Should Attend:

• Product Owners, Product Managers, Business Analysts
• Project Managers, Technical Leads, Agile Coaches, Scrum Masters

What You Will Get:

• 24 contact hours with an experienced trainer
• Practical exercises, case studies, group activities
• Continuous mentoring and coaching
• Soft copies of course materials
• Certificate of Participation

Eligibility Requirements: No prior experience required. The course is ideal for professionals transitioning into product management roles or those looking to refine their existing skills.

Course Outline:

• The outward orientation of a product owner/product manager 
  • Market Analysis (Market trends and events, benchmarking, competitor analysis)
  • Enternal environment analysis (PESTEL Porters 5 forces, value chain)
• The inward orientation of a product owner 
  • Value chain analysis, SWOT, Value proposition cavas
• Identifying needs in the form of problems and opportunities
  • Definition of needs, problems and opportunities 
  • Writing a problem statement 
  • Root cause analysis techniques (Fishbone diagram, 5 whys, Pareto analysis)
• The product as a solution to a problem
  • Definition of a requirement
  • Types of requirements (business, stakeholder, functional, non-functional, transition)
  • Definition of a solution and design
• The product life cycle
  • The diffusion curve and the product life-cycle
• The product vision (north star)
  • Writing the product vision
  • Elevator pitch statement
  • Vision board by Roman Pitchler
  • Postcard from the future
  • Vision video
• Writing business requirements (Goals, Objectives and key results of the product)
• Stakeholder Analysis 
  • Stakeholder list, maps (RACI, Onion diagram, Mendelow’s matrix)
• Empathy
  • Conducting and empathy interview
  • Creating an Empathy mapping canvas
• User personas
  • Definition of a context
  • Users in different contexts
  • Creating a user persona
• User journey mapping
• Product Backlog Management
  • What is a product backlog
  • Product Backlog Items and the DEEP backlog
  • Progressive elaboration
• Writing functional requirements of a product
  • Writing a functional requirement involving a user as a User Story using the ‘user-voice’ format (With practical activities)
  • Writing a functional requirement without a user as a Job Story (JTDB)
• Writing quality user stories
  • INVEST criteria by Will Wake
  • 3 C’s of a User Story by Ron Jefferies
• Acceptance Criteria
  • What are acceptance criteria
  • Writing acceptance criteria as objective statements (bullet points)
  • Writing acceptance criteria using Gherkin Syntax (Given-When-Then)
• Techniques to better structure requirements
  • Data dictionary to capture entity and attributes related information (fields and validations)
  • NFR catalogue to capture NFRs
  • Business Rules Catalogue to capture Business rules
  • Brief discussion about using process diagrams, state chart diagrams, prototyping and other techniques
  • Good practices when structuring requirements using user stories and all above-mentioned techniques
• Splitting user stories by Richard Lawrence (with practical activities)
  • 10 user story splitting patterns (with practical activities)
• Identifying work to be done by technical team members as Enabler Stories (work that is not a functionality but of significant magnitude)
  • POC, R&D work as exploration enablers 
  • Enhancing/maintaining the architectural runway using architectural enablers 
  • Infrastructure work using infrastructure enablers 
  • Documentation, legal/regulatory work using compliance enablers
• Identifying large pieces of work as Epics
• Prioritizing backlogs of work 
  • What is priority 
  • What are prioritization criteria 
  • Prioritization techniques (MoSCoW, HML, WSJF)
• Estimating backlogs of work 
  • Cone of uncertainty 
  • Absolute estimation vs relative sizing 
  • Criteria to consider when doing relative sizing (relative sizing is more than effort estimation) – Identifying a base story 
  • Estimating backlog items using story points 
  • Playing planning poker to gain team concensus on bigness of backlog items
• Creating a user story map with prioritized backlog items
• Handling Change Requests, Enhancements, Defects, and Spillovers (with discussion around definitions, capturing such work, etc.)