Scrum Product Owner (SPO) Training in Evansville

Enroll in or hire us to teach our Scrum Product Owner (SPO) class in Evansville, Indiana by calling us @303.377.6176. Like all HSG classes, Scrum Product Owner (SPO) may be offered either onsite or via instructor led virtual training. Consider looking at our public training schedule to see if it is scheduled: Public Training Classes
Provided there are enough attendees, Scrum Product Owner (SPO) may be taught at one of our local training facilities.
We offer private customized training for groups of 3 or more attendees.

Course Description

This dynamic course is filled with practical exercises and real world examples. Experienced Scrum practitioners will walk away with ideas for improving their Scrum practices and students brand new to Scrum will gain a solid understanding of how to get started. Similar to the SM course, the SPO class also goes deeper on the topics more related to the role of the Product Owner. More emphasis on the PO role in Scrum with topics such as using a Vision Statement to guide the Team, creating a Product Roadmap, and Release Planning. Learn about the maintenance of the Product Backlog and practice writing User Stories using user roles and personas.
Course Length: 2 Days
Course Tuition: $1150 (US)


This class is appropriate for beginners who are just learning and for people who have been using Scrum for a while and trying to learn new ideas on how to do it better. Ideal learners would be Business Analysts, Project Managers, Product Managers, Business Managers, Executives, and anyone seeking to understand the Product Owner Role and learning the benefits that Scrum can bring to the business.

Course Outline


What is Agile?

  • The Agile Manifesto and principles
  • Scrum and Agile; what’s the difference?


  • The history and framework
  • The five Scrum values and the benefits
  • Empirical Process vs. Defined Process

The Roles of the ScrumMaster, Product Owner, and Team

  • Responsibilities of each
  • Team self-organization
  • Who should play the roles


Sharing the Vision

  • Working with Stakeholders
  • Using a Roadmap
  • Creating a Release Plan


The Scrum Meetings

  • Their purposes
  • The duration and invitees
  • The value of each
  • Estimating and planning


The Scrum Artifacts/Documents

  • Building your Product Backlog
  • Understanding the Sprint Backlog
  • Interpreting the Burndown/Burn-up charts


Product Backlog Items

  • Writing and working with User Stories
  • Understanding and creating Acceptance Criteria
  • Prioritizing your stories
  • Grooming your Product Backlog
  • Accepting or Rejecting the work

Course Directory [training on all levels]

Upcoming Classes
Gain insight and ideas from students with different perspectives and experiences.

Agile/Scrum Uses & Stats

Agile/Scrum is Used For:
Project Management Processes Maintenance Iteration
Year Created

Faster Deployment of Solutions
Because there is a continuous collaboration between stakeholders and teams, the focus on the essentials speed up the delivery process.

Gives Every Team Member a Purpose
People own and are expected to deliver on their responsibilities.

Keeps the End Goal in Mind at Every Level
With the end-goal in mind, teams stay focused and unite in their efforts

Promotes Flexibility in Order to Adapt
Close team and customer contact prompts acceptance of change, and frequent deliverables.

Faster Detection of Issues and Defects
Scrum methodology incorporates daily meetings, which helps to identify problems and resolving them in time.


Can Act As a Band-Aid to Bigger Problems
Agile has been the go to cure-method for larger issues that most of the time organizations are not able to deal with because they don’t have a neutral party to facilitate their corporate patterns, practices, policies and culture.

Can Create a Micro-Managed Environment
Practiced incorrectly, a project manager may not want to give up control and neutralize any real decision making from the team.

Not Everyone Is On Board
Although project teams may be ready for agile development, the rest of the company may not always be easily absorbed within larger more traditional organizations where there are significant amounts of rigidity or flexibility within processes, policies, or teams.

Push for Higher Performance
The push for a higher performance is even more relentless than in traditional, procedural organizations that have rigid processes or operating methods.

Not Well-Suited for Every Project
Agile may not work as intended if a customer is not clear on goals, the project manager or team is inexperienced, or if they do not function well under significant pressure.

Agile/Scrum Job Market
Average Salary
Job Count
Top Job Locations

Agile and SCRUM methodologies are practiced mostly in larger organizations that have cross-platform teams that need to be on the same page. Adoption rates vary in different industries. 


Industry                       Agile Adoption Rate

Software (ISV)               23 percent

Financial services          14 percent

Professional services     12 percent

Insurance                        6 percent

Healthcare                      6 percent

Government                    5 percent

Telecoms                         4 percent

Transportation                 4 percent

Manufacturing                 4 percent

Complimentary Skills to have along with Agile/Scrum

Agile Methodologies and Frameworks include:

ASD - DevOps - DAD - DSDM - FDD - IID - Kanban - Lean - SD - LeSS - MDD - MSF - PSP - RAD - RUP - SAFe - Scrum SEMAT TSP UP XP

The Standards and Bodies of Knowledge Include:

BABOK - CMMI - IEEE standards - ISO 9001 - ISO/IEC standards - PMBOK - SWEBOK - ITIL

Interesting Reads Take a class with us and receive a book of your choosing for 50% off MSRP.