Answers to: Yet another sprint burndown issuehttps://jazz.net/forum/questions/16372/yet-another-sprint-burndown-issueAccording to the sprint burndown report, &quot;only work items which are open and in progress and which have an estimate are included in the calculation&quot;. This raised a question when I tried to manually recompute the remaining work.
<br />
<br />As of today, our sprint burndown shows we still have around 155 hours of work left.I have to approximate as the dot is between the 140 and 160 hour lines but near the 160.
<br />
<br />According to the Progress report bar:
<br /><blockquote>
<br /> Work hours done: 182 of 300
<br /> Expected Work Hours: 245
<br /></blockquote>
<br />
<br />And tallying all the defects and tasks in our current sprint:
<br />
<br /><pre>
<br /> Total number of work items&#58; 28
<br /> Total number of work items w/o estimates or time spent&#58; 22
<br />
<br /> Not started work items &#58; 10
<br /> Total estimate&#58; 32hrs
<br />
<br /> In Progress work items w/o correction&#58; 8
<br /> Total estimate&#58; 205hrs
<br /> Total time spent&#58; 109.5hrs
<br /> Remaining&#58; 95.5hrs
<br />
<br /> In Progress work items w/ correction&#58; 1
<br /> Total estimate&#58; 36hrs
<br /> Total corrected estimate&#58; 16hrs
<br /> Total time spent&#58; 12hrs
<br /> Remaining&#58; 4hrs
<br />
<br /> Resolved work items&#58; 2
<br /> Total estimate&#58; 18hrs
<br /> Total corrected estimate&#58; 26hrs
<br /> Total time spent&#58; 26hrs
<br /> Remaining&#58; 0hrs
<br /></pre>
<br />
<br />The phrasing of the report description is confusing so here are my calculated numbers
<br />
<br /> * Work items which are open <b:55e922e2e2>AND</b:55e922e2e2> in progress <b:55e922e2e2>AND</b:55e922e2e2> have an estimate
<br />
<br /> Number of WI matching filter: 9
<br /> Total estimate w/o correction: 241hrs
<br /> Total estimate w/ correction: 221hrs
<br /> Total time spent: 121.5 hours
<br /> Total remaining effort against original estimate: 119.5
<br /> Total remaining effort against corrected estimate: 99.5
<br />
<br /> * Work items which are <b:55e922e2e2>(</b:55e922e2e2> open <b:55e922e2e2>OR</b:55e922e2e2> in progress <b:55e922e2e2>)</b:55e922e2e2> <b:55e922e2e2>AND</b:55e922e2e2> have an estimate
<br />
<br /> Number of WI matching filter: 19
<br /> Total estimate w/o correction: 273hrs
<br /> Total estimate w/ correction: 253hrs
<br /> Total time spent: 121.5 hours
<br /> Total remaining effort against original estimate: 151.5
<br /> Total remaining effort against corrected estimate: 131.5
<br />
<br />
<br />Based on the approximated value in the Sprint Burndown graph, the second filtering criteria is closer but why was the burndown not considering the corrected estimate in the computation? I am sure nobody has updated any time fields from the time the database snapshots were updated and when I took the sample data I used in the computation. And how do I tie it with the Progress bar report?
<br />
<br />Anybody care to explain where I possibly used a wrong assumption? Our server is using RTC 1.0.1.
<br />
<br />ciao!enSun, 04 Aug 2024 14:54:47 -0000