Changes between Version 163 and Version 164 of ScrumBurndownPlugin


Ignore:
Timestamp:
Jul 22, 2007, 12:44:21 AM (8 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ScrumBurndownPlugin

    v163 v164  
    1818
    1919== Who's Using It ==
    20 I'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: '''129'''
     20I'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: '''130'''
    2121
    2222Also, feel free to drop me an e-mail if you've got any questions that aren't answered here and aren't really ticketable.
     
    5454In 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.
    5555
     56''Not sure I understand this.''
     57 * initial ticket has 8 hours as the estimate
     58  * burndown chart has 8 - 0 added to it
     59 * work for 5 hours on the ticket and enter this in the Hours to Add field.
     60  * presumably the remaining 8 - 3 hours go on the burndown chart
     61 * if I go over 8 hours should I change the estimate as well?
     62 * seems like there should be 3 fields
     63  * initial estimate
     64  * current hours worked
     65  * estimated hours remaining
     66 * or do you use the estimated hours as the estimated hours remaining to complete the ticket?
     67
    5668== Bugs/Feature Requests ==
    5769