Logo

dev-resources.site

for different kinds of informations.

Rose bushes and story points

Published at
5/18/2022
Categories
agile
scrum
storypoints
estimation
Author
jhall
Author
5 person written this
jhall
open
Rose bushes and story points

Yesterday my wife asked me to dig a hole in the garden so she could plant a rose bush. No sooner had I grabbed the spade than my 16-month-old son came over to help.

A few minutes, and a scraped knee later, we had successfully dug a hole.

This got me thinking.

A task that normally would have taken me about a minute, tops, took about 3 minutes. And I probably exerted double the effort, since rather than just moving some soil, my concern was moving soil slowly and deliberately in a way that gave my son a sense of participation. And my son exerted significant effort of his own.

As I’ve been thinking about story points lately, I saw a parallel.

Had I estimated the hole-digging task before hand, perhaps I would have assigned it a value of 1 story point.

But with my son involved, how does that affect my estimate? Let’s consider three options:

  1. 1 Story Point It’s the same task, whether I do it alone, or with the help of a trainee
  2. 3 Story Points By involving a trainee, we can expect the task to take 3x longer
  3. 8 Story Points To reflect the aggregate effort and increased complexity that comes from involving a trainee

I find this an interesting thought experiment, because whatever answer I come up with, I can see it conflicting with common advice about story points. If I say 1 story point, because the task is the same, then I’m admitting that story points don’t really reflect effort or complexity—a trope we hear constantly.

If I say 3 story points, then I’m essentially saying that story points are just translated to time. While this makes a certain sense, especially when trying to estimate for the sake of business schedules, it also violates the common trope that “story points do not equate to time!”

So 8 story points it is, right? But this makes our estimates entirely subjective, depending entirely on who is doing the work. It also makes comparison of story points (whether over time, which is often an anti-pattern anyway), or just relative estimation much harder, because like stories won’t have like story point values.

What do you think? I’m running a poll on LinkedIn, and your feedback is welcome!


If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

estimation Article's
30 articles in total
Favicon
Practical Approaches to Accurate Project Estimation
Favicon
The Importance of Accurate Cost Estimation in Construction Projects
Favicon
Emmision CO2 of a cat and a dog with python
Favicon
Top Project Cost Estimation Software Solutions for Accurate Budgeting & More
Favicon
Estimating Coding Tasks: What Could Go Wrong?
Favicon
Software Estimation Techniques
Favicon
Seniority in Tech: Beyond Technical Skills
Favicon
How we estimate tasks in Story Points
Favicon
Best Construction Estimating Services in USA Canada
Favicon
Nobody knows how to estimate software projects
Favicon
A developer's guide to estimation
Favicon
Seeing JavaScript Math.random Not Be So Random
Favicon
Flow Metrics Book Review
Favicon
My new POV on Story Points — a lesson in task estimation
Favicon
Predictability is overrated
Favicon
The Woes & Reliefs of Technical Recon
Favicon
Project Estimation - how to prepare for project implementation
Favicon
Rose bushes and story points
Favicon
How to release 2 years of unfinished code, the "Agile way"
Favicon
A Simple Estimation Exercise
Favicon
So do you expect me to write a blank check?
Favicon
Story Points means Relative Estimation, right? Not so fast.
Favicon
Three Bears Estimation
Favicon
The thing with agilists and deadlines
Favicon
Uncertainty increase development effort
Favicon
Estimates are not metrics
Favicon
Effective Estimation by Uncle Bob
Favicon
How to Become Better Software Estimator?
Favicon
Step by step estimation guide
Favicon
How to Estimate Anything Quickly

Featured ones: