Product Discovery - Where Agile & Design Thinking meet!

2. 2
Product Discovery
Where Agile & Design Thinking meet!

3. © Benzne. All rights reserved
AGILE
DEVOPS
AI
DESIGN
THINKING
CULTURE
LEAN
KANBAN
VISUALIZATION
ITSM
CI/CD
SCRUM
SAFE
XP
CLOUD
ANALYTICS
MINDSET
PEOPLE
PROCESS
TECHNOLOGY
DATA

4. © Benzne. All rights reserved
Agile Transformation
Awareness Trainings
Knowing People &
Projects
Business KPIs, Metrics &
Reporting
As-Is Assessment
Presenting Findings &
Proposed Roadmap
Piloting Projects
Focused Training
Team Level
Implementation
Even Facilitation
Role Based Mentoring
On-the job coaching
Metrics & Artefacts
Qtrly Team Assessments
Explore Scaling at group
level
Leadership & Org Agility
Prepare Growth Plan
Identify & Assign KPIs
Form communities
Implement & Re-
evaluate Progress
Transition to Internal
Coaches
Handover Artefacts
Transformation
Journey
Introduction
Pilot at
Team Level
Organizational
Agility
End State
Assessment &
Closure

5. 5
Anuj M Ojha
12+ years Agile experience
7+ Orgwide Agile
Transformation Journeys
11,000+ People Trained
120+ teams coached across
multiple Geographies
Special area of interest has
been bringing in business
agility, appropriate
mindset & enriching
Culture.

