Certified Scrum Product Owner
Though each CSPO course varies depending on the instructor, all Certified Scrum Product Owner courses focus on Scrum from a product owner's perspective. Graduates will receive the CSPO designation. All CSPO course are taught by Certified Scrum Trainers.
Even projects that have solid, well-defined project plans encounter some degree of change and waste. Shifting market conditions, budget cuts, staff restructuring, or any number of influences will disrupt the best plan while contributing to customer dissatisfaction and staff discouragement. Moreover, projects that begin with changing or unclear requirements make it difficult to even establish project expectations. Scrum is the agile development process that allows teams to deliver usable software periodically throughout the life of the project, absorbing change and new requirements as the project proceeds.
As we move through the disciplines promoted by Scrum you will gain a comprehensive understanding of this agile product development framework while specifically reviewing the behaviors expected of a Product Owner. While many of us may be accustomed to the practice of establishing value and priority across projects, the Product Owner needs to consider value and priority across the features of a single project.
After successfully completing this class, participants will be registered with the Scrum Alliance as Certified Scrum Product Owners, and will have on-line access to class training materials and any updates for one year. Participants can also claim 14 PDU's with the PMI.
8-9 Jun 2010
Short, five-minute exercises and case studies will be scattered throughout the two-day session. Longer exercises are detailed below. Ample material is available for this session, and while all essential information will be covered, time spent on each topic will vary depending on the composition of the class and the interest in particular areas. A more detailed course outline is available at our website.
Agile Thinking: In order for us to understand the benefits of Scrum and the nuances behind its framework, we begin with the history of agile methods and how relatively new thoughts in software development have brought us to Scrum. “The Art of the Possible” is an opportunity to understand how small changes in behavior can have a large impact on productivity. This also turns our thinking towards new ideas and a willingness to change for the better.
The Scrum Framework: Here we’ll ensure that we’re all working from the same foundational concepts that make up the Scrum Framework. We’ll review the three areas that impact an organization most as we move ahead with Scrum and explain the different Scrum Roles, Artifacts, and Meetings.
Implementation Considerations: Moving beyond Scrum’s foundational concepts, we’ll use this time to dig deeper into the reasons for pursuing Scrum. We’ll also begin a discussion of integrity in the marketplace and how this relates to software quality.
Exercise: The 59-minute Scrum Simulation. This popular exposure to Scrum originally developed by Jean Tabaka asks us to work on a short project that lasts for just 59 minutes! We’ll walk through all of the key steps under the Scrum framework as we work in project teams to deliver a new product.
Scrum Roles: Who are the different players in the Scrum game? We’ll review checklists of role expectations in preparation for further detail later in our session.
Exercise: establishing product expectations. This is a long-running exercise where we will discuss and practice various aspects of product and project planning in an agile Scrum environment.
The Product Backlog: This section includes Product Visioning and Progressive Elaboration. The Scrum Team must have an understanding of our Product Vision so they can make good decisions, and the organization must have an understanding of our Vision to provide funding. The Product Backlog is a reflection of that Vision.
Exercise: We'll go through the initial steps of creating a "healthy" Product Backlog as we practice developing its content. Here we will begin using User Stories, guided by Bill Wake's INVEST model. This is the beginning of our project definition that will be used as part of our discussions and exercises that follow.
Velocity and Story Points: Since a Product Owner is responsible for monitoring progress, we'll discuss and practice how to measure a Team's progress in delivering product features. We'll be discussing relative effort, Planning Poke, Story Points, Ideal Team Days, and Team Capacity.
Prioritization Considerations and Methods: Prioritization is the Product Owner's number one tool for maximizing return on investment. In this section we'll review different techniques available to establish meaningful priorities, including Weighted Impacts, Theme Screening, and Kano Modeling.
References and Advanced Considerations: This section of our material acts a reference for more detailed information regarding Meetings, Artifacts, Advanced Considerations, and additional thoughts on Extracting Value from our endeavors.
Closing Topics: We’ll wrap up with direction on where to go next with your Scrum experience, some Scrum reference sites, and our graduation ceremony.
This 2-day class is suitablefor those who are responsible for setting product and financial direction on a Scrum project. While current Certified ScrumMasters can attend, this class should not be considered a next step after taking the CSM Class, but instead should be viewed as an alternative to the CSM Class.