Changes between Version 31 and Version 32 of ScrumBurndownPlugin


Ignore:
Timestamp:
Sep 13, 2006 8:08:55 PM (8 years ago)
Author:
sambloomquist
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ScrumBurndownPlugin

    v31 v32  
    55A plugin to enable burndown chart capabilities, a common part of Scrum and other agile development methodologies. 
    66 
     7This plugin is now integrated with the TimingAndEstimationPlugin. 
     8 
    79== Who's Using It == 
    810I'm interested to know how many people are using this plugin.  If a lot of people are using it or at least evaluating it, I will be able to justify spending more time on it to my boss.  If you download it, please increment this counter: '''13''' 
     11 
     12Also, feel free to drop me an e-mail if you've got any questions that aren't answered here and aren't really ticketable. 
    913 
    1014== Installation Instructions == 
    1115 
    1216Installing this plugin is a four-step process. 
     17 1. Install the TimingAndEstimationPlugin 
    1318 1. Install the egg 
    14  1. Add custom ticket fields 
    15  1. Create a cron/pycron job to run a daily python script 
    16  1. Add permission fields 
     19 1. Create a cron/pycron job to run a daily/hourly/however-often-you-want-to-update-the-burndown-ly python script 
     20 1. Assign permissions 
    1721 
    1822==== Installing the egg ==== 
    1923Install just like you would any other Trac plugin.  Drop the egg into your plugins or site-packages folder and then try to access Trac in your browser.  You will get an error message saying that the database needs to be upgraded and telling you to use the trac-admin command to do it.  (I think it's something like 'trac-admin !YourProjectName.db upgrade').  Perform the upgrade. 
    20  
    21 ==== Add custom ticket fields ==== 
    22 Add the following to your trac.ini file: 
    23  
    24 {{{ 
    25 [components] 
    26 burndown.* = enabled 
    27  
    28 [ticket-custom] 
    29 orig_estimate = text 
    30 orig_estimate.label = Original Estimate (in hours) 
    31 current_estimate = text 
    32 current_estimate.label = Current Estimate (in hours) 
    33 time_spent = text 
    34 time_spent.label = Time Spent 
    35 }}} 
    36  
    37 Original estimate is not really used by the plugin, it's just common Scrum process to be able to see how the estimates have change throughout a given sprint. 
    3824 
    3925==== Pycron/cron job ==== 
     
    4531Set up a job to run the burndown_job.py script once a day.  I personally am using Windows, so I used pycron.  Here is an example pycron tab file to run the job at noon on weekdays: attachment:crontab.txt   
    4632 
    47 This job totals up all the remaining time for given milestones and components and saves the information into the trac burndown table so that the plugin can use it to draw charts. 
     33This job totals up all the remaining time for given milestones and components and saves the information into the trac burndown table so that the plugin can use it to draw charts.  Per suggestions from the user community, this job can now be run multiple times per day.  If the given day already has a burndown entry, an UPDATE will be performed instead of an INSERT. 
    4834 
    4935==== Assign Permissions ==== 
     
    5743You can view different burndown charts, selectable by milestone and component by choosing from the dropdowns and clicking the 'Show Burndown Chart' button. 
    5844 
    59 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. 
     45In 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 'Hours to Add' field. 
    6046 
    6147== Bugs/Feature Requests ==