Advanced Certified Scrum Product Owner™ Training

Developing Practical Product Strategies
2.1. … demonstrate a context-rich approach for communicating with stakeholders and Scrum Team members.
2.2. … describe at least one simple tool that captures key aspects of a business. For example: business model canvas, Lean canvas, value proposition canvas.
2.3. … discuss a real-world example of how product strategy is operationalized and evolves over time in an Agile organization.
2.4. … practice at least two approaches to identify purpose or define strategy and foster alignment and shared ownership. For example: co-creating, collaborating, product or vision box, cover story, selling, or telling.

Advanced Roadmapping and Release Planning
2.5. … organize and facilitate a stakeholder session to break down a solution or feature as progressively smaller items that may be completed in sprints.
2.6. … create a prioritized product roadmap with stakeholders.
2.7. … demonstrate how to plan a product release based on content from a roadmap, market segmentation and market window.

Customer Research and Product Discovery
3.1. … use one technique to connect teams directly to customers and users to build deeper understanding and empathy (e.g., job shadowing, customer interviews, customer observation, collaborative customer games, usability testing, or simulating customer experience).
3.2. … integrate at least three techniques to generate new product and feature ideas, and use at least one (e.g., design studio, brainstorming, collaborative customer games, etc.).
3.3. … practice at least two techniques of product discovery and how each contributes to successful product outcomes (e.g., user research, customer experience design, interaction design, usability engineering, visual design) and practice one technique.
3.4. … demonstrate at least two techniques to visualize and communicate product and feature ideas and assumptions. For example: business model canvas, customer journey map, user story map, user scenario, or design comic.

4.1. … list two cognitive biases that may impact the Product Owner’s capability to effectively deliver business value. For example, anchoring (on prior opinion or desired total effort), priming based on assumptions, confirmation bias, framing bias, self-serving bias, fundamental attribution error, etc.
4.2. … appraise how effectively the sprint review meeting is used in your organization to inspect and adapt based on the product increment that was built in the sprint.
4.3. … experiment with at least two approaches to incorporate testing assumptions into the Scrum framework. For example: Validation is complete prior to starting sprints, the Product Owner validates assumptions a sprint or two ahead of the Development Team, and the Scrum Team uses the Sprint Goal to deliver results to test assumptions.
4.4. … develop three hypotheses for a given target user/customer segment and create a plan to test one hypothesis. For example, “I believe [target market] will [do this action/use this solution] for [this reason].” “The signal to detect the hypothesis is true or false is…”
4.5. … compare at least three approaches to testing assumptions by their cost and the quality of learning (e.g., building potentially releasable product, customer interviews, ethnographic research, direct user observation, A/B tests, collaborative games, concierge/Wizard of Oz MVPs, paper prototypes, functional prototypes.).

Differentiating Outcome and Output
5.1. … describe one benefit of maximizing outcome and impact to the business, user, and market while minimizing output for a product/feature idea. For example: Don’t build features that won’t be used, faster time to market by focusing only on highest outcome, etc.
Defining Value
5.2. … use at least two techniques to model value. For example: “We believe that if we do X, then the result will be Y.” “By adding this capability, we expect click through rates to increase by 20% in the next three months.”
5.3. … use at least two techniques to measure value. For example: usage metrics, NPS, customer and user interviews, social media sentiment, direct observation, ROI, profitability of the product, inbound customer feedback, etc.

Ordering Items
5.4. … describe and apply at least four factors to implement when ordering a product backlog (e.g., value, effort, risk reduction, dependencies, cost of delay, readiness to build, testability, learning value, ability to deliver to customers).
5.5. … apply at least two different techniques to structure and filter the contents of a given product backlog (e.g., using themes, feature areas, concerns).

Advanced Item Refinement

5.6. … illustrate how the Product Owner can ensure that enough product backlog items are “ready” for the upcoming sprint. For example, create a shared Definition of “Ready,” hold frequent refinement sessions, empower more people to do this work, etc.
5.7. … integrate feedback from at least three sources to generate product backlog items. For example: different stakeholder groups, regulatory requirements, learning from validation, defects, technical concerns, etc.
5.8. … demonstrate how to communicate the purpose and intent of a product backlog item, answer clarification questions, and rephrase or split the product backlog item with others.

5.9. … list at least three techniques to enhance user/customer contribution to product backlog item formulation (e.g., user story brainstorming, customer interviews, open planning meeting).
5.10. … describe acceptance criteria for a product backlog item so that a Development Team can understand the conditions for the item to be accepted as done.