AGILE - CERTIFIED SCRUM MASTER

Fundamentals of the Product Owner Role

1.1. Describe the responsibilities of the Product Owner role and the benefits of Scrum Team collaboration.

1.2. Report that the Product Owner helps the organization realize value through delivering product solutions that delight customers and users within the constraints of technical feasibility.

1.3. Describe the Product Owner’s role in the various Scrum events.

1.4. List at least three personal qualities of a Product Owner that support effective delivery and validation of product ideas. Examples: emotional intelligence, collaborative skills, motivating teams, knowledge of Scrum, ability to work and empathize with customers, ability to communicate difficult decisions at all levels, ability to work within an organization to remove impediments, ability to say no, business skills, knowledge of the complete product life cycle, ability to apply the 80/20 rule, conflict management, negotiation skills, ability to influence, ability to make decisions, domain expertise.

1.5. Identify the impact on a Scrum Team and organization of at least three anti-patterns that might exist for Product Owners and report on one. Examples: The Product Owner is viewed as simply an order taker; the Product Owner says, “It’s all important,” focusing only on strategy and handing details off to the Development Team; leaving everything ambiguous, letting the team figure it out with no input; telling the team how to do their job.

1.6. Discuss at least three types of organizational contexts that affect the approach to the Product Owner role and report on one. Examples: A Product Owner has complete ownership of target customer, problem, and solution; a Product Owner owns the delivery of someone else’s idea or initiative; a Product Owner delivers a shared service to other teams in the organization; a Product Owner works on short-term projects that they own the outcome for, etc.

1.7. Explain why Scrum as a framework works for product development and how the Scrum Team delivers product increments. Examples: Discover and evaluate a real-world product idea where the output delivered a successful outcome and used feedback loops to inspect and adapt plans for further value delivery; describe how Scrum reduces risk through inspection and adaptation over short timeframes; describe how Scrum creates an environment where imperfect knowledge and/or decisions are acceptable since Scrum enables error corrections.

Working with Stakeholders

1.8. Use at least one technique to provide transparency to stakeholders on goals and progress. Examples: release burn-up chart, roadmap, sprint reviews, etc.

1.9. List at least three different decision-making approaches a Product Owner might use, depending on their context. Examples: Product Owner decides and informs the team, Product Owner consults the Development Team and/or stakeholders and then decides, Product Owner delegates a decision, etc.

1.10. Define a facilitator and discuss at least two situations where the Product Owner might act as a neutral facilitator and when they might use a different engagement approach.

1.11. List one technique a Product Owner could use when engaging with stakeholders to gather information or insights (e.g., affinity grouping, dot voting, fist of five, open-ended questions, etc.).

Working with the Development Team

1.12. Describe how the Product Owner collaborates with the Development Team on activities such as defining done and backlog creation, refinement, and ordering.

Product Ownership with Multiple Teams

1.13. List at least three techniques for visualizing, managing, or reducing dependencies between teams. Examples: Coordinate with other Product Owners, redefine product backlog items to remove dependencies, ensure product backlogs are visibly shared between Product Owners and Scrum Teams.

Product Strategy

2.1. Define the terms purpose, vision, mission, strategy, and tactics in relation to the work. (Note: These terms are debated among experts, so the goal is to discuss and agree on how the terms might be used on the learner’s team.)

2.2. Communicate the purpose of a product idea by describing the problem being solved, who is most affected by the problem, how the team’s efforts will improve the situation, and how that solution’s effectiveness will be evaluated.

2.3. Identify at least two approaches to identify purpose or define strategy. Examples: co-creating, collaborating.

2.4. Explain how strategy is impacted from outside the Scrum Team. Examples: alignment with other parts of the business, hiring, channel partners, cost structure, metrics, etc.

Roadmaps and Release Planning

2.5. Describe at least three different strategies for the incremental delivery of a product. Examples: opportunistic, multi-sprint releases, fixed date or fixed scope, release each sprint, continuous delivery (in sprint), etc.

2.6. Explain how to create a prioritized product roadmap with stakeholders.

2.7. Describe a solution or feature as progressively smaller items that may be completed in a sprint.

Customer Research and Product Discovery

1. Understanding Key Groups

3.1 Compare and contrast the needs of three key groups:Users: Those who actively use the product. They need usability, functionality, and features that solve their specific problems.

Customers: Those who purchase the product. They focus on value for money, ROI, and how the product improves business outcomes.

Stakeholders: Those who benefit indirectly from the product, such as internal teams, investors, or regulatory bodies, often concerned with compliance, market impact, or strategic alignment.

2. Segmentation of Customers and Users

3.2 Illustrate an approach for segmenting customers and users. Example methods:Customer Types: Individual, enterprise, or SMB.

Geography: Regional, global, or country-specific.

Regulatory Bodies: Compliance-driven segmentation (e.g., finance, healthcare).

3. Product Prioritization Strategy

3.3 Describe a strategy for product prioritization:Focused Strategy: Prioritize discovery and delivery for specific user/customer types to deepen engagement and ensure targeted value delivery.

Broad Strategy: Focus on multiple users and customers for wide market coverage but with a higher risk of diluted focus.

4. Building Empathy with Customers

3.4 List three benefits of connecting teams directly to customers and users, such as deeper understanding of needs, improved product design, and increased customer satisfaction.Techniques include:Job Shadowing

Customer Interviews

Usability Testing

5. Describing Users and Customers

3.5 Use a technique to describe users and customers, such as:Empathy Maps: Understand user jobs, pains, and gains.

Personas: Create a fictional representation of target users to guide development.

6. Generating New Product and Feature Ideas

3.6 Describe three techniques for generating ideas and practice one, such as:Design Studio

Brainstorming

Collaborative Customer Games

7. Aspects of Product Discovery

3.7 Identify at least three aspects of product discovery, such as:User Research: Identifying user needs and pain points.

Customer Experience Design: Crafting interactions that delight users.

Usability Engineering: Ensuring ease of use through iterative testing.

8. Techniques for Building Deeper Customer Understanding

3.8 List techniques to connect teams directly to customers and users:Job Shadowing

Customer Observation

Simulating Customer Experience

Differentiating Outcome and Output

Defining Value

Ordering Items

Creating and Refining Items