Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Your job doesn't start when your fingers touch the keyboard. It starts when someone utters the words: "How hard would it be?" This is a crash course in estimating work, identifying hidden costs, and dealing with constraints. Along the way we will also learn how to defend against tricks from the Dark Side such as estimation bargaining, ego manipulation, and crunch time. They taught me Big-O notation, I wish they taught me this. I'm a full stack Rails developer at LiquidPlanner, and have been writing software that helps people get work done for the past dozen years. You'll find me running, walking, biking and eating about town. Help us caption & translate this video! http://amara.org/v/FGZP/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled "Unreasonable Estimates and Improbable Goals," Adam Sanderson, a full stack Rails developer at LiquidPlanner, discusses the critical aspects of project estimation and the challenges developers face when asked about the difficulty of a task. He highlights the importance of accurately understanding project requirements, considering hidden costs, and managing constraints effectively. Key Points Covered: - **Clarification of Requirements:** Sanderson emphasizes that developers often get vague inquiries like "How hard would it be to..." and suggests clarifying what the requester truly means, ensuring both parties share the same understanding. - **Understanding the Project's Why:** It's important to ask why a feature is needed, as it could lead to alternative solutions and saving development time. - **Estimating Effort:** Sanderson encourages developers to break down tasks, recalling experiences with similar issues, and making informed guesses about time and complexity, acknowledging that estimates should allow for uncertainty. - **Communicating Uncertainty:** He advises developers to communicate any uncertainties at the outset, to avoid unpleasant surprises later in the project timeline. - **The Dark Arts of Project Management:** Sanderson warns against common pitfalls, such as estimation bargaining and ego manipulation. Developers should stick to their estimates, as reducing them under pressure can lead to unrealistic outcomes. - **Managing Hidden Costs:** Features sometimes impose future complexities that require additional considerations. Sanderson highlights types of hidden costs including operational, support, and opportunity costs, suggesting that developers factor these into their estimates. - **Prioritization and Deadlines:** He discusses the necessity of recognizing soft versus hard deadlines and how developers should handle them appropriately, whether it be cutting scope, adding resources, or finding alternatives when a deadline cannot be met. Sanderson asserts that communication is key throughout this process to prevent misunderstandings and ensure successful outcomes. In conclusion, the takeaway from Sanderson's presentation is the need for clear communication, thorough understanding, and realistic estimation in project management, which can translate to better project outcomes and less frustration for developers and teams alike.
Suggest modifications
Cancel
