Agile Product Management Training Course

Participants can create a product strategy that gives teams and stakeholders clear direction.

• Vision statements tested against customer, business and delivery realities
• Product strategy choices: target users, needs, differentiation and constraints
• Positioning statements structured with category, audience, benefit and proof
• Value proposition canvas applied to customer jobs, pains and gains
• Strategic themes translated into bounded product investment areas
• Assumptions register records strategic beliefs requiring evidence

Participants can frame product problems using market, customer and operational evidence.

• Problem framing separates symptoms, causes, affected users and consequences
• PESTLE analysis identifies external forces affecting product viability
• Porter's Five Forces tests competitive pressure and market attractiveness
• Jobs to Be Done interviews identify functional, emotional and social progress
• Customer journey maps expose friction, handoffs and unmet needs
• Service blueprints connect customer experiences with backstage operating processes

Participants can plan and conduct discovery that reduces critical product uncertainty.

• Research questions derived from the riskiest product assumptions
• Interview guides avoid leading questions and solution confirmation bias
• Recruitment criteria define relevant customer segments and user contexts
• Observation notes distinguish direct evidence from researcher interpretation
• Affinity mapping groups interview findings into recurring needs
• Research repositories preserve evidence, quotes, decisions and open questions

Participants can assess opportunities before committing them to delivery roadmaps.

• Opportunity solution trees connect desired outcomes, opportunities and solutions
• Assumption mapping ranks beliefs by importance and uncertainty
• Impact mapping links business goals to actors, behaviours and deliverables
• Opportunity scoring combines customer value, strategic fit and feasibility
• Problem statements specify users, situations, needs and measurable impacts
• Discovery backlog orders research, prototypes and validation decisions

Participants can assess product opportunities using basic commercial and financial measures.

• Business model canvas tests value creation, delivery and revenue logic
• Cost-to-serve analysis identifies operational costs by customer interaction
• Unit economics calculate contribution margin, acquisition cost and retention value
• Total cost of ownership includes implementation, support and change costs
• Benefits hypotheses specify measurable financial, customer and risk outcomes
• Sensitivity analysis tests business cases against uncertain demand assumptions

Participants can define product outcomes and connect them to measurable objectives.

• Objectives and Key Results distinguish direction from measurable evidence
• Outcome statements describe changed customer behaviour or business performance
• Leading indicators provide early signals before lagging value measures
• Key result thresholds define success, concern and intervention points
• Initiatives mapped beneath OKRs without treating them as key results
• OKR cadences coordinate product reviews, decisions and learning

Participants can select and interpret metrics for product decisions and learning.

• North Star Metric links sustained customer value with product growth
• AARRR funnels track acquisition, activation, retention, referral and revenue
• Cohort analysis separates retention patterns from aggregate customer averages
• Funnel analysis identifies conversion loss between critical user actions
• Product metric trees connect executive measures with team-level drivers
• Guardrail metrics detect quality, equity, risk and service deterioration

Participants can design proportionate experiments that support product investment decisions.

• Test cards document hypotheses, methods, measures and decision criteria
• Minimum viable experiments test assumptions with limited time and cost
• Prototype fidelity selected according to the learning question
• A/B test design controls audience, variables and success metrics
• Sample bias and confounding risks assessed before interpreting results
• Experiment decisions recorded as persevere, pivot, pause or stop

Participants can create outcome-based roadmaps that communicate investment choices clearly.

• Now-next-later roadmaps communicate direction without false delivery precision
• Theme-based roadmaps group initiatives around strategic customer outcomes
• Roadmap horizons separate commitments, forecasts and exploratory options
• Investment guardrails define budget, capacity, risk and compliance limits
• Dependency maps reveal sequencing constraints across products and platforms
• Roadmap narratives explain choices, uncertainties and decision triggers

Participants can prioritise product investments using transparent value and urgency criteria.

• RICE scoring compares reach, impact, confidence and effort
• Cost of Delay combines user value, time criticality and risk reduction
• WSJF sequencing considers cost of delay against job size
• Kano analysis distinguishes basic, performance and attractive product attributes
• Prioritisation workshops expose scoring assumptions and stakeholder disagreements
• Portfolio heatmaps compare strategic fit, value, uncertainty and delivery risk

