TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Software development: dealing with awful estimates

8 点作者 Unosolo超过 14 年前

3 条评论

cromulent超过 14 年前
I have a customer whose strictly-enforced process is:<p><pre><code> 1. Estimate (based on one-sentence title of feature) 2. Wait for approval 3. Find out detailed requirements 4. Design and document 5. Implement and deploy </code></pre> 3,4, and 5 should be included in your original estimate.<p>If you try to do 3 first, you are <i>not following the process</i>. The process is touted as "best practice 2.0".
评论 #2217419 未加载
评论 #2217403 未加载
gte910h超过 14 年前
I do like that he puts forth the "don't agree to stupid" and "don't agree to hurry unduly" positions.<p>I disagree with him on "Normally, the way it works, is that your estimate is first scanned for odd looking or relatively large items. Hence be prepared to defend anything with “non-standard” name. Also split larger tasks so that all tasks have same order of magnitude, i.e. if most tasks take 2 days and one single task is 10 days be prepared to get drilled."<p>I believe generally you should actually communicate the hard parts of the project to people. You should actually communicate what about it is hard if you have any ability to do so, and you should state alternative risk management strategies you've turned down for what reasons if they ask about them.
评论 #2218802 未加载
StudyAnimal超过 14 年前
This is one thing the agilists have gotten right.<p>Estimate the size of the problem in abstract units like story points, and do it in small chunks.