Changes between Version 9 and Version 10 of ScrumBurndownPlugin

Timestamp:

Jun 23, 2006, 8:18:38 PM (18 years ago)

Author:

Sam Bloomquist

Comment:

--

ScrumBurndownPlugin

@@ -48 +48 @@
 [[Image(burndown.jpg)]] 
 
-At the beginning of a sprint, after the tickets have been inputted and estimated in Trac an admin user should click the 'Start Milestone' plugin.  This inputs a datetime integer into the milestone table to indicate when the milestone was started.  The daily burndown_job.py script will only recorded hours_remaining entries for milestones that have started, but have not been completed.  It should be fairly obvious, then, that an admin user should click the 'Milestone Complete' button at the end of the milestone to prevent the burndown_job from continuing to collect data.
+At the beginning of a sprint, after the tickets have been inputted and estimated in Trac an admin user should click the 'Start Milestone' plugin.  This inputs a datetime integer into the milestone table to indicate when the milestone was started.  The daily burndown_job.py script will only record hours_remaining entries for milestones that have started, but have not been completed.  It should be fairly obvious, then, that an admin user should click the 'Milestone Complete' button at the end of the milestone to prevent the burndown_job from continuing to collect data.
 
 You can view different burndown charts, selectable by milestone and component by choosing from the dropdowns and clicking the 'Show Burndown Chart' button.
+
+In order for this to work, it is imperative that developers keep the current_estimate and time_spent fields up-to-date on the tickets they are working.  At my company, if we add a new ticket in the middle of the sprint, we input 0 for orig_estimate so that we can track our estimating abilities at the end of each sprint.
 
 == Bugs/Feature Requests ==