Have you ever been in a situation where you were provided very little information and asked to estimate it out? Have you been in the followup scenario where you had to explain why your estimates were "wrong"? I have been in this situation multiple times and decided to do something about it. By requiring technical annotations and building out a process for providing better estimates, I found myself less and less in the difficult conversations about the work completed. Learn about my tips and tricks to technical annotations and estimating.


Comments are closed.

Brian Fenton at 13:46 on 10 Mar 2018

Good list of potential pitfalls creating estimates, with strategies to avoid missing tasks. How not give estimates you can stick with and meet.

Riley Major at 13:52 on 10 Mar 2018

Nice reminders to document more during project estimation process; memorialize what’s in *and* out of scope. Good tip to white board out interface to remove distractions and provide a framework for walking through the individual components during estimation.

I would recommend approaching “ADA compliance” from a more inclusive perspective. Rather than (or perhaps in addition to) scaremongering with the threat of lawsuits, lobby for accessibility on its own merits— that it helps more people use your site more effectively.

Anonymous at 13:53 on 10 Mar 2018

Lots of good thoughts on APIs and how they should work.

Thanks for the talk! It was a good overview of stuff to think about when creating an estimate.

Louise Adams at 13:55 on 10 Mar 2018

Well organized, logical approach!

Greg Lyon at 13:58 on 10 Mar 2018

Documentation is king!

Justin Foell at 10:51 on 11 Mar 2018

Good stuff. I like that you track your actuals verses estimates. Would like to hear more about how you arrive at estimate numbers for something you haven't done before.

Great talk! Full of great, detailed information on how to do annotations and estimates. I agree with Riley Major about accessibility information.