Scrum Product Owner Professional By SCRUMVersity in Martinique

• Sl. No.
• Chapter

• Chapter - 1
• INTRODUCTION TO AGILE / SCRUM

• Chapter - 1.1
• What is Agile

• Chapter - 1.2
• Agile Manifesto

• Chapter - 1.3
• Definition of Scrum

• Chapter - 1.4
• Scrum History

• Chapter - 1.5
• FIVE values of scrum

• Chapter - 1.6
• Scrum Values defined

• Chapter - 1.7
• Scrum values and behaviors

• Chapter - 1.8
• Scrum Characteristics

• Chapter - 1.9
• Scrum Roles

• Chapter - 1.10
• What is the difference between Agile & Scrum

• Chapter - 2
• WHY AGILE

• Chapter - 2.1
• Agile Manifesto

• Chapter - 2.2
• Empirical process control

• Chapter - 2.3
• Defined process control

• Chapter - 2.4
• Why is scrum empirical process control

• Chapter - 2.5
• The Big Picture

• Chapter - 2.6
• Delivering Value Early & Often

• Chapter - 2.7
• Faster Turnaround Time & Shorter Feedback Cycle

• Chapter - 2.8
• Scrum Team Composition - Engineering Team (Dev+QA, Product Owner, Scrum Master)

• Chapter - 3
• Product Owner Basic

• Chapter - 3.1
• Understanding Product Owner role

• Chapter - 3.2
• What is the role in scrum

• Chapter - 3.3
• A good product owner

• Chapter - 3.4
• Product owner success

• Chapter - 3.5
• Responsibilities

• Chapter - 3.6
• Understanding Product vision

• Chapter - 3.7
• Vision Boards

• Chapter - 3.8
• What is the problem we are trying to solve

• Chapter - 3.9
• What value is it going to provide to the end user

• Chapter - 3.10
• The Big Picture (Product roadmap)

• Chapter - 3.11
• Product Visualization / Preparing Product Plan

• Chapter - 3.12
• Prepare/ walk through a case study to explain product plan creation

• Chapter - 3.13
• UX-UI design in product

• Chapter - 4
• Product backlog ownership

• Chapter - 4.1
• Product backlog creation

• Chapter - 4.2
• Creating work flows from Use cases

• Chapter - 4.3
• What is backlog and how to create it

• Chapter - 4.4
• how much details

• Chapter - 4.5
• Emergence and how to handle it

• Chapter - 4.6
• Progressive refinement

• Chapter - 4.7
• Story formats – Problem statement, Description, Acceptance Criteria

• Chapter - 4.8
• Identifying stories from Use cases & Work flows

• Chapter - 4.9
• Story Sizing – How many acceptance criteria per story?

• Chapter - 4.10
• Identifying dependencies

• Chapter - 4.11
• prioritization and Backlog Grooming

• Chapter - 4.12
• Relative weighting

• Chapter - 4.13
• Feature scoring

• Chapter - 4.14
• Business value

• Chapter - 4.15
• Time boxed stories. What/ Why?

• Chapter - 5
• Release Planning

• Chapter - 5.1
• Estimation

• Chapter - 5.2
• What do you as PO need know for estimates

• Chapter - 5.3
• Basic Principles

• Chapter - 5.4
• Accuracy in estmation

• Chapter - 5.5
• Estimate Size & velocity , Effort vs Accuracy

• Chapter - 5.6
• What is a good Plan

• Chapter - 5.7
• Planning

• Chapter - 5.8
• Release Planning

• Chapter - 5.9
• Technical Debt / Bugs prioritization

• Chapter - 5.10
• Mid sprint – Reviews / Handling spill over

• Chapter - 5.11
• Velocity

• Chapter - 5.12
• Understanding “Velocity”

• Chapter - 5.13
• Incorporating feedback from Retrospectives

• Chapter - 6
• Product Feature acceptance

• Chapter - 6.1
• Defining – Definition of done

• Chapter - 6.2
• Story acceptance

• Chapter - 6.3
• When / Where / How

• Chapter - 6.4
• Customer reviews / communication