Agile Product Management: Product Backlog: 21 Tips To Capture and Manage Requirements with Scrum (scrum, scrum master, agile development, agile software development)


Product Backlog Management Just Got Easier

In this class, you will be given a multitude of proven tips to manage your product backlog as part of an agile scrum team.

I know you will get value from this class as it gives you a full introduction to the concept of the product backlog. I then walk you step by step through the steps involved in managing a backlog. Following this, I give you tips for improving product backlog management in your team or business from the ground up. Along the way, I give you plenty of examples and give you best practices for product backlog management within agile scrum. In this class, you will learn:

A brief recap of agile and scrum principles

What is a product backlog and how is it different from traditional requirements documents

How to create a product backlog from a product from vision

What user stories are and how they are simpler for managing requirements

Concise techniques for improving your product backlog management

So let’s get started and let me teach you how to improve product backlog management.

Table of Contents


Section 1: Introducing- Agile scrum

What is Agile Scrum?

Section 2: Introducing Product Backlog & User Stories

Product Backlog

Walkthrough: How To Create A Product Backlog From A Product Vision

Section 3: Product Backlog Management

Step 1: Convert All Ideas into User Stories

Step 2 – Prioritization

Step 3 -Estimate The Product Backlog

Step 4 – Refining and Grooming Your Product Backlog

Tips & Strategies

Tip #1: PO Should Know That He/She Will Be Expected To Present Enough Work That Can Last About Two Sprints Beyond The Current Sprint During All The Backlog Refinement Sessions For The Current Sprint

Tip #2: Avoid Scheduling Backlog Refinement During The First Or Last 20% Of The Sprint

Tip #3: The Backlog Items Must Be Fine Grained And Properly Understood By The PO For This Meeting To Flow Well. Define Initial Set Of Acceptance Tests Before The Meeting Occurs

Tip #4: Treat Every Backlog Refinement Meeting Just Like The Beginning Of Sprint Planning Meeting

Tip#5: Everyone Should Understand That Estimates Are Provisional Until A User Story Is Accepted Into A Sprint

Tip #6: Strive To Optimize Your Time During The Meeting

Tip #7: Remember That Backlog Items Are Actually A Collaboration Between The PO And The Team

Tip #8: Keep Your Eye On The Goals Of The Meeting

Tip #9: Get Volunteers For Action Items For Any Unknowns Or Big Risks

Tip #10: You’re Definitely Free To Split User Stories During This Meeting

Tip #11: Everyone Should Understand That Product Backlog Order Is Provisional Until A User Story Has Been Accepted Into A Sprint

Tip #12: Be Brave To Discuss A Couple Of Items Farther Down The Backlog

Tip #13: Let The Dev Team Review The User Stories To Be Discussed About 24 Hours Before The Refinement Session

Tip #14: Have A Mini Backlog Refinement Prior To Holding The Backlog Refinement For The Full Team

Tip #15: Track Progress Using Release Burndown Charts

Tip #16: Feel Free To Introduce Late Breaking User Stories. As You Do That, Strive To Minimize Them But Also Embrace Them As And When They Happen

Tip #17: Use One Issue Tracker and One Backlog!

Tip #18: Watch Out For Too Many Changes And Limit Your Scope

Tip #19: Ensure To Experiment With The Amount Of Refinement, Which Your Team Does

Tip #20: Ensure To Retrospect, Inspect And Then Adapt

Tip #21: Transparentize, Prioritize And Stick To The Product Vision



Preview of ‘The Scrum Master Mega Pack’

May 7th, 2016 by