• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

The un-Lean Product Backlog.

Full name

Job
email
Company
City (Country)
Time
Type of Conference
Level

Description

The un-Lean Product Backlog.
The textbook Product Backlog (5 min)

A brief overview of a basic Product Backlog composed of only with strong User Stories tightly linked to clear business objectives and estimated by business value and story points.

What’s missing? (5 min)

Creating and shipping software in large organizations involves tasks and deliverables that go beyond straightforward testing, coding and releasing. So what needs to be done to get your product in front of the user? What are we forgetting?

The Definition of DONE (10 min)

What does DONE mean? Can it be DONE within a User Story? If not, what do we do with it? We’ll explore a broader way of defining DONE in order to identify all the work needed to complete the project.

Polluting the Product Backlog (15 min)

The goal is to expose in some way this “required” work, estimate the effort needed and let it drastically affect the scope. A practical tool to accomplish this is the Product Backlog. This approach will pepper the Product Backlog with items that will in effect, pollute it. We’ll allow ourselves to create technical stories and non-functional requirements to explicitly create visibility and hopefully a sense of urgency.

Iteratively cleaning the Product Backlog (15 min)

This is where the real work starts! The Product Backlog can’t remain in this state. It’s needs to be filled, almost exclusively, with items that deliver business value. We want to create those required discussions with the Product Owner, the team and the organization as a whole and evaluate if all the items in the Product Backlog hold up the basic Lean principals.

Questions (5-10 min)

NOTE : This session can be giving in french.


Tags: