Lets do 'discovery'

1. Let’s Do
'Discovery'

2. You may not find a path,
but you will find a way..
- Tom Wolfe

3. Whatever we will do, we need ‘everyone’ to participate

4. Primary Objectives (practical):
1. Identify the backlog – Scope, Cost, Time
2. Rolling wave strategy
3. Identify the commit date
Necessities to achieve the commitment confidence:
1. Scope of the backlog - summation of the stories points of all the stories
2. Predictive velocity - unit of work that confirms the maturity of team in accomplishing the DONE stories
in backlog
Why we do?

5. Structure
Collect the ideas
Goal setting
Persona Mapping
User journey
Story Mapping
MVP identification
Now - Next - Later
Story writing
Writing Epics
Writing User stories
Prioritization
Identifying Themes
Value & Risk
MoSCoW
ROI
Differentiator, Spoiler,
Table Taker,
Organizational cost
Estimation
Scope, Cost & Time
Story point estimation
Base story definition
Dependencies & Risks
Timeline View
Sprint Zero expectations

6. Step 1 - Collect the ideas
1. Prerequisite - Product Owner comes with the clarity of high-level goal or vision
that we need to achieve while the product goes in production. Also, identify the
personas and the backbone
2. Persona Mapping & User Journey discussion
3. Conduct Story Mapping Session
1. Identify breadth - Walking Skeleton & backbone (check the attached
example to understand - Orange post-its are backbone & Blue as Walking
skeleton & rest are ideas)
2. Identify depth - ideas to finish all the elements of breadth items
3. Identify NOW, NEXT, LATER as MVP1, MVP2 and Future MVPs

7. Persona Mapping
https://in.pinterest.com/pin/52706258122113556/?autologin=true

11. Step 2 : Story writing session
1. Idea is to convert ideas collected to user stories
1. Identify the stories along with the well defined acceptance criteria
2. Replace the ideas on the story mapping board with the user-stories
identified
3. Reconfirm the NOW, NEXT, LATER

12. Prioritization
1. Time to identify the byte of the burger experience which could be
candidate for Sprint 1, Sprint 2 and so on
2. Goal is to deliver maximum benefits to the customer first
3. Goal is to resolve High Risk items first which could affect value to
customer

13. Estimation
1. Either of the technique - story wall, bucket list, white elephant estimation, T-
shirt sizing to identify story points of the stories
2. Estimations are meaningful only when we have clarity on Definition of
DONE - identify that
3. Find SIZE OF THE BACKLOG - by summing the story points of all the stories
in the backlog

14. Hack Sprint planning to find predictive
velocity1. Identify list of well defined user stories
2. Do capacity planning to find an optimal hours of time that a team has during a
sprint - ensure its a productive time - that means without meetings - only work
time
3. Fill the capacity bucket with stories - by splitting stories to tasks & then planning
poker to estimate hours for tasks
4. When the bucket is full - SUM the story points of the stories in the bucket
5. Summation is - Predictive Velocity version 0.5 (say 20 story points)
6. Buffer 25% - (15 story points now) will be your PREDICTIVE VELOCITY (ver
1.0)

15. Commit date identification
1. Divide SIZE OF THE BACKLOG (say 300 story points) with PREDICTIVE
VELOCITY (say 15 story points)
2. You will NUMBER OF SPRINTS TO FINISH THE IDENTIFIED SCOPE OF
BACKLOG (300/15 = 20 sprints)
3. Sprint duration is fixed (say 2 weeks) hence you can NUMBER OF WEEKS OR
MONTHS TO FINISH THE PROJECT ( 20 sprints x 2 weeks = 40 weeks = 10
months)
4. You just found the potential COMMIT DATE
5. Check buffering if needed

16. Plan for the 1st MVP (NOW)
1. Your NOW of Story Map should be your immediate plan to focus on
2. Do a quick Sprint ZERO to get set GOOOOO.. :)

17. THANK YOU
www.Benzne.com
Anuj M Ojha