Scrum Product owners are backbones of a scrum team. They act as a Mini CEO with complete ownership of the product backlog and value to the end customer. The outcome and value of a Scrum Product depends on the efficiency of the Scrum product owner.
Why Scrum Needs a Product Owner?
Scrum values human interaction over comprehensive documentation. Product owners are the backbone of a scrum team, responsible for keeping the product backlog, ensure timely feedback from the customer and communicate priorities within the scrum team. A Scrum Product Owner is expected to understand and apply scrum values and principles while maintaining the transparency while communicating with different stakeholders.
A full-time product owner ensures that the scrum team is working on the most valuable backlog item at any point in time and there is a considerable value in the form of a shippable product at the end of every sprint.
Why CSPO Certification?
The two days Scrum Product owner workshop helps you master the scrum values and principles. The outcome of a CSPO workshop is, you become an effective facilitator with working understanding of scrum and the role of a product owner. The two days scrum workshop ensures that you understand and appreciate the role of a product owner in success of a scrum project, and …
- Imbibe the scrum values and principles
- Learn to Manage stakeholders, Product backlog, create user stories, Definition of Done and acceptance criteria.
- Understand, prioritize and maximize the value out of every sprint
- Lead the scrum implementation in your team alongside Scrum Master
- Advocate scrum philosophy and strive for continuous improvement.
What is covered in the CSPO Class –
The CSPO certification workshop is based on the Scrum Product Owner Learning Objectives as defined by Scrum Alliance. For more information, please download the document here.
Who should Do a CSPO Course?
Certified Scrum Product Owner is a unique certificate. Product owner is a challenging role, you should do CSPO if you are …
- Business Analyst/Senior business Analyst
- Quality Assurance professional
- Product Manager/Product Owner
- Product owners/Existing scrum professional
- Scrum Enthusiast
On successful completion of the CSPO course, you will receive:
- Certified Product Owner Certificate
- Scrum Alliance membership for 2 years.
- Hard Copy of Study Material as specified by Scrum Alliance
- Master program on Agile, Scrum and Kanban ($150 Value -complimentary with CSPO class)
- Support and guidance in advanced certificates like CSP, PMI-ACP, Scaled Agile Framework etc.
Job Prospectus after CSPO
As a product owner you master the skills such as emotional intelligence, facilitation, negotiation, collaboration within teams and stakeholder management. You become a domain expert, a must have skill to reach new heights in a niche. Scrum has popularized the role a product owner or product manager within product teams. The industry is moving away from the service model and most companies are focusing on the product which sets them for a long-term success.
In 2018 alone, there are 1000s of new start-ups emerge at global arena with great products and unique solutions, thanks to dedicated product owners. The role of a product owner offers stability, growth and a job with more opportunities for lifetime.
Scrum Product owners can grow as Product Managers, Agile coaches, Scrum leaders and enterprise agile evangelists.
Download the detail course content here:
Need Some help? Call us 9990451333, 9958297711, 8884670012
Meet Our Trainers
CST , CEC, SPC4, PMP and PMI-ACP
Sekhar is a technocrat, management consultant and an Enterprise Agile Transformation Coach has over 16+ years of using methodologies from Agile to Waterfall.
Certified Scrum Product Owner (CSPO) training course:
1. Understand the Scrum Flow, the core components of the Scrum framework, and the Scrum vocabulary.
2. Understand the principles/legs of empirical process control
3. Understand the work culture Scrum creates
Roles & Responsibilities
1. Understand the scope of the Product Owner role in detail
2. Understand the scope of the ScrumMaster role at a high level
3. Understand the scope of the Team role at a high level
4. Understand why there is no project manager and no agile product manager
1. Understand the importance of having the product vision as an overarching goal galvanizing the entire Scrum team
2. Understand the desirable qualities of the vision
3. Understand how the vision can be shaped
4. Understand the importance of carrying out just enough prep work
5. Understand the relationship between vision and product roadmap
1. Understand the different estimation levels in Scrum
2. Understand that the accuracy of an estimate is more important than the precision of the estimate
3. Understand that estimates of size and duration can be done separately
4. Understand the impact of pressuring team members to provide low estimates.
5. Understand the difference between estimating and committing
The Product Backlog
1. Understand what the product backlog is (and is not)
2. Understand product backlog grooming
1. Understand the importance and benefits of prioritizing the product backlog
2. Understand the implications of saying everything is mandatory
3. Understand who should have input into prioritization decisions
4. Understand that proper prioritization of a product backlog is based on multiple factors.
5. Understand and know how to apply formal approaches to prioritizing (i.e., beyond just “gut feel” or intuition)
6. Understand how much latitude to give a team in adjusting the sequence of work.
1. Understand the goal of release management
2. Understand that planning is adaptive, iterative, and collaborative
3. Understand why quality is frozen and the concept of technical debt
4. Understand why software should be released early and frequently
5. Understanding and measuring velocity
6. Understand the release burndown chart
7. Understand how a release plan can help forecast the future
1. Understand the product owner’s role in the Scrum meetings
2. Understand how the Product Owner and Development Team collaborate during the Sprint
3. Understand what team commitment means
4. Understand why sprints are timeboxed and protected
5. Understand the concept of sustainable pace
Q. What is the definition of product owner?
A product owner is a mini CEO with the complete ownership of a product and the value it delivers to the end customer. A product owner’s role is to maintain and prioritize product backlogs, interact with the stakeholders for feedback on product, collaborate between team and other stakeholder for effective on time delivery of the product under development.
Q. Which is the best Certification for product owners?
|Features||Professional Scrum Product Owner||Certified Scrum Product Owner||SAFe Product Owner|
|Community Membership||Lifetime||2 years||1 year|
|Certification fee||$200 Exam fee+training||27000 for exam and training both||25000 Aprox. For exam and training both|
Q. Can I do an online training for CSPO certification?
Scrum Alliance always gives preference to in person interaction over virtual sessions. Like many other Scrum Alliance Workshops, classroom is mandatory for CSPO as well.
Q. What are the personal qualities of a successful product owner ?
|motivating teams||Moderately critical|
|knowledge of Scrum||Critical|
|Ability to work and empathize with customers||Very Critical|
|Ability to communicate difficult decisions at all levels||Very Critical|
|Ability to work within an organization to remove impediments||Moderately critical|
|Ability to say no||Critical|
|Knowledge of the complete product life cycle||Critical|
|Ability to apply the 80/20 rule||Very Critical|
|Negotiation skills||Very critical|
|Ability to influence||Very Critical|
|Domain expertise||Very Critical|
|Conflict management||Moderately Critical|
|Ability to make decisions||Very critical|
Q. What is the known scrum anti patterns that a product owner should be aware of?
Here is the comprehensive list of Product Owner Anti-patterns that a product owner should understand and avoid –
|Scrum Anti-Pattern (Product Owner)||Explanation|
|Oversized product backlog||The product backlog contains more items than the Scrum team can deliver within three to four sprints.|
|Incorrect product Backlog||Product Owner Copies items from requirement documents without consulting the scrum team.|
|The weak Product Owner||The product owner does not have the ability to say NO.|
|Prioritization by proxy||Other stakeholders are prioritizing the product backlog and PO is just their proxy with little power.|
|No One is THE product owner||When there are multiple stakeholders are defining and refining the requirements, team gets confusing decisions and instructions.|
|“I know everything” Product Owner||The PO does not involve stakeholders or subject matter experts in the refinement process, and probably not even the Scrum team.|
|Role Confusion||The product owner is confused about his role, tries to be both Scrum master and product owner at the same time.|
|Lack of interaction||Lacks interaction with the team, mostly dependant on the tools like Jira for interaction with team.|
|Not questioning Requirements||Inserting everything from the requirement document without questioning the value for end user.|
|Not understanding the risk||Add items without a valid understanding of business risks|
|The lack of a sprint goal||The Product Owner cannot provide a sprint goal, or the chosen sprint goal is flawed.|
|The pushy PO||Pushes the development team to take on more tasks than it could realistically handle using his previous experience and learning of team velocity|
|Playing with “definition of done”||Changing DOD by squeezing in some last-minute user stories that do not meet the definition of Done|
|The absent Product Owner||A PO should be readily available for immediate clarification. His inability to respond quickly will create a risk of scrum team missing their sprint goal.|
Cannot let go product backlog items once they become sprint backlog items
|Increasing the scope of a user story or modifying the acceptance criteria at last moment without consulting the scrum team.|
The selfish Product Owner
|There is no I in the team. Its not his or her accomplishments, its team accomplishments. Product owner should not take credit for team achievements.|
|The unapproachable, the broadcasting Product Owner||The PO is not accepting feedback from the customers and the stakeholders.|
Q. What are the types of organizational contexts that affects the Product Owner role?
There are three leading organizational contexts that affect a product owner’s role –
- Full-time product owner – A product owner acts as a mini-ceo, someone who have the complete ownership of target customer, problem, and solution
- Product owner as shared resource – A product owner is working with multiple teams as a shared resource or taking care of other engagements while playing the role of a PO.
- Short term product owners – a Product Owner works on short-term projects that they own the outcome for, they do not hold a prolonged engagement with the product and are not responsible for the long-term ROI on the product.
Q. What are the product owner’s tools to bring transparency in scrum teams?
- Release burn up charts – a burn up chart clearly shows work completed and project scope. It is an effective tool for communicating to the project stakeholders and clients how the extra feature requests they are asking for will affect the deadline, and at the same time for reassuring them that good progress is being made
- Sprint review – Sprint review is another tool to bring transparency within the scrum team. Its an opportunity to discuss what is working and what needs to be fixed. Team can openly raise impediments and product owner can work with scrum master and other stakeholders to remove these impediments.
- Product Roadmap – A Goal oriented product roadmap clearly shows the future course of action to the team.
- Daily stand-up – product owner can participate in daily standups to get an update on the progress of product backlog items and issues that the team is facing.
Q. What are the decision-making approaches for product owner?
A product owner can take following distinct decision-making approaches. Here is their pros and cons
|Decision making approach||Pros||Cons|
|Product Owner decides and informs the team|
|Product Owner consults the Development Team and/or stakeholders and then decides|
|Product Owner delegates a decision|
Q. How does facilitation skill help in becoming a better product owner?
A product owner is a natural facilitator. The role involves dealing with multiple stakeholders often with conflicting interests. The product owner has to perform the role of a neutral facilitator in the entire discussion; his focus should be on getting an unambiguous and non-conflicting information out of a discussion between various stakeholders.
Q. What are the various techniques a Product Owner could use when engaging with stakeholders to gather information or insights?
As a product owner you need to be a master facilitator who can bring the best out of a team and enhance collaboration. Here is a list of most important facilitation techniques for product owners –
Affinity grouping –
Affinity Grouping is a brainstorming method in which participants organize their ideas and identify common themes. A product owner can use Affinity grouping to club similar product ideas of feature requests, it helps them refine a user story.
Follow these steps to create Affinity grouping in your next Product Discussion meeting –
- Ask everyone to write their idea on a sticky note.
- Place all cards on a flipchart or whiteboard.
- Ask everyone from the group to club similar ideas
- Target for less than 10 groups of items.
- Discuss the grouped items as team
- Give a name to each clubbed item or attach to a story
- The discuss every group of idea with everyone present to stimulate the ideas, add more information or remove what is irrelevant.
- Add outcome of each discussion to the final list of features or points to the story.
Dot voting is another group discussion technique used by product owners to find preferences. The product owners can use this technique to prioritize a feature list or a list of story items. Follow the steps below to use dot voting technique –
- It is a simple group activity for recognizing preferences among limited options:
- Participants are each given a set number of dot stickers.
- They place dot stickers next to options presented that they like.
- Options with the most dots “win”.
Fist to five,
Fist to five is another popular brainstorming technique used by product owners to help achieve the consensus among teams. Follow the steps below to use this technique –
- State an action the group should take or show their level of support to a story item.
- Each member responds by showing the number of finger or closed fist. Higher the number of fingers, more the support.
- Any team member showing less than 3 fingers is given an opportunity to share her objections.
- The team will address the objections and the process is repeated again. It continues till the team achieves a consensus.
As a product owner if you want to explore a story in detail, Open ended questions are a great way. By asking open ended questions you offer people an opportunity to share more information, feelings, attitudes and understanding of the topic.
Q. Who is responsible for the product backlog?
The product backlog and owned, managed and prioritized by the product owner. He may take some help from the scrum team and discuss ideas but primary responsibility stays with the product owner.
Q. What is the difference between product owner and product manager
Scrum Does not recommend any role of a product owner. The complete product backlog and stakeholder interaction is owned by Product Owner. But in an Enterprise Agile Environment, organization do have a product manager role who focuses on high level requirements and interacts with the external stakeholders.
Difference between product owner and product manager
|Product owner||Product manager|
|Converts high level requirements into user stories||Manages high level requirements|
|Writes story level Acceptance criteria and Definition of done.||Writes high level Acceptance criteria|
|Interacts with internal stakeholders||Interacts with external stakeholders|
|Focus on immediate delivery and product value. Attends scrum meeting, retrospectives, product demo etc.||Has a long-term vision for the product, interacts with sales, marketing and other external stakeholders|
Q. At what experience level should I go for a product owner certificate?
There is no defined level of experience after which you can consider going for a PO role. Ideally after a 3-4 years of experience you might be able to handle the challenges which a product owner role offers. A product owner needs to be tough negotiator, team player and a great collaborator in order to succeed in his role. Domain expertise and understanding of scrum framework is also critical for success.
Q. Why should I go for CSPO®?
A. CSPO® – Certified Scrum Product Owner is a credential offered by Scrum Alliance®. A Product owner is someone who understands the customers who buy the product, end users who use the product and sponsors who invests in the product and prioritizes the work done. If you want to start your journey of becoming product owner using Agile principles and the Scrum Framework, Scrum Product Owner® is the first step.
Q. Will I get any PDUs after your training program?
A.Yes, the students will get 16 Category ‘A’ PDUs towards any PMI’s PMP® / PMI-ACP® / PgMP® / PMI-PBA ® credential after the training program.
Q. Do I need membership of Scrum Alliance to attend training for this certification?
A. No, this workshop provides you the membership of Scrum Alliance for 2 years.
Q. Do I need to take any test to become CSPO®?
A. No, on successful completion of the course, you will receive Certified Scrum Product Owner® (CSPO®) Certificate.
Q.Do you provide training material for this certification?
A. We provide very good pre-training material in the form of Videos and content which include “Impact Mapping” book by Gojko Adzic, a workbook, a hard copy of the material used in the class and digital reading material for post-class reference.
Q. What next after becoming a CSPO®?
A. You can go for advance certificates like CSP® or PMI-ACP®. We also provide support in getting your advanced certificates like CSP® or PMI-ACP®.
1. Familiarize yourself with Scrum, by accessing our pre-training material in the form of Videos and contents.
2. Attend our 2-day course.
3. This 2-day course enables participants to understand the role of a Product Owner and a few tips and techniques to maximize the value of work done as part of product development. It will help you understand how Scrum works by focusing on your role as the Product Owner, or customer, for a Scrum team.
4. On successful completion of the course, you will receive Certified Product Owner (CSPO®) Certificate.