Please Provide Following Information. We will get back to you as soon as possible.


Please Provide Below Information.


This program is eligible for the HRDF training grant claims under the TRAINING ASSISTANCE SCHEME (SBL SCHEME). Click on the below link to know the eligibility criteria and claim procedure.

HRDF Claim Eligibility and Procedure

Certified Scrum Product Owner (CSPO) Training

This document describes the Learning Objectives (LOs) that must be covered in a Certified Scrum Product Owner (CSPO) offering. These Learning Objectives take the following into consideration:

Every implementation of Scrum is different. Teams and organizations apply Scrum within their context, but the fundamental framework always remains the same.

Certified Scrum Product Owner

The Learning Objectives for this offering are based on:

  • Scrum Guide, scrumguides.org
  • Agile Manifesto, four values and 12 principles, agilemanifesto.org
  • Scrum Alliance® Scrum Foundations Learning Objectives


Scrum Alliance has adopted the Scrum Guide, The Definitive Guide to Scrum: The Rules of the Game, co-authored and updated (most recently in 2017) by the co-creators of the Scrum framework, as the guiding curriculum for this offering. CSPO® candidates are expected to build a body of knowledge of the Scrum framework, including its roles, events, and artifacts. Incorporating Scrum principles and practices takes diligence, patience, and a commitment to continuous improvement. Scrum is a framework, not a prescriptive methodology. Participants in a CSPO offering should expect that each Learning Objective identified in this document will be covered. Students should also expect that the Scrum Foundations Learning Objectives are covered either before or during the offering.

Learning Objectives

The CSPO Learning Objectives fall into the following categories:

  • Product Owner Core Competencies
  • Describing Purpose and Strategy
  • Understanding Customers and Users
  • Validating Product Assumptions
  • Working with the Product Backlog

Detailed Learning Objective

1.  Product Owner Core Competencies

1.1. Fundamentals of the Product Owner Role

  • Describe at least three distinct responsibilities of the Product Owner and at least two benefits of mastering the role.
  • Identify the impact on a Scrum Team and organization of at least three anti-patterns that might exist for Product Owners.
  • Discuss at least three types of organizational contexts that affect the approach to the Product Owner role.

1.2. Working with Stakeholders

  • Use at least one technique to provide transparency to stakeholders on progress toward goals.
  • List at least three techniques to engage stakeholders to gather information or insights.
  • List at least three different decision-making approaches a Product Owner might use.
  • 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.3. Working with the Development Team

  • Describe how the Product Owner collaborates with the Development Team for activities such as defining “Done” and backlog creation, refinement, and ordering.

1.4. Product Ownership with Multiple Teams

  • List at least three challenges of being a Product Owner with multiple teams.
2. Describing Purpose and Strategy

2.1. Product Strategy

  • Describe vision and practice the creation of a product vision.
  • Describe strategy and relate it to mission and goals.

2.2. Product Planning and Forecasting

  • Describe at least three different strategies for the incremental delivery of a product.
  • Explain at least three techniques to plan product delivery over time.
3. Understanding Customers and Users

3.1. Describe why a Product Owner performs discovery and validation work.

3.2. Illustrate at least one approach for segmenting customers and users.

3.3. Practice at least one technique to prioritize between conflicting customer (or user) needs.

3.4. Describe at least three aspects of product discovery and identify how each contributes to successful product outcomes.

3.5. Use one technique to describe users and customers, their jobs, activities, pains, and gains.

3.6. List at least three ways to connect the Development Team directly to customers and users, and describe at least three benefits of Development Team direct interactions.

4. Validating Product Assumptions

4.1. Describe how Scrum supports validating product assumptions.

4.2. List at least three approaches to validating assumptions by their cost and the quality of learning.

4.3. Describe at least one approach to choosing which assumption should be validated first.

5. Working With The Product Backlog

5.1. Differentiating Outcome and Output

  • Describe the relationship between outcome and output.
  • Describe at least three attributes of a Product Backlog item that help assess maximizing outcome.

5.2. Defining Value

  • Define value and list at least two techniques to measure value.
  • Describe value from the perspective of at least three different stakeholder groups.
  • List at least five terms and definitions related to product economics that contribute to financial success.

5.3. Ordering Items

  • Describe at least three criteria for ordering the Product Backlog.

5.4. Creating and Refining Items

  • Identify at least three sources of Product Backlog items.
  • Describe at least three techniques for generating new Product Backlog items and create at least one Product Backlog item that includes description of desired outcome and value.
  • List at least three techniques to enhance customer or user contribution to creating Product Backlog items.
  • Describe at least one approach to Product Backlog refinement.

Classes Schedule

Coming Soon

Please Write us to connect@agilemania.com

Need Support

Contact us if you need further assistance!