Professional Scrum Product Owner Training in Fayetteville

Enroll in or hire us to teach our Professional Scrum Product Owner class in Fayetteville, North Carolina by calling us @303.377.6176. Like all HSG classes, Professional Scrum Product Owner 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, Professional Scrum Product Owner may be taught at one of our local training facilities.
We offer private customized training for groups of 3 or more attendees.

Course Description

 

In the Professional Scrum Product Owner course, explore and learn to apply the accountabilities of the Product Owner and the principles of Professional Scrum. Gain an understanding of the pivotal role the Product Owner plays in bridging strategy and agile product management in order to help the Scrum Team create valuable products.

Course Length: 2 Days
Course Tuition: $790 (US)

Prerequisites

Course Outline

 
Agile Product Management
Reasons to Pursue Agility
Agile Product Managers Have a Product
Mindset
The Bigger Picture
Product Management Activities
Product Management Encapsulates Many
Things
Product Owner Is an Agile Product Manager
An Entrepreneurial Product Owner
Techniques for Modeling Business Strategy
Business Model Canvas
Lean Canvas
Value Proposition Canvas
Business Strategy
Boiler Plate Warning
Techniques For Creating A Product Vision
Innovation Games Product Box
Product Vision Template
Business Problem Statement
Product Owner and Technology
Strategic Alignment Index
Discontinuing Products Is Not What Kills You
 
Value-Driven Development
What is value?
For organizations, value is…
Delivering Value
A Release Is Needed to Realize Value
Traditional Development Delays the Realization of Value
Business Value Over Time
Business Value Over Time – Optimized
Delivering Value
How do you measure?
Information Value Neutrality
The Right Metrics
Value Measures
Product Variations
Innovation Rate
On-Product Index
Usage Index
Securing Success by Securing Scope?
Installed Version Index
The Right Metrics
 
Scrum Theory & Empiricism
When Will It Be Ready?
The Complexity of Product Development
The Predictability of Product Development
The Complexity of Product Development
Situation Dictates the Type of Process
Empirical Processes Require Trust & Courage
Scrum Values
Take Away – Scrum Theory & Empirical Process Control
 
The Scrum Framework
Definition of Scrum
What is needed for Scrum?
Roles: Each One Has a Specific Accountability
Fitting the pieces together
Roles, Artifacts and Events in the Scrum Framework
Exploring the purpose of a Product Owner
The Rewrite Fallacy
Key Points for the Product Owner
Key Points for the Product Owner
The Product Owner / Development Team Relationship
Stakeholders – Who Are They and What Do They Want?
What Is a Scrum Sprint?
Sprint Goal
Some Sprint Goals
Sprint Planning Meeting Flow
Product Owner and Sprint Backlog
Attributes of a High-performing Team
Cancelling a Sprint
A Sprint is a Feedback Loop
Flow of the Sprint Review Meeting
Definition of “Done”
Increment Requires Transparency
Increment Grows Over Time Iteratively – Always Done
Sprint Retrospective
Can one product owner possibly do it all?
One Product Owner Can Do It All, with Help and Thought
Product Owner Role
 
Product Backlog Management
Levels of Specification
Characteristics of a Product Backlog
Use Product Backlog to Maintain a Roadmap
Managing the Vision, Value and Validation Flow using Kanban
Valid Product Backlog Items
The Three C’s of User Stories
User Story
Popular User Story Template
If Not Precise Enough, Split Them
Refined to Ready
Acceptance Criteria
A/B Test and Technical Spike
Story Mapping
Create a Product Backlog
Product Backlog Supports Emergent Architecture Development
Architecture Changes
How Do You Prioritize Work?
Product Backlog Order Influenced by Many Factors
Techniques for Product Backlog Ordering & Value
Product Backlog Ordering
Map Product Backlog Items to Value Proposition
 
Release Planning
A Release Serves to Actually Deliver Value
Some Reasons Are Better Than Others
Release Strategies
Customer Absorption Is One Constraint
Build Plan as Needed
Techniques for Estimating Product Backlog Size
Estimating Size
Velocity Is an Option to Measure Progress
When Will Item “A” Likely Ship?
Monitoring Progress and Uncertainty
Undone Work & Technical Debt
The impact of Technical Debt on future Value
Good Velocity
Refinement
 
Closing

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
Difficulty
Popularity
Year Created
2001
Pros

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.
 

Cons

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
$89,553
Job Count
n/a
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.