4 ms·

Dunno but Spolsky wrote there was some developer velocity metric in some blog post about estimations he was really proud of. So I guess it some proto-Jira with

• noir_lord 4y ago
  Most likely this - https://www.joelonsoftware.com/2007/10/26/evidence-based-scheduling/ https://www.joelonsoftware.com/2007/10/26/evidence-based-sch... The approach sounds lovely on paper, in practice most software development environments range from absolutely terrible to terrible - that level of organisation isn't something I can see more teams doing even if the tool does help.
  • rightbyte 4y ago
    Oh ye that one. I remember reading that and thinking to my self "that can't possibly work" - years before I was exposed to Agile for the first time learning first hand how silly upfront no-research estimations are. What I learned is that people pad and fudge numbers to make the burndown chart nice, which might be what Spolsky's employees did in the end to please his try to make an estimation tool. Also, breaking down task in my experience counterintuitively makes them harder to estimate. I.e. summing many small estimates over doing one big for the set of subtasks.
• krallja 4y ago
  For summer vacation, I’ve been reading some histories of modern computing (electronic, digital, programmable). One of the ENIAC’s first tasks was to run Monte Carlo simulations to help design the H bomb. The first Cray jobs also used Monte Carlo simulation for weather modeling (important Cold War knowledge; you need to know where your fallout is likely to spread) and weapons design. This technique is also how Evidence-Based Scheduling works.