Participants can translate product opportunities into coherent, releasable user journeys.

• User story maps organise activities, tasks and release slices
• Backbone activities represent the end-to-end customer journey
• Walking skeletons establish minimum end-to-end technical and user capability
• Vertical slicing delivers usable value across interface, logic and data
• INVEST criteria improve story independence, value and testability
• Release slices tested against outcome hypotheses and operational readiness

Participants can maintain a product backlog that supports reliable delivery decisions.

• Product backlog ordering reflects value, risk, learning and dependencies
• User stories capture actor, need and intended product value
• Acceptance criteria specify observable conditions for product behaviour
• Example mapping exposes rules, examples and unanswered questions
• Definition of Ready supports appropriate refinement without excessive specification
• Backlog ageing identifies stale items, duplicates and obsolete assumptions

Participants can support delivery teams while preserving product decision accountability.

• Sprint goals connect planned work with a single meaningful outcome
• Sprint reviews gather stakeholder evidence rather than approval theatre
• Daily Scrum boundaries protect team coordination and product manager focus
• Capacity planning accounts for discovery, delivery, support and technical debt
• Technical debt conversations connect engineering investment with product risk
• Definition of Done includes quality, documentation, security and operational requirements

Participants can plan releases that account for adoption, operations and risk controls.

• Release plans align product scope, readiness criteria and decision gates
• Feature flags support controlled exposure, rollback and staged learning
• Go-live checklists cover service support, training, communications and monitoring
• Operational readiness reviews assess processes, ownership and incident response
• Launch cohorts sequence users according to risk, value and support capacity
• Post-launch reviews compare expected outcomes with observed product performance

Participants can structure stakeholder engagement and escalation around product decisions.

• Stakeholder maps assess influence, interest, expectations and decision authority
• RACI matrices clarify accountabilities for product investment and release decisions
• Decision logs record options, evidence, owners and agreed rationale
• Product councils review strategic choices, dependencies and investment thresholds
• Escalation paths distinguish delivery issues from product direction decisions
• Executive product updates communicate outcomes, risks, decisions and requests

Participants can integrate risk, compliance and quality requirements into product planning.

• Risk registers document product threats, controls, owners and review dates
• Three lines model clarifies management, oversight and assurance responsibilities
• Privacy by design embeds data minimisation and purpose limitation
• Non-functional requirements address performance, availability, security and accessibility
• Threat modelling identifies misuse cases, attack surfaces and mitigations
• Accessibility acceptance criteria reference WCAG principles and user needs

Participants can coordinate product work across teams without losing customer focus.

• Team topologies clarify stream-aligned, platform and enabling team interactions
• Product boundaries define ownership, interfaces and customer value streams
• Dependency boards visualise cross-team commitments, blockers and handoffs
• Integrated planning balances local autonomy with shared delivery milestones
• Communities of practice establish consistent product methods and standards
• Portfolio Kanban visualises demand, discovery, delivery and investment decisions

Participants can manage product performance, improvement and retirement decisions over time.

• Product health reviews combine value, quality, risk and cost evidence
• Customer feedback loops classify requests, defects, complaints and emerging needs
• Retention analysis identifies adoption barriers and declining customer engagement
• Lifecycle stages guide investment, optimisation, maintenance and retirement choices
• Sunset plans address migration, communications, data retention and support closure
• Post-implementation reviews capture benefits, lessons and follow-up actions

Participants can build, review and present a complete evidence-based product management pack.

• Problem assessment consolidates customer evidence, market context and operational constraints
• Product strategy states vision, target segment, positioning and strategic themes
• Opportunity map links desired outcomes with prioritised customer opportunities
• Roadmap sequences initiatives, dependencies, investment assumptions and release horizons
• Metrics model defines OKRs, North Star Metric and guardrails
• Backlog slice specifies user journey, acceptance criteria and delivery sequencing
• Stakeholder presentation defends product choices, evidence, risks and next decisions