Scribd
Upload
27 views39 pages

User Story Estimation: Point

This document introduces a new method for estimating the effort required for user stories called User Story Point (USP) estimation. The USP method is presented as being more consistent, reliable and structured than traditional story point estimation techniques. The USP method involves two main steps: 1) calculating a productivity factor based on characteristics of the team and project, and 2) assigning a complexity score to each user story based on defined complexity factors and calculating the story points by multiplying the complexity score by the productivity factor. Advantages of the USP method include being more objective, repeatable and adaptable to changes than traditional velocity-based estimation.

Uploaded by

Cesar Bedoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
27 views39 pages

User Story Estimation: Point

This document introduces a new method for estimating the effort required for user stories called User Story Point (USP) estimation. The USP method is presented as being more consistent, reliable and structured than traditional story point estimation techniques. The USP method involves two main steps: 1) calculating a productivity factor based on characteristics of the team and project, and 2) assigning a complexity score to each user story based on defined complexity factors and calculating the story points by multiplying the complexity score by the productivity factor. Advantages of the USP method include being more objective, repeatable and adaptable to changes than traditional velocity-based estimation.

Uploaded by

Cesar Bedoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 39

USER STORY

POINT
ESTIMATION
Hello!
I am Fred Heath

Developer, Problem solver, Ruby


evangelist, Agile practitioner.

You can find me at:


@FredAtBootstrap
bootstrap.me.uk
“
There is currently no standard unit
of measurement in software
development
What’s this all about

○ Current estimation methods not fit for


purpose
○ A new structured, empirical way
introduced: USP estimation

USP = User Story Point


4-
easy
4-
Not to easy
me - 16
but, look
here……
…………..
easy, see?
I suppose
you’re
right,
4 then!
What went wrong

Environmental Technical factors Human interaction


factors ignored ignored factors ignored
Ben unfamiliar with Asynchronous Jerry charismatic and
project, programming processing is influential leader. Peer
language and inherently complex, pressure always wins.
application domain. setup is not trivial.
Key problems with story points

○ Inconsistent

○ Subjective

○ Unreliable
Velocity Assumptions

○ Stable previous velocity


○ Team doesn’t change
○ Sprint duration doesn’t change
○ Initial planning session is inerrant
○ Technology / platform doesn’t change
○ Individual productivity doesn’t change
USER STORY POINT ESTIMATION

A consistent, reliable, structured, empirical


estimation method
Use Case Point
Estimation

for Object-Oriented, Use-Case


based development
Use Case Points

Environmental Technical Factors (TF) Use Case complexity


Factors (EF) Complex algorithms, (UUCP)
Project familiarity, concurrency, cross- Simple, average or
application experience, platform support, etc. complex
motivation, language
complexity, etc.

Use Case Points = UUCP * TCF * ECF


UCP References
1. Karner, G, 1993, “Metrics for Objectory”. Diploma thesis, University
of Linköping, Sweden. No. LiTHIDA-Ex-9344:21. December 1993.
2. Smith, John, 1999, “The Estimation of Effort Based on Use-Cases.
Rational Software.Cupertino, CA.TP-171. October 1999.
3. Anda, Bente, D. Dreiem, Dag Sjøberg and Magne Jørgensen, 2001,
“Estimating Software Development Effort Based on Use-Cases -
Experiences from Industry”, The Unified Modeling
Language.Modeling Languages, Concepts, and Tools, 4th
International Conference, Toronto, Canada, October 1-5, 2001,
LNCS 2185
4. Roy Clem, Project Estimation with Use Case Points,
http://www.codeproject.com/KB/architecture/usecasep.aspx
USP - STEP 1
PRODUCTIVITY
FACTORS
Productivity Factors
1.5

0.5

1.5

-1

-1

-2 -1 0 1 2
Total Impact
= F1 weight * F1 score
+ F2 weight * F2 score
+ F3 weight * F3 score
+ F4 weight * F4 score X
+ F5 weight * F5 score
+ F6 weight * F6 score
+ F7 weight * F7 score
+ F8 weight * F8 score
P FACTOR

PF = 1.4 + (-0.03*Total Impact)


USP - STEP 2
USER STORY
COMPLEXITY
COMPLEXITY FACTORS
Factor Name

Distributed or Parallel
A1
processing
A2 Concurrency

A3 High Performance

B1 Reusability & Modularity

Complex internal
B2
Processing
COMPLEXITY FACTORS
(cont’d)
Factor Name

B3 Ease of Use

B4 Cross-Platform Support

Complex Setup or
B5
installation
Extensibility &
B6
Compliance

B7 Security
USER STORY COMPLEXITY

Complexity Condition USCP

Simple No complexity factors apply 5


Average 1-2 B factors, but no A factor 10
apply

Complex At least one A factor, or 15


more than 2 B factors, apply
USER STORY POINTS

USP = USCP * PF
PRODUCTIVITY FACTORS
Name Weight Score Impact

Project Familiarity 1.5 4 6

Application Experience 0.5 4 2

Proramming paradigm
1 5 5
experience

Team Cohesion 1 4 4
PRODUCTIVITY FACTORS
Name Weight Score Impact

User Story Robustness 1.5 5 7.5

New team-members -1 3 -3

Proramming language
-1 3 -3
complexity

Motivation 1 5 5

TOTAL IMPACT = 23.5


P FACTOR

PF = 1.4 + (-0.03*23.5)
= 0.695
User Story

Epic: “As a user, I want to backup my hard


drive.”

Story: “As a power user, I can specify files or


folders to backup based on file size, date
created and date modified.”

USCP = 10
USER STORY POINTS

USP = 10 * 0.695
= 6.95
USP ADVANTAGES

○ Objective

○ Repeatable

○ Quick to apply

○ Adaptable to change
“
The greatest gift is the power to
estimate things at their true worth.

Francois de la Rochefoucauld
CREDITS

Special thanks to all the people who made and released these awesome
resources for free:
○ Simple line icons by Mirko Monti
○ E-commerce icons by Virgil Pana
○ Streamline iconset by Webalys
○ Presentation template by SlidesCarnival
THANKS!
Any questions?

You can find me at:


@FredAtBootstrap
[email protected]

You might also like