Autoplay
Autocomplete
Previous Lesson
Complete and Continue
Product Management :Agile Requirements using Product Backlog
Introduction
01. Introduction (1:16)
02. Pashun Consulting Intro (0:13)
03. Agile Scrum Recap (3:12)
04. What is a Product Backlog (5:05)
05. Introducing User Stories and the Product Backlog (1:46)
Section 2: Creating a Product Vision
06. What is a Product Vision (2:14)
07. How to create the Product Vision (2:59)
08. What is a vision board (6:13)
09. EXAMPLE Vision Board The Sports Website
10. EXERCISE 1
Section 3: Creating a Product Backlog Step by Step
3.1 about Product Backlog Management (0:51)
3.2 Introduction to User Stories and Acceptance Criteria (4:35)
3.3 Step 1: Convert All Ideas into User Stories (1:30)
3.4 about User Stories (5:52)
3.5 what is DEEP ? (1:09)
3.6 what is the INVEST principle ? (2:39)
EXAMPLE: Initial Product Backlog for The Sports Website
EXERCISE 2
3.7 Step 2 - Prioritization (2:32)
3.8 the importance of Prioritising the Backlog (1:40)
EXAMPLE: A Propritized Product Backlog for the Sports Website
5. EXERCISE 3
3.9 Step 3 -Estimate The Product Backlog (0:52)
3.10 how to carry out Product Backlog Grooming and Estimation (1:25)
3.11 estimating with Story Points (3:07)
EXAMPLE: An estimated Product Backlog for The Sports Website
3.12 Step 4 - Refining and Grooming Your Product Backlog (0:43)
EXAMPLE: A Refined Backlog for the Sports Website
EXERCISE 4
SECTION 4 - Tips 1-7
4.1 Introduction: Tips & Strategies (0:28)
4.2 how to Capture Stories in Meetings (0:43)
4.3 Tip #1: PO Should Know That He/She Will Be Expected To Present Enough Work That (0:50)
4.4 Tip #2: Avoid Scheduling Backlog Refinement During The First Or Last 20% Of The (0:22)
4.5 Tip #3: The Backlog Items Must Be Fine Grained And Properly Understood By The PO (0:42)
4.6 Tip #4: Treat Every Backlog Refinement Meeting Just Like The Beginning Of Sprint (0:19)
4.7 Tip#5: Everyone Should Understand That Estimates Are Provisional Until A User St (0:30)
4.8 Tip #6: Strive To Optimize Your Time During The Meeting (0:20)
4.9 Tip #7: Remember That Backlog Items Are Actually A Collaboration Between The PO (0:53)
SECTION 5 - Tips 8-14
how to Manage Changing Requirements (1:00)
Tip #8: Keep Your Eye On The Goals Of The Meeting (0:32)
Tip #9: Get Volunteers For Action Items For Any Unknowns Or Big Risks (0:43)
Tip #10: You’re Definitely Free To Split User Stories During This Meeting (0:17)
Tip #11: Everyone Should Understand That Product Backlog Order Is Provisional Un (0:21)
Tip #12: Be Brave To Discuss A Couple Of Items Farther Down The Backlog (0:43)
Tip #13: Let The Dev Team Review The User Stories To Be Discussed About 24 Hours (0:39)
Tip #14: Have A Mini Backlog Refinement Prior To Holding The Backlog Refinement (0:40)
SECTION 6 - Tips 15-21
how to Prioritise for the Release (1:02)
Tip #15: Track Progress Using Release Burndown Charts (1:25)
Tip #16: Feel Free To Introduce Late Breaking User Stories. As You Do That, Stri (0:41)
Tip #17: Use One Issue Tracker and One Backlog! (0:27)
Tip #18: Watch Out For Too Many Changes And Limit Your Scope (1:22)
Tip #19: Ensure To Experiment With The Amount Of Refinement, Which Your Team Doe (0:58)
Tip #20: Ensure To Retrospect, Inspect And Then Adapt (0:28)
Tip #21: Transparentize, Prioritize And Stick To The Product Vision (1:12)
EXAMPLE: Complete example of Product Backlog: The Sports Website
6.9 Conclusion (0:50)
FEEDBACK: Reviews and Discussion
Thank you again for taking this class! (0:21)
BONUS MATERIALS
BONUS LECTURE
4.4 Tip #2: Avoid Scheduling Backlog Refinement During The First Or Last 20% Of The
Lesson content locked
If you're already enrolled,
you'll need to login
.
Enroll in Course to Unlock