• Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Modern Software Management

The modern way to manage software development.

  • Home
    • Welcome
    • Welcome Video
    • Recent Posts
    • Search
  • Resources
    • Textbook
    • Horizon Planning Intro
    • Horizon Planning Spreadsheet
  • Blog
  • Services
  • About/Contact
You are here: Home / Management / Episode 2: Estimation (or… why I hate “agile story points”)

Feb 14 2023

Episode 2: Estimation (or… why I hate “agile story points”)

Welcome to Episode 2! I decided I better start numbering my YouTubes, so I went back and added numbers to the previous two (including the 2 min Welcome video which seemed appropriate, and computer sciency, to be numbered at 0 – Ric Hehner would be proud).

This is building on the previous video where I went over a rough-an-ready “Horizon Plan” and used units that I called “Days” without going into any detail. Here I clarify what I mean by “Days” = Effective Coder Days, or ECDs.

I start out by saying if you can’t measure it, you can’t estimate it, so for everything I estimate there has to be an operational definition of the the thing based on how you would measure it after the fact. I use height, weight, and strength as illustrations.

I go on to talk about how to “measure” the size of software. I discuss and discard both lines-of-code and function point analysis. I say the only reasonable approach is a time-based estimate, but that “confounds” four things:

  • The “inherent size” of the work item (whatever that means).
  • Who is working on it.
  • How productive that person will be working on that thing with the time they dedicate to it.
  • How many hours of dedicated time they can put in over a period.

I say that last thing is quite easy to strip out and measure separately. I introduce the concept of workdays and work factor to convert workdays into ECDs. I explain why I’m only sizing coder time, working alone, and only up to the point the dev thinks they are done, preferring ratios for the rest.

I then go on to discuss how estimates and stochastic distributions intersect. I eventually discard anything like that as being impractical to implement (but useful to bear in mind). And ultimately not needed, as we eventually converge on a very tight distribution as we get closer and closer to the end, assuming we have good information flow.

I then take some time to heartily disparage “abstract story points”, or “agile story points”, or just “story points”. Man, do I hate those things with a passion!

Enjoy the vid!

Written by David Penny · Categorized: Management · Tagged: estimation

Reader Interactions

Comments

  1. Jeremy Chan says

    2023-05-24 at 7:32 pm

    Found this quite accurate, and humourous. The “asking 3 times” is a great technique, I find. Here’s an experiment I ran with staff at one point: https://www.linkedin.com/pulse/trouble-software-estimation-jeremy-chan/

    Reply
    • David Penny says

      2023-06-15 at 1:13 pm

      I hadn’t seen that article before. Great work!

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Tags

Architecture (1) Business (1) coding (3) estimation (3) experience (1) hiring (2) horizon-plan (2) Multi-tenancy (1) planning (3) Saas (1) testing (2) women (1)

Footer

Search

  • Home
  • Resources
  • Blog
  • Services
  • About/Contact

Copyright © 2022–2025 - David A. Penny