This would be really useful - a burndown chart to monitor the end date of a project and show people at regular intervals who start to cry if they see anything more complex.
The one type of burndown chart that is really effective is a burndown chart that works on a cross basis (see attached) This would also record any new tasks or features that were added to your project essentially pushing the end date out. If the horizontal line is your baseline, the additional time added from new tasks (or refactored time on existing tasks, is represented by a new horizontal line that effectively become you revised baseline reflecting task completion actuals and time for new tasks added. This also then shows you the new end date.
The attachment does show roughly what I mean I hope! 0 represents the baseline. The minus figures underneath the 0 baseline reflect additional/refactored tasks or features, thus giving you a new end date.
The one type of burndown chart that is really effective is a burndown chart that works on a cross basis (see attached) This would also record any new tasks or features that were added to your project essentially pushing the end date out. If the horizontal line is your baseline, the additional time added from new tasks (or refactored time on existing tasks, is represented by a new horizontal line that effectively become you revised baseline reflecting task completion actuals and time for new tasks added. This also then shows you the new end date.
The attachment does show roughly what I mean I hope! 0 represents the baseline. The minus figures underneath the 0 baseline reflect additional/refactored tasks or features, thus giving you a new end date.
Last edited by chat-noir; 2008-02-21 at 09:50 AM..
Threaded Mode