Have Geek Brain

How to measure progress in software development

I would like to help my project manager (not a programmer) keep track of how quickly things will get done. We have a detailed requirement specification in DOORS that allows us to track requirements that have been met. I suggested this as a sane tracking mechanism.

0


a source to share


3 answers


Make sure the items you are tracking are small enough to have some semblance of accuracy in their estimates.

Nothing stands in the way of a software project more than inaccurate estimates, and the more work, the more inaccurate the estimates will be.



Put differently, in order 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", you can't get anything close to an accurate progress report.

+2


a source


It looks like you are looking to write down chart , as used in the scrum . I only recently got some insight into this, but it looks like a very good concept that actually tracks progress very accurately.

but



  • You have to break much more, much less than what you specified in your requirements specification. They are capable of great appreciation to reliably value.
  • Destruction must be done by developers.
  • EVALUATIONS AT THESE POINTS MUST COME FROM IMPLEMENTS!

Without the bottom-up aspect that allows the performer to make the assessment himself, you will never get good grades. Starting with top-down estimates of system requirements, they are fine until they become final estimates.

0


a source


I love using FogBugz ... It works great to track not only bugs with a program, but also features that need to be implemented. This tells you very well if you make your ship date on time.

It's free for a team of one person. But it is not that expensive to use a monthly plan.

http://www.fogcreek.com/FogBUGZ/

0


a source






More articles:


All Articles