Changes between Version 316 and Version 317 of ScrumBurndownPlugin


Ignore:
Timestamp:
Feb 19, 2010 12:06:32 AM (5 years ago)
Author:
rjollos
Comment:

Add burndown image

Legend:

Unmodified
Added
Removed
Modified
  • ScrumBurndownPlugin

    v316 v317  
    1818This plugin is integrated with the TimingAndEstimationPlugin. 
    1919 
    20 '''Current Version:''' 1.9.2[[BR]] 
    21  
    22 == Installation Instructions == 
    23 Installation instructions can be found here: [http://stuq.nl/software/trac/ScrumBurndownPlugin/installation Installation instructions] 
    24  
    2520== Using the plugin == 
    2621At 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. 
     
    2924 
    3025In order for this to work, it is imperative that developers keep the 'Estimated Hours' and 'Total Hours' fields accurate and up-to-date on the tickets they are working.  The 'Total Hours' field itself should never be manually edited, but rather, it can be changed by inputting positive and negative values into the 'Hours to Add' field. 
     26 
     27[[Image(burndown.jpg,80%)]] 
    3128 
    3229== Bugs/Feature Requests ==  
     
    4138 
    4239You can check out the source [/svn/scrumburndownplugin using Subversion] or [source:scrumburndownplugin browse the source] with Trac. 
     40 
     41== Installation Instructions == 
     42Installation instructions can be found here: [http://stuq.nl/software/trac/ScrumBurndownPlugin/installation Installation instructions] 
    4343 
    4444== Related Plugins ==