6. © Benzne. All rights reserved
Product Discovery
6
Product
Roadmap
Why this
project?
(benefit to
business, value
to customer etc
Who will use? Why
will they use? How
are they getting
their work done
today? What
change we want to
bring to elevate
their experience?
What is the As-Is
journey?
Triggers? Happy &
sad moments?
What should be
their to-be
journey?
Breadth and
Depth?
Frequent
delivery goals -
MVPs?
Backlog
(stories/epics)?
Prioritisation,
estimation,
budgeting?
Identified Risks,
dependencies, 3rd
party
dependencies,
inter-team
collaboration?
Timelines?

7. This is how product development will happen
Sprint
0
Sprint
1
Sprint
2
Sprint
3
Sprint
4
Sprint
5
Sprint
6
Sprint
7
Sprint
8
Pre-
Release
Release
R
E
A
D
I
N
E
S
S
H
A
R
D
E
N
I
N
G
M
O
V
E
TO
MARKET
FEATURE 1
FEATURE 2
Planned work
item
Defects/
Incidences
New
Changes
7

8. © Benzne. All rights reserved
Release Release 1 Release 2 Release 3
Sprints Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Sprint 9 Sprint 10 total 10 sprints
Sprint Goals Repurpose the goals as per the team's capacity and situation at that time
Avg Velocity 25 25 25 25 25 25 25 25 25 25
Backlog size - 250
sp
EPIC A A.1 A.3 A.4 A.6
100 sp
A.2 A.5 A.7
A.8
EPIC B B.1 B.2 B.4 B.5 B.6
80 sp
B.3 B.7
B.8 B.9
EPIC C C.1 C.3 C.4 C.6 C.8 C.9
70 sp
C.2 C.5 C.7 C.10
Product Roadmap | Timeline View

9. A sample blueprint of agile project kickstart
1
Business Case
Identifying the business
benefits, value to customers
2
Forming the Agile
POD & training
Based on understanding
the current team
structure, we finalise the
roles & start grooming
them
3
Visioning
Effective vision statement
is the key
4
Identify Persona &
draw Empathy
Map
To know the end users
and their current
working state
5
Identify User
Journey
To understand the As-Is
state and identify the To-
Be state
6
Develop Story Map
This will help us in identify
the breadth and depth of
our current product
knowledge & further lead
to development of
Product Roadmap
12
Start sprinting
Here onwards, we will
iteratively and
incrementally deliver
outcome to realise the
delivery benefits of agile
implementation
11
Sprint ZERO
activities
Setting up the event
calendar, sharing the
invites, ensuring few
sprints of clarity in place
10
Identify DOD &
DOR
Definition of Done &
Definition of Ready is
crucial for a success of
agile implementation
9
Update
tool/tracker
Update the backlog on
tools like (JIRA/Azure
DevOps etc)
8
Prepare Product
backlog, prioritise,
estimate, Timeline View
Here we do story writing
session to create a
unidirectional prioritised list
of requirements and also
estimated to know the size of
backlog
7
Identify MVP Goals
It is important to derive
the continuous releasing
aspect prioritised by
delivering maximum
value first
9
D
I
S
C
O
V
E
R
Y
K
I
C
K
S
T
A
R
T

10. Bringing it all together
Product Level
Release Level
Sprint Level
10

11. © Benzne. All rights reserved
Start with forming
your POD (example)
Skills/
Functions
Digital
(D)
Underwriting
(U)
Revenue
Assurance
(RA)
Digital
Marketing
(DM)
Vendor 1
(V1)
Vendor 2
(V2)
Members 3 2 2 1 4 2
D U
DM
RA
V1 V2
Internal team External External
One Team with who owns
end to end project
execution from initiation
to closure. They all
respect the common
Definition of Done.
ONE TEAM

12. Explaining goals by Elevator pitch - Vision Statement
12

13. Persona & Empathy Map
Know your end user. Give it a name, a face, emotions & make it REAL..
Example
● Car-seeker
○ Student,
○ Professional
○ One-way
traveller
○ Driver-in-a-
trouble
● Car-provider
○ Intercity
○ Inter-state
○ Premium
○ Affordable
13

14. Persona & Empathy Map
Sample
14

15. Discovery with entire POD
15

16. User Journey
16

17. Story Map

18. It starts with ideas & not stories
& Ideas are collected using Story-Mapping
We are here
right now..
18

19. Time to Convert bi-directional map into a Unidirectional list
BACKLOG
19

20. Let’s prioritise - Use MoSCoW or 100 point methods
20

21. This is how a Product backlog looks like..
Story Writing Prioritization Estimation
EPIC Features Story As a I want So that Acceptance
Criteria
Assumptions MoSCoW Value Point Risk Point Story point
E1 A A.1 Must
E1 A A.2 Must
E1 A A.3 Must
E1 A A.4 Should
E1 B B.1 Should
E1 B B.2 Could
E1 B B.3 Could
It could be t-shirt sizing or
story points or anything to
know the size of the
backlog
21

22. Science of Estimation
22
© Benzne. All Rights Reserved.
As much you could know MoSCoW Estimation
Work Item 1 Must 20
WI 2 Must 13
WI 3 Must 20
WI 4 Must 8
WI 5 Must 13
WI 6 Must 20
WI 7 Must 13
WI 8 Must 20
WI 9 Must 8
WI 10 Should 13
WI 11 Should 20
WI 12 Should 13
WI 13 Should 20
WI 14 Should 8
WI 15 Should 13
WI 16 Could 20
WI 17 Could 13
WI 18 Could 20
WI 19 Could 8
WI 20 Could 13
20 stories 9M+6S+5C 300 sp

23. In terms of Project Mgmt
23
© Benzne. All Rights Reserved.
● Suppose, size of the backlog is 150 SP, and the team can finish 30 SP in each sprint
then it will take 5 sprints of time to finish the project,
● 150 SP (Distance) / 30 SP (Velocity) = 5 Sprints (Time)
● Ensure, NO CHANGE should be made in the sprint duration and the team formed
● Make Sure to make the estimates more relevant,
○ It’s the development team who should estimate
○ Story points are prefered over hourly or man-days
○ Use techniques like t-shirt sizing, planning poker, white elephant to estimate
Sprints Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 5 sprints
Cost/S 20,000 20,000 20,000 20,000 20,000 100,000 $
Velocity 30 sp 30 sp 30 sp 30 sp 30 sp 150 Sp

24. © Benzne. All rights reserved
Release Release 1 Release 2 Release 3
Sprints Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Sprint 9 Sprint 10 total 10 sprints
Sprint Goals Repurpose the goals as per the team's capacity and situation at that time
Avg Velocity 25 25 25 25 25 25 25 25 25 25
Backlog size - 250
sp
EPIC A A.1 A.3 A.4 A.6
100 sp
A.2 A.5 A.7
A.8
EPIC B B.1 B.2 B.4 B.5 B.6
80 sp
B.3 B.7
B.8 B.9
EPIC C C.1 C.3 C.4 C.6 C.8 C.9
70 sp
C.2 C.5 C.7 C.10
Product Roadmap | Timeline View

26. ‘Questions’
Write to us consult@benzne.com
26

27. © Benzne. All rights reserved
Thank You!