This episode is part of a wider mini-series looking at Estimation in Software Development.
So for this episode I want to introduce the idea of a "valuable estimate" and what that may mean for you.
As I go through this series I will use the term "valuable estimate" as a short hand for some value that is desirable by the organisation asking for it.
This may seem a little vague … and to be honest, by design it is. I've spent a lot of time trying to decide what the best estimates should look like - but ultimately I feel it depends on a variety of factors - and is likely to be specific to an organisations - or maybe an initiative - or maybe even to an individual piece of work. We quickly find ourselves in the consultants stock answer of "it depends".
So while, in this episode I'll discuss to key characteristics that I believe affect the value of an estimate, the actual (or imagined) value of an estimate will be in the "eye of the beholder".
Thus the short hand of "valuable estimate"
-----
Find this episodes show notes at: https://red-folder.com/podcasts/191
Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Ver todos los episodios