CSPO
Coming Soon
Expected availability announced soon
This course is in active development. Preview the scope below and create a free account to be notified the moment it goes live.
CSPO
Candidates learn the Product Owner’s accountability, mindset, vision, backlog management, customer insight, and stakeholder collaboration within Scrum, enabling them to deliver value-driven products. The course prepares them for the CSPO exam through interactive sessions and applied assessments.
Who Should Take This
Emerging and current Product Owners, business analysts, and agile team members who have at least six months of Scrum experience benefit from this certification. They seek to deepen their understanding of product vision, backlog refinement, and stakeholder engagement to drive successful product outcomes.
What's Covered
1
Domain 1: Product Owner Accountability and Mindset
2
Domain 2: Product Vision and Product Goal
3
Domain 3: Product Backlog Management
4
Domain 4: Understanding Customers and Users
5
Domain 5: Stakeholder Engagement
6
Domain 6: Release Planning and Forecasting
7
Domain 7: Sprint Collaboration and Definition of Ready
What's Included in AccelaStudy® AI
Adaptive Knowledge Graph
Practice Questions
Lesson Modules
Console Simulator Labs
Exam Tips & Strategy
20 Activity Formats
Course Outline
65 learning goals
1
Domain 1: Product Owner Accountability and Mindset
3 topics
Product Owner role within Scrum
- Describe the Product Owner accountability as the single person responsible for maximizing the value of the product resulting from the work of the Scrum team.
- Identify the Product Owner's key responsibilities including developing and communicating the Product Goal, creating and ordering Product Backlog items, and ensuring the Backlog is transparent and understood.
- Apply the principle that the Product Owner is one person rather than a committee, delegating work to the Developers while retaining accountability for backlog decisions.
- Analyze the challenges Product Owners face when the organization does not respect their authority over the Product Backlog, and determine strategies for establishing appropriate empowerment.
Value-driven mindset
- Describe value maximization as the primary objective of the Product Owner, focusing on delivering the highest-value features and capabilities to customers and the business.
- Apply economic thinking to product decisions by evaluating cost of delay, return on investment, and opportunity cost when ordering Product Backlog items.
- Analyze the tradeoffs between building new features, reducing technical debt, and improving existing functionality to determine the ordering that maximizes overall product value.
Scrum framework from PO perspective
- Describe how each Scrum event supports the Product Owner's responsibilities including Sprint Planning for selecting work, Sprint Review for gathering feedback, and Retrospective for improving processes.
- Apply the Product Owner's participation in Sprint Planning to communicate the Sprint Goal, clarify backlog items, and answer Developer questions while respecting team autonomy over implementation.
- Analyze the Product Owner's role in Sprint Review to determine how to maximize stakeholder feedback quality and translate insights into actionable Product Backlog updates.
2
Domain 2: Product Vision and Product Goal
3 topics
Product vision creation
- Describe a product vision as an aspirational description of the long-term purpose and direction of the product that inspires and guides the Scrum team's work.
- Apply product vision creation techniques including elevator pitch format, vision board, and product box exercise to articulate a compelling and shared product direction.
- Analyze the alignment between the product vision and current Product Backlog content to identify gaps where the team's work does not advance the stated vision.
Product Goal definition
- Describe the Product Goal as a measurable medium-term objective that supports the product vision and provides the Scrum team with a target for planning and prioritization.
- Apply Product Goal setting techniques to define clear, measurable, and achievable goals that bridge the gap between the product vision and Sprint-level execution.
- Analyze when to pivot or persist on a Product Goal based on market feedback, delivery progress, and changing stakeholder needs.
Roadmap and goal communication
- Describe product roadmaps as strategic communication tools that convey planned direction without committing to fixed scope or dates, emphasizing goals over specific features.
- Apply roadmap creation techniques such as Now-Next-Later and goal-oriented roadmaps that communicate product direction while maintaining the flexibility needed for empirical product development.
- Analyze roadmap effectiveness by evaluating stakeholder understanding of product direction and the frequency of misalignment between expected and actual delivery outcomes.
3
Domain 3: Product Backlog Management
3 topics
Backlog creation and structure
- Describe the Product Backlog structure including epics, features, user stories, and technical items, explaining how different levels of granularity serve different planning horizons.
- Apply user story writing using the role-feature-benefit format with acceptance criteria to create backlog items that are clear, testable, and independently deliverable.
- Apply the INVEST criteria to evaluate user story quality, ensuring stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
- Analyze Product Backlog items to determine appropriate decomposition strategies that break large items into smaller, independently deliverable pieces while maintaining value coherence.
Backlog ordering and prioritization
- Describe prioritization frameworks including MoSCoW, Weighted Shortest Job First, and Kano model, explaining when each approach is most appropriate for ordering backlog items.
- Apply MoSCoW prioritization to categorize backlog items as Must-have, Should-have, Could-have, and Won't-have for a given release or Product Goal increment.
- Apply value-versus-effort analysis to order Product Backlog items by considering the ratio of expected business value to development effort for each item.
- Analyze the impact of dependencies, risk, and learning objectives on backlog ordering to determine when items should be promoted or deferred regardless of pure value ranking.
Backlog refinement
- Describe Product Backlog refinement as the ongoing activity of adding detail, estimates, and order to backlog items, typically consuming no more than 10% of the Developers' capacity.
- Apply refinement session facilitation techniques to prepare backlog items for upcoming Sprints, ensuring items are sufficiently understood and right-sized for Sprint Planning.
- Analyze refinement effectiveness by evaluating Sprint Planning duration, Developer confidence in estimates, and the frequency of mid-Sprint scope clarification requests.
4
Domain 4: Understanding Customers and Users
3 topics
Customer and user segmentation
- Describe customer segmentation techniques including demographic, behavioral, and needs-based segmentation to identify distinct user groups with different product requirements.
- Apply persona creation techniques to develop representative user profiles that capture goals, pain points, behaviors, and context to guide product decisions.
- Analyze the difference between customers who purchase the product and end users who interact with it to ensure backlog ordering considers both buyer and user perspectives.
User feedback and validation
- Describe user feedback collection methods including interviews, surveys, usability testing, and analytics to gather empirical evidence about user needs and product effectiveness.
- Apply minimum viable product thinking to define the smallest Increment that can be released to gather meaningful user feedback and validate product assumptions.
- Apply empathy mapping to synthesize user research data into actionable insights about what users say, think, feel, and do in relation to the product.
- Analyze user feedback patterns to distinguish between requests that address genuine unmet needs and requests that reflect habitual preferences or competitor feature matching.
Market and competitive awareness
- Describe competitive analysis techniques including feature comparison, SWOT analysis, and market positioning to understand the product's context within its competitive landscape.
- Apply competitive intelligence gathering to inform backlog ordering decisions, identifying features where the product leads, lags, or differentiates from competitors.
- Analyze market trends and customer feedback patterns to identify emerging opportunities and threats that should influence product direction and backlog priorities.
5
Domain 5: Stakeholder Engagement
2 topics
Stakeholder identification and management
- Describe stakeholder categories including sponsors, users, customers, regulators, and internal teams, identifying their different interests and influence on product direction.
- Apply stakeholder mapping to visualize stakeholder influence and interest levels, determining appropriate communication frequency and engagement strategies for each group.
- Analyze competing stakeholder priorities to determine how to balance conflicting requests while maintaining focus on the Product Goal and overall value maximization.
Communication and transparency
- Describe the Product Owner's communication responsibilities including articulating product direction, sharing progress updates, and managing stakeholder expectations about scope and timeline.
- Apply transparent communication techniques to share product progress, upcoming priorities, and known risks with stakeholders using accessible visual formats.
- Apply the Sprint Review as a stakeholder engagement opportunity, structuring the event to maximize feedback quality and collaborative product direction setting.
- Analyze communication breakdowns between the Product Owner and stakeholders to identify root causes and implement improved communication channels and cadences.
6
Domain 6: Release Planning and Forecasting
3 topics
Release planning
- Describe release planning as the activity of defining what subset of the Product Backlog will be delivered by a target date or within a defined scope boundary.
- Apply release planning techniques using velocity data, capacity estimates, and Product Backlog ordering to create realistic delivery forecasts for stakeholders.
- Analyze release plan assumptions including team stability, scope volatility, and dependency risks to communicate forecast confidence levels and contingency strategies.
Definition of Done and quality
- Describe the Definition of Done from the Product Owner perspective, explaining how quality standards affect release readiness and stakeholder trust in the Increment.
- Apply the Definition of Done to Sprint Review acceptance decisions, distinguishing between items that meet quality standards and items that require additional work.
- Analyze the impact of Definition of Done evolution on release predictability, explaining how strengthening quality standards may temporarily reduce velocity while improving long-term delivery.
Product metrics
- Describe product success metrics including user adoption, customer satisfaction, revenue impact, and feature utilization rates that measure value delivery beyond velocity.
- Apply product metrics collection and reporting to demonstrate the value of delivered Increments and inform future Product Backlog ordering decisions.
- Analyze the correlation between product metrics and backlog ordering decisions to evaluate whether the team is delivering maximum value aligned with the Product Goal.
7
Domain 7: Sprint Collaboration and Definition of Ready
3 topics
Definition of Ready practices
- Describe the concept of Definition of Ready as a team agreement about when a Product Backlog item has sufficient detail for the Developers to confidently commit to it in Sprint Planning.
- Apply Definition of Ready criteria to evaluate whether backlog items include clear acceptance criteria, are appropriately sized, and have dependencies identified before Sprint Planning.
- Analyze the tradeoffs between strict readiness criteria that slow backlog throughput and relaxed criteria that cause mid-Sprint discovery and scope renegotiation.
Sprint Goal collaboration
- Describe the Product Owner's role in Sprint Goal creation as proposing value to be delivered while collaborating with Developers to define a goal that balances ambition with achievability.
- Apply Sprint Goal negotiation techniques to balance stakeholder urgency with team capacity, creating goals that are meaningful to the business and achievable by the team.
- Analyze Sprint Goal achievement patterns across multiple Sprints to identify whether goals are consistently too ambitious, too conservative, or misaligned with Product Goal progress.
Acceptance criteria writing
- Describe acceptance criteria as the conditions that a Product Backlog item must satisfy to be considered complete, providing a shared understanding between Product Owner and Developers.
- Apply Given-When-Then format and scenario-based acceptance criteria to create clear, testable conditions that reduce ambiguity and prevent scope creep during Sprint execution.
- Analyze acceptance criteria completeness by evaluating whether edge cases, error handling, and non-functional requirements are adequately specified for each backlog item.
Scope
Included Topics
- All topics in the Scrum Alliance Certified Scrum Product Owner (CSPO) learning objectives aligned to the Scrum Guide (2020): Product Owner accountability, Product Backlog management, value delivery, and stakeholder collaboration.
- Product Owner core competencies including product vision articulation, Product Goal definition, Product Backlog creation and ordering, user story writing, acceptance criteria definition, and value maximization.
- Goal setting and Sprint planning from the Product Owner perspective including Sprint Goal collaboration, release planning, and forecasting delivery timelines.
- Understanding customers and users through segmentation, persona development, empathy mapping, and techniques for validating product assumptions and gathering user feedback.
- Stakeholder management including identifying stakeholders, managing expectations, facilitating collaboration between business and development, and communicating product direction.
- Scrum framework fundamentals as they relate to the Product Owner accountability including all events, artifacts, and commitments from the Product Owner perspective.
Not Covered
- Advanced product strategy, business model innovation, and market analysis covered by A-CSPO and CSP-PO certifications.
- ScrumMaster-specific facilitation, coaching, and organizational change management techniques covered by the Scrum Master track.
- Technical engineering practices, architecture decisions, and developer-specific agile practices covered by the Developer track.
- Scaling product ownership across multiple teams and product portfolios beyond basic awareness.
- Specific tool configurations for product management platforms such as Aha!, ProductPlan, or Pendo.
Official Exam Page
Learn more at Scrum Alliance
CSPO is coming soon
Adaptive learning that maps your knowledge and closes your gaps.
Create Free Account to Be Notified