Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
I Estimate this Talk will be 20 Minutes Long, Give or Take 10 Minutes by Noel Rappin Estimates are like weather forecasts. Getting them right is hard, and everybody complains when you are wrong. Estimating projects is often critically important to the people who pay us to develop software. We can do better. We can focus our estimates on the parts we do well, like estimating complexity. We can present estimates without falsely inflating them, and we can be transparent during the development process. The humble point estimate can help you, if you understand its limitations. Better estimates and communication of estimates will make your projects run more smoothly. Help us caption & translate this video! http://amara.org/v/H0zn/
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
The video "I Estimate this Talk will be 20 Minutes Long, Give or Take 10 Minutes" by Noel Rappin, presented at RubyConf 2015, explores the complexities and challenges of project estimation in software development. Rappin draws parallels between estimating project timelines and predicting weather, emphasizing that accurate estimates are critical yet often fraught with difficulty. He argues that focusing on estimating complexity rather than arbitrary timeframes can enhance communication between developers and clients, leading to smoother project execution. Key points discussed include: - **The Nature of Estimates**: Rappin illustrates how estimates, like predicting travel time to an airport, rely on assumptions and can easily become inaccurate due to various unpredictable factors. - **Industry Comparisons**: He compares software development estimations to those in construction and home remodeling, asserting that estimation issues are widespread across industries and not unique to developers. - **Agile Methodologies**: Rappin addresses the idea proposed by some Agile proponents to eliminate estimates entirely. He contends that while this approach may work in some contexts, consulting projects typically require at least a rough plan and communication around expectations. - **Communication Importance**: Estimates serve as a communication tool, showcasing monetary investment and progress tracking, which are crucial in managing client relations and setting realistic expectations. - **Challenges of Early Estimates**: Rappin highlights the difficulty of producing accurate estimates at the beginning of a project, suggesting that estimating complexity remains more feasible and effective. - **Embracing Uncertainty**: He stresses that estimates should acknowledge uncertainty and avoid chasing false precision, focusing instead on relative complexity. - **Methods for Estimation**: Rappin proposes a technique involving assigning ranges of point values to tasks based on their complexity, allowing for a better initial framework while recognizing the fluid nature of project estimations. In conclusion, Rappin advocates for a pragmatic understanding of estimates by recognizing their inherent uncertainties and utilizing them as strategic communication tools. Enhanced processes and transparency in estimates can ultimately improve project outcomes and client satisfaction.
Suggest modifications
Cancel
