软件时间规划指标
在软件开发中我们都需要正确规划时间。我想知道您在软件的所有流程（例如分析、开发、维护等）中使用什么指标来规划时间……
当然，您可以建议一些很棒的文章或您遵循的方法论，您能告知一下吗？
In software development we all need to planning the time correctly. I want to know what metrics you are using to planning time in all processes of software such as analysis, development, maintenance etc...
Sure there are some great articles that you could suggest or methodologies that you follow, could you please inform?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
坏消息是，不......让我们称之为“现成的”指标......会立即给你好的结果。开发团队之间存在太多变量，不同的人应用该指标的方式也有太多差异。
在估算中获得良好结果的唯一方法是采取措施将估算与现实联系起来。估算不仅与现实相符，还必须与现实进行比较。这意味着您必须进行估计，将估计与实际发生的情况进行比较，并适当调整生成估计的过程。
对于更具体的内容，Joel on Software 有一篇关于基于证据的调度< /a> 值得一读。我不一定认为这是“最好”的过程，但它是一个比 95% 的软件团队曾经实现的更好的起点。
The bad news is that no... let's call it an "off-the-shelf" metric... will immediately give you good results. There are too many variables between development teams and too much variation in how different people may apply the metric.
The only way you can get good results in estimation is by taking steps to chain your estimates to reality. Estimates do not just fall in line with reality, they must be wrestled there. That means you must make estimates, compare the estimates to what really happened, and adjust your process for generating them appropriately.
For something more concrete, Joel on Software has a great article on Evidence-Based Scheduling which is worth a read. I don't necessarily think this is the "best" process but it's a starting point which is better than 95% of software teams ever achieve.
如果您对敏捷方法感兴趣，我发现敏捷估算和规划 读得好。
If you are interested in Agile methodology I found Agile Estimating and Planning a good read.