The document discusses factors that can impact estimates for software development projects including developer skill, domain knowledge, and clarity of requirements. It notes that these factors can multiply and result in estimates that are off by as much as 5000 times. It also discusses techniques for estimating including planning poker, relative sizing, and avoiding absolute estimates. Finally, it recommends starting defect fixing early to improve estimates and culture.
8. “Just-a-second syndrome.”
Keeps the work environment healthy.
Scope is determined.
Highlights areas of concern/risk.
Polishes stories.
Rocks, stones, and sand.
9. S, M, L, XL
Lacks mathematical convenience.
Linear
Assumes uniform effort steps.
Fibonacci
Reduces the illusion of additive
mathematics.
15. • Avoid it
• Overhead
• Inspires bad behavior
– Developers cut corners
– Start lying
• Derive it rather than track it
16. • Usually not estimated
– Time for root cause analysis is unpredictable
– Or, you know where the problem lies
• Start defect fixing in first few iterations
– Improves estimation and team culture
How many passengers can travel in each of these?Boeing 747 – Between 400 and 600. Max Take off weight: 750-950,000 lbs.Airbus A 380 – Between 500 and 800. Max Take off weight: 1.2 – 1.3 million lbs.Cruise ship – Approximately 2000.
How many room does this hotel have? Why did it become a little more difficult this time? (Never seen this building before? No idea of it’s scale? Not sure what’s inside of it?)
What’s the problem in estimation here? We know what it is, we have the history, so why can’t we be certain?
