WHY AGILE?

• Schedule slips

• Project cancellation

• Quality spiral death

• High defect rate

• Business misunderstood

• Staff turnover

Let's find a metaphor...

Adaptation:

1 week

2 weeks

2 weeks

6 weeks

3 weeks

On Top of Everything

1 week

2 weeks

2 weeks

6 weeks

3 weeks

1st week

of the most important feature

2nd week

of the next important feature

3rd week

of the next valuable feature

4th week

of the next feature

 OK AGILE...
BUT HOW?

PLANNING

RELEASE PLAN
EPICS

STORIES

TASKS

CYCLE

The goal is to know what problems we will solve

YOU NEED TO BE PART OF SCOPING...

PRODUCT THINKING

Content Blocks

CYCLE

The goal is to know what problems we will solve

• Focuses on the problem and not the solution

• Negotiable, scope can be changed

• Expresses real customer value

• Splittable to multiple stories

• Framed from the user’s perspective

HOW TO WRITE GOOD

HOW TO WRITE GOOD

• Incrementally bring customer value
  (even if it's small and temporary)

• Items can be swapped or replaced

• Have realistic milestones with clear acceptance criteria, and business value

AT THE END OF THE CYCLE PLANNING

• We know what problems we will solve and make a commitment to deliver a solution for them

• We have estimations for the solutions

• We have a high-level backlog for the cycle with epics and stories for at least the first few weeks

ITERATION

The goal is to know how
and when we will solve a  committed problem

ITERATION

The goal is to know how and when we will solve a committed problem

EPIC

PROBLEM 1

EPIC

PROBLEM 2

EPIC

PROBLEM 3

WHAT IS LIKE A GOOD

• Have customer value
  (even if it's small and temporary)

• Phrased from the customer perspective

• Possibly optional, independent

• Small enough to fit 2-3 stories in an iteration

• It's small enough to be able to make a good enough estimation

HOW TO WRITE A GOOD

• Have a short and precise name or identifier
  Eg. "Feedback button on report page"

• Then add details:

  • Whose problem is solved by this story?

  • What problem is addressed in the story?

  • Why to do that? What is the value?

• ​One template:
  ​“As a <particular class of user>, I want to <be able to perform/do something> so that <I get some form of value or benefit>”

HOW TO WRITE A GOOD

• It has clear acceptance criteria

  • Precise, reproducable steps how to check the completeness of the story

  • ​Understandable and possible checkable by the PM

EPIC

PROBLEM 1

EPIC

PROBLEM 1

• Implementation steps

• Sometimes technical details

• Guide the development

• Usually not interesting for the PM

• Make it clear to everyone how to implement the story

• Not too detailed, no need for code snippets

AT THE END OF THE ITERATION PLANNING

• We have a good estimation what will fit into the iteration / sprint, it's not a commitment but we do our best and learn if we failed to deliver

• We know what we will demo

• Everyone understands the stories so anyone can grab any story and start working on that

NOW IT'S YOUR TURN!

TASK

Create a product plan with epics  and split them into stories. Create also a release plan for them.

Work in teams

I will be the Product Manager :)