152 karma · joined October 14, 2015
If the client wants to pay a fixed bid then bake that added risk into your estimate.
For clients - if they're asking for something new/unique, what they have in their minds at the beginning is just a theory and needs to be tested -- working in iterations and focusing on "how do we help you prove your hypothesis in the most time/cost effective manner". Agile is about incremental, demonstrable progress to provide clarity and reduce risk.
Another thing that helps me focus is Chrome's user profiles (and the main reason I haven't migrated to Safari). I maintain both 'Work' and 'Play' profiles -- that separation helps limit the urge to cycle through my bookmark bar.
Estimating is important because it gives management the ability to deploy resources strategically and manage expectations. Bad managers think estimates are a promise/guarantee. Assuming the estimates were arrived at with as much clarity as possible (planning poker), good managers understand that estimates are a tool to aid decision-making.
Not as pleased with the Windows version, but it's serviceable
It's a fascinating listen into the psychology behind gigantic failures.
[1] http://omegataupodcast.net/2015/09/181-why-megaprojects-fail...