Distinguish yourself as an advanced Scrum Product Owner
3 Months FREE Access to all our E-learning courses when you buy any course with us
You have shown your commitment to Agile by gaining the CSPO certification. But how will you distinguish yourself from other CSPOs? How will you ensure that your resume reflects your skillset, diligence, and commitment to continuous improvement? You can gain the Advanced Certified Scrum Product Owner™ (A-CSPO™) credential.With this credential, you will demonstrate to your peers and employers that you have advanced knowledge and skills on all things Scrum, and can guide your Scrum team to success.
KnowledgeHut brings you a course that will help you understand all the learning objectives of the course and gain the certification. You will gain the practical expertise and enhanced skills to implement Agile in the workplace through interaction, facilitation, coaching, and team dynamics.
Prerequisites:
To earn an Advanced CSPO, you must have an active CSPO® certification with Scrum Alliance®, in addition to demonstrating at least one-year work experience specific to the role of Product Owner.
Certification:
Attending this workshop and completing all the learning objectives will help you gain the certification.
What you will learn:
You will also get:
Examining the Product Owner Role
1.1. … describe the impact on a Scrum Team and organization of at least three anti-patterns that might exist for Product Owners and relate one to your organization or Scrum Team. For example: 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 delivery team; leaving everything ambiguous, letting the team figure it out with no input; telling the team how to do their job; the organization assigns “proxy Product Owners” that don’t have authority to reorder; the organization has technical Product Owners for customer-facing products; a “part time Product Owner” who is attempting to fill the role while doing another job.
1.2. … analyze how you as a Product Owner help the organization realize value through delivering product solutions that delight customers and users within the constraints of technical feasibility, organizational context, and regulatory requirements.
1.3. … discuss the skills and capabilities needed for a Product Owner to collaborate as a member of a cross-functional Scrum Team in order to create successful products.
1.4. … explain the role of the Product Owner and at least three of the benefits of mastering the role.
1.5. … illustrate why Scrum and product ownership is important for you.
Working with Stakeholders
1.6. … identify at least four major stakeholder groups and describe how a Product Owner may interact with them during the development cycles (e.g., customers, sponsors, users, service, team members, customer support, training, governance (audit, compliance, risk), managers, infrastructure, security, architecture, etc.).
1.7. … discuss three questions that will help you identify that you are working with the key stakeholders you need. Example questions: Can you clearly identify what you want from the stakeholder? Can you exist without or easily replace the stakeholder? 2 scrumalliance.org
1.8. … using two concrete examples, recognize when the Product Owner should not act as the facilitator for the stakeholders (i.e., emotional conflict, impediment to creativity, lack of facilitation skills, too invested in the outcome of the discussion to be impartial).
1.9. … demonstrate at least three facilitative listening techniques (e.g., paraphrasing, mirroring, making space, stacking, etc.).
1.10. … list at least three alternatives to open discussion (e.g., structured go-arounds, individual writing, listing ideas, dialogue in pairs or small groups, etc.) and demonstrate the use of at least one of them.
1.11. … identify at least three indicators when a group is engaged in divergent thinking and at least three indicators where a group is engaged in convergent thinking.
1.12. … identify at least three challenges of integrating multiple frames of reference.
1.13. … describe at least three ways a group of stakeholders could reach their final decision (e.g., fist of five, decider protocol, majority vote, etc.).
1.14. … practice a product backlog ordering session with multiple stakeholders.
1.15. … debate the importance of various stakeholders participating in sprint review meetings (e.g., CEO, external customer, head of engineering, other teams, etc.).
1.16. ...demonstrate at least three techniques for engaging with stakeholders on a regular basis. For example, product backlog refinement, roadmapping, release planning, qualitative market research, Sprint Reviews, observe Daily Scrums, etc.
Working with the Development Team
1.17. … define technical debt and explain why the Product Owner should be cautious about accumulating technical debt (e.g., by showing how technical debt impacts the capacity of the team over time, the increase of cost for addressing technical debt too late, using the “Debt Quadrant” by Martin Fowler).
1.18. … list at least five practices (e.g., from extreme programming: test-driven development, pair programming, continuous integration, collective code ownership, refactoring) that will help Scrum Teams deliver a high-quality product increment and reduce technical debt each sprint.
1.19. … list at least three ways technical practices may impact the Product Owner’s ability to maximize business value each sprint (e.g., continuous integration allows early feedback, pairing speeds up understanding and reduces documentation effort, TDD improves quality and reduces rework and regression testing time).
Product Ownership with Multiple Teams 1.20. … list at least three scaling frameworks or approaches (LeSS, DAD, Enterprise Scrum, etc.).
1.21. … describe how at least two large-scale participatory meeting formats (Open Space, World Cafe, Review Bazaar) might be adapted to scale Scrum meetings.
1.22. … question the benefits of managing dependencies when compared to reducing/removing dependencies.
1.23. … illustrate at least three techniques for visualizing, managing, or reducing dependencies between teams.
1.24. … describe at least three benefits and drawbacks of feature teams and component teams
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.
The instructor was highly knowledgeable and able to provide real-world use cases of Python so that we could use it in professional scenarios effortlessly.
Attended Advanced Certified Scrum Product Owner™ (A-CSPO™) workshop in March 2018Good training!
Attended Advanced Certified Scrum Product Owner™ (A-CSPO™) workshop in January 1970It was very helpfull
Attended Certified ScrumMaster®(CSM) workshop in February 2018The coach Mr. Nanda had absolutely great knowledge about Agile and Scrum processes.
Attended Certified ScrumMaster®(CSM) workshop in January 2018This A-CSPO course is targeted at people already experienced with Scrum and the Product Owner role and existing CSPOs.
To earn an Advanced CSPO, you must have an active CSPO® certification with Scrum Alliance®, in addition to demonstrating at least one-year work experience specific to the role of Product Owner.
This course uses a blended approach to learning. The primary purpose of competency-based learning is accumulation, practice, reflection, and validation of relevant knowledge, skills, and abilities. This can be done through face-to-face or online training, partial self-study and assessment, mentoring, coaching, or any combination of the above modes.
Yes. The required work experience can be met before, after or during the course of your A-CSPO training. Your education component can be completed while you earn work experience as a Product Owner. Remember that you will need to enter at least one year of your Product Owner work experience on your Scrum Alliance dashboard in order to gain the A-CSPO certification. Go here to find Advanced Product Owner educational offerings.
The A-CSPO™ credential is good for two years. The process for renewal of the credential is still being determined by Scrum Alliance.
An A-CSPO™ certification validates your knowledge as an expert on Scrum processes, terminologies, ceremonies and principles. Not only this, it allows you to better perform within your team and organization to deliver great products and business value. It allows you to make your resume more marketable and distinguish yourself in the marketplace. Stand out among your peers and project yourself as a highly valued professional.
Your instructors are Certified Scrum Alliance trainers who have years of industry experience.
Any registration cancelled within 48 hours of the initial registration will be refunded in FULL (please note that all cancellations will incur a 5% deduction in the refunded amount due to transactional costs applicable while refunding). Refunds will be processed within 30 days of receipt of written request for refund. Kindly go through our Refund Policy for more details: http://www.knowledgehut.com/refund
Please send in an email to support@knowledgehut.com, and we will answer any queries you may have!
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
