NoEstimates: How To Measure Project Progress Without Estimating
How to always be on time, and not risk missing important deadlines or go over budget
This book is the result of many years of hard work, and plenty of lessons learned. I wrote it because I believe we can do better than the accepted "status quo" in the software industry.
It took me years to learn what I needed to learn to come up with my version of the #NoEstimates approa
It's hard to dismiss that our industry has a knack for turning estimates into commitments. I assume that's partly because our brain just anchors to the first numbers it heard (see Kahnemans Thinking fast & slow). Probably that's just how we humans tick. Undesirable, but unfortunate reality.
I always tried to work my way around estimates with corridors and probabilities wherever I can, especially to communicate uncertai ...more
If you're interested in Agile development and dropping estimates this is an okay book. I have a feeling that there is better out there though.
Die Story, in die das ganze eingebettet ist: puh. Wäre eigentlich nicht nötig gewesen. Und das Problem (das mich am meisten interessiert hat), nämlich *zum Projektbeginn* zu schätzen, wird einfach nicht beantwortet (obwohl es als Problem aufgeworfen ...more
So, how can you minimize the amount of estimates? You should timebox features. Working within this boundary should encourage the team to come up with creative options. As for user stories, timeboxing them to 1 day is a great target, but I f ...more
Por otra parte, podría estar bastante mejor escrito, parece más un borrador que un libro.
Goodreads is hiring!
Learn more »