I would like to help my project manager (a non-programmer) track how quickly things get done. We have a detailed requirement spec in DOORS that allow us to track completed requirements. I have suggested this as a reasonable tracking mechanism.
我想帮助我的项目经理(非程序员)跟踪事情的完成速度。我们在DOORS中有详细的要求规范,允许我们跟踪已完成的要求。我已经建议将其作为一种合理的跟踪机制。
3 个解决方案
#1
Make sure the items you track are small enough to have some semblance of accuracy in their estimations.
确保您跟踪的项目足够小,以便在估算中具有一定的准确性。
There nothing that disturbs a software project as much as inaccurate estimates, and the bigger the job, the more inaccurate the estimates will be.
没有什么能够像软件估算不准确那样扰乱软件项目,而且工作量越大,估算值就越不准确。
Put differently, to be able to accurately track project progress, you need small tasks that have relatively accurate estimates.
换句话说,为了能够准确地跟踪项目进度,您需要具有相对准确估计的小任务。
If you have items on your list that will take a "week or longer", there's no way you will be able to have anything close to a accurate progress report.
如果您的列表中的项目需要“一周或更长时间”,那么您将无法获得接近准确进度报告的任何内容。
#2
I like to use FogBugz... It works great to track not only bugs with the program but also features that need to be implemented. It does pretty well with telling you if you will make your ship date on time.
我喜欢使用FogBugz ...它不仅可以跟踪程序中的错误,还可以跟踪需要实现的功能。它告诉你是否按时约会你的确是如此。
For a one man team it is free. But it is not that expensive to use the monthly plan.
对于单人团队来说,它是免费的。但使用月度计划并不昂贵。
#3
It sounds like you are looking for a burn down chart like used in scrum. I have only just recently gained some exposure to it, but it looks like a very nice concept that actually tracks progress very accurately.
听起来你正在寻找像scrum中使用的刻录图表。我刚刚获得了一些曝光,但它看起来像一个非常好的概念,实际上非常准确地跟踪进展。
However
- You have to break down in much, much smaller items than what you have listed in your requirement specification. They are way to big to estimate reliably.
- The break down have to be done by the implementers.
- THE ESTIMATES ON THOSE ITEMS HAVE TO COME FROM THE IMPLEMENTERS!
您必须分解比您的需求规范中列出的项目小得多的项目。它们是可靠的估计方式。
分解必须由实施者完成。
对这些项目的估计必须来自实施者!
Without the bottom-up aspect of letting the doer make the estimate him-/her-self you will never achieve good estimates. Starting with top-down estimates from system requirements are fine - as long as they do not end up being the final estimates.
如果没有自下而上的方面让行动者估计他/她自己,你将永远无法获得良好的估计。从系统要求的自上而下的估计开始是好的 - 只要它们最终不是最终的估计。
#1
Make sure the items you track are small enough to have some semblance of accuracy in their estimations.
确保您跟踪的项目足够小,以便在估算中具有一定的准确性。
There nothing that disturbs a software project as much as inaccurate estimates, and the bigger the job, the more inaccurate the estimates will be.
没有什么能够像软件估算不准确那样扰乱软件项目,而且工作量越大,估算值就越不准确。
Put differently, to be able to accurately track project progress, you need small tasks that have relatively accurate estimates.
换句话说,为了能够准确地跟踪项目进度,您需要具有相对准确估计的小任务。
If you have items on your list that will take a "week or longer", there's no way you will be able to have anything close to a accurate progress report.
如果您的列表中的项目需要“一周或更长时间”,那么您将无法获得接近准确进度报告的任何内容。
#2
I like to use FogBugz... It works great to track not only bugs with the program but also features that need to be implemented. It does pretty well with telling you if you will make your ship date on time.
我喜欢使用FogBugz ...它不仅可以跟踪程序中的错误,还可以跟踪需要实现的功能。它告诉你是否按时约会你的确是如此。
For a one man team it is free. But it is not that expensive to use the monthly plan.
对于单人团队来说,它是免费的。但使用月度计划并不昂贵。
#3
It sounds like you are looking for a burn down chart like used in scrum. I have only just recently gained some exposure to it, but it looks like a very nice concept that actually tracks progress very accurately.
听起来你正在寻找像scrum中使用的刻录图表。我刚刚获得了一些曝光,但它看起来像一个非常好的概念,实际上非常准确地跟踪进展。
However
- You have to break down in much, much smaller items than what you have listed in your requirement specification. They are way to big to estimate reliably.
- The break down have to be done by the implementers.
- THE ESTIMATES ON THOSE ITEMS HAVE TO COME FROM THE IMPLEMENTERS!
您必须分解比您的需求规范中列出的项目小得多的项目。它们是可靠的估计方式。
分解必须由实施者完成。
对这些项目的估计必须来自实施者!
Without the bottom-up aspect of letting the doer make the estimate him-/her-self you will never achieve good estimates. Starting with top-down estimates from system requirements are fine - as long as they do not end up being the final estimates.
如果没有自下而上的方面让行动者估计他/她自己,你将永远无法获得良好的估计。从系统要求的自上而下的估计开始是好的 - 只要它们最终不是最终的估计。