Changes between Version 163 and Version 164 of ScrumBurndownPlugin

Timestamp:

Jul 21, 2007, 10:44:21 PM (17 years ago)

Author:

anonymous

Comment:

--

ScrumBurndownPlugin

@@ -18 +18 @@
 
 == Who's Using It ==
-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'''
+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: '''130'''
 
 Also, feel free to drop me an e-mail if you've got any questions that aren't answered here and aren't really ticketable.
@@ -54 +54 @@
 In 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.
 
+''Not sure I understand this.''
+ * initial ticket has 8 hours as the estimate
+  * burndown chart has 8 - 0 added to it
+ * work for 5 hours on the ticket and enter this in the Hours to Add field.
+  * presumably the remaining 8 - 3 hours go on the burndown chart
+ * if I go over 8 hours should I change the estimate as well? 
+ * seems like there should be 3 fields
+  * initial estimate
+  * current hours worked
+  * estimated hours remaining
+ * or do you use the estimated hours as the estimated hours remaining to complete the ticket? 
+
 == Bugs/Feature Requests ==