Benzne webinar Story writing is an Art, Estimation is science

Benzne Agile Series:
Story Writing is an Art,
Estimation is Science

© Benzne. All rights reserved
2
AgileITSM
AI
Design
Thinking
Culture
Lean
Kanban
Visualization
DevOps
CI/CD Scrum
SAFe
XP
Cloud
Analytics
Mindset
People
Process
Technology
Data

3
Anuj M Ojha
10+ years Agile experience
6+ Orgwide Agile Transformation
Journeys
8000+ People Trained
80+ teams coached across multiple
Geographies
Special area of interest has been
bringing in business agility,
appropriate mindset & enriching
Culture.
© Benzne. All Rights Reserved.

‘Why writing a user story is an art?’
Let’s Explore
4

5
The expression or application
of human creative skill and
imagination is the creation of
aesthetic objects,
environments or experiences,
that can be shared with
others.
So, are the stories :)

User stories &
rest of all
6

What’s life without a little CHAOS?
7
STORIES

Not to ignore...
8
IRON TRIANGLETIMELINE VIEWS

What are stories by the way?
9

Why should requirements be in form of stories?
10
Because our outcome impacts PERSONAS

We need to ‘know’ them..
Who they are? Why are they concerned? What? When? Where? How? How much?
11

And also know that their stories will change.. Very often
12

How are we going to do it?
13
Let’s explore a DISCOVERY session

Story Map - Our outcome will look like this..
14
Collect the
Ideas Goal setting Persona
Mapping
User journey Story Mapping MVP
identiﬁcation
Now - Next -
Later

Product Vision is also as a Story
15

Personas
16

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

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

Product Owner’s Toolbox
Story Writing Prioritization Estimation
Epic Name Story Id As a I want So that Acceptance
Criteria
Assumptions MoSCoW Value Point Risk Point Story point
A A.1
A A.2
A A.3
A A.4
B B.1
B B.2
B B.3
20

This is how a Product Roadmap Plan looks like
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
21 © Benzne. All Rights Reserved.

Timeline View - Program Increment/ Release Roadmap
22

And all that matters..
23

‘Why estimation is science?’
Let’s Explore
24

Science of Estimation
25

In terms of Project Mgmt
26
● Suppose, size of the backlog is 1000 SP, and the team can ﬁnish 100 SP in each sprint then it will take
10 sprints of time to ﬁnish the project,
● 1000 SP (Distance) / 100 SP (Velocity) = 10 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

Relative Sizing
27

Estimation
28
As much you could know MoSCoW
Work Item 1 Must
WI 2 Must
WI 3 Must
WI 4 Must
WI 5 Must
WI 6 Must
WI 7 Must
WI 8 Must
WI 9 Must
WI 10 Should
WI 11 Should
WI 12 Should
WI 13 Should
WI 14 Should
WI 15 Should
WI 16 Could
WI 17 Could
WI 18 Could
WI 19 Could
WI 20 Could
20 stories 9M+6S+5C
Story points (SP) = Complexity * Uncertainty * Effort
Columns are STORY POINTS STORY WALL// Bucket List Technique
Base Story = Simple * Certain * Small
0 0.5 1 2 3 5 8 13 20 40 100 ?
WI 7 WI12
Scenarios Stories A B C D E Estimate Observation Happens
Sc 1 WI 12 3 3 3 3 3 3 BINGO 1%
Sc 2 WI 15 3 5 3 5 3 5 Min & max are neighbours 30%
Sc 3 WI 5
13 8 5 8 13
13
Min & max are not
neighbours
45%
8 8 8 8 13
Sc4 WI 19
3 5 8 3 3
83 13 8 5 3

Have you thought of using variance, APV & standard deviation?
Legends Team A Team B Team C Team D Team E Team F
S#1 1.2 0.7 0.5 1 1 1
S#2 1 1.1 1.3 1 1.8 0.5
S#3 0.8 1.5 0.7 1 1.5 1.5
Upper Control limit 1.2 1.2 1.2 1.2 1.2 1.2
Lower Control Limit 0.8 0.8 0.8 0.8 0.8 0.8
Average 1.05 1.10 0.83 1.00 1.43 1.00
APV 13% 30% 37% 0% 43% 33%
STDEV 0.20 0.40 0.42 0.00 0.40 0.50
plotstd (upper) 6.67% 20.00% -11.70% 0.00% 40.41% 16.67%
plotstd (lower) 33.33% 60.00% 94.97% 0.00% 40.41% 83.33%
30

Here is an interpretation.. Try to keep it under 25% percent
31

32

‘Questions’
We might help you :)
33

Thank You!
34
Outcome Driven Agile Adoption is the core of what we do.
Reach out to us for solutions.
Write at Alok@benzne.com for Free Agility Health Assessment Report
Agile Transformation - https://benzne.com/agile/
Few Customized Workshop Outlines - https://benzne.com/corporate-training/
Public Workshop Calendar - https://benzne.com/training-calender/
Benzne Agile blogs - https://benzne.com/blog/

Benzne webinar Story writing is an Art, Estimation is science

Recommended

Recommended

More Related Content

Similar to Benzne webinar Story writing is an Art, Estimation is science

Similar to Benzne webinar Story writing is an Art, Estimation is science (20)

More from Tarun Singh

More from Tarun Singh (17)

Recently uploaded

Recently uploaded (20)

Benzne webinar Story writing is an Art, Estimation is science