02:50 – Michael Hartl, Tau Manifesto
- Hardest Part of Programming = Estimation
- Person Problem; Not a Programming Problem
04:10 – Estimation
- Complexity Number vs Time Number
- MS Project
- Project Planning vs Estimation
07:13 – Tools/Estimation Methods
08:20 – Things That Throw Off Estimations
- ‘Ugh!knowns’
- Oversight
10:25 – Planning Poker vs Velocity vs Points
- Points: Measure to Estimate Effort for Completing Agile Development
- Or Measures of Complexity
- Velocity (in Agile) = Points Completed Per Iteration
- Pivotal Tracker
20:40 – Components to Making Estimate
- Amount of Time/Effort
- Confidence Factor
- Risk: Not Completing Task But Meeting Schedule Estimate
- Best Case vs Worst Case
25:00 – How Well Teams Estimate
25:50 – Building a House vs Building Software
- Waterfall: You Already Know the ‘Gotchas’
- Software: Solve a Problem That Hasn’t Been Solved Before
38:20 – Success Stories
41:59 – Worst Estimates / How to Get Better at Estimating
- Implementing/Breakdown of Stories
- Pi Factor: Make an Estimate, Multiply by 3.14
- If Developer < 5 years Experience, Multiply by 2 & Raise It! (Ex: Two Days = 4 Weeks)
52:49 – Ways to Get Better
- Red Flag When You Hear ‘Two Weeks’
- Well-gelled Teams
- ESTIMATE YOUR ESTIMATING
- Most Important Part: Retrospective at the End of the Sprint
