The document discusses why software developers often end up working long hours to complete projects. It notes that while estimates assume 160 hours of work, contingencies need to be added for weekends, holidays, emergencies, and learning curves when adopting new technologies. As a result, projects often require longer hours, including weekends and 12-hour days, to catch up when actual work lags behind initial estimates and unplanned issues arise.

1. Why do we end up working long hours? The Hockey Stick

4. Final Work Estimate WEEKEND WEEKEND WEEKEND WEEKEND And we tell the customer we will take 32 days instead of the 20 we estimated

5. Lets Look at it again… Theoretical Final We ain’t no Robots

6. Planned Work Progress Trendline Without Contingency With Contingency

7. New Technology – Learning Time Planned Trend line Transition Time Learning Curve

8. To Catch Up… Planned Trend line Learning Curve

9. Not a stretch yet, Possible with Eight Hour Days Planned Trend line Learning Curve Trend line accounting for learning time

10. But, we Just Got out of another Fire Fight… Planned Trendline Why not go slow for some time

11. We Just Got out of another Fire Fight… Planned Trendline We can go slow for some time After all we are no strangers to 10 hour days We should still be able to catch up

12. Ugh… Oh!!! Planned Trendline Life Happens !!!

13. How do we catch up? Planned Trendline 12 hr days including weekends

14. Planned Vs. Actual Work Progress The Hockey Stick

15. Thank You