Whether you’re building software, managing projects, or just driving from one place to another—you’re measuring time and effort in some way. Measuring time and effort happens in all shapes and sizes. When driving somewhere you’re most likely going on experience and deciding to leave when you assume you have enough time given a set of variables such as route, traffic, and weather. When building software the measuring is a bit more specific and likely written down somewhere in some form. But who decides how much to measure? How specific and precise to get?
We’re going to dig into the varying ways to measure time and effort in a variety of contexts. Looking at our collective experiences and the experiences and teachings of those in a few different industries we will have plenty to discuss and debate on this topic. You will hopefully leave with a new perspective or idea on when, how and how much to measure.
-------
Slides prepared and formatted for Refresh Savannah on Sept 16, 2014.
References:
- http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension
- http://classes.soe.ucsc.edu/ams214/Winter09/foundingpapers/Mandelbrot1967.pdf
- http://en.wikipedia.org/wiki/Coastline_paradox
- http://www.stevepavlina.com/blog/2008/05/how-to-make-accurate-time-estimates/
- http://www.mindtools.com/pages/article/newPPM_01.htm
erikreagan
c0rp_mdm
arches0501
livesense
akippa
kkosukeee
tokyo_metropolitan_gov_digital_hr
takashi_toyosaki
mercari_inc
arisaiyou
kubell_hr
fkino
paigeccino
sugarenia
morganepeng
lauravandoore
jeffersonlam
maggiecrowley
chriscoyier
davidbonilla
addyosmani
matthewcrist
marktimemedia
kneath
