Timeline for Scrum overestimation and replanning
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2011 at 15:45 | comment | added | RyanWilcox | Having been on a team that did burn up charts in terms of days, please do NOT do a burn up chart with days being the units. In our team, in a two week sprint, the first half week didn't show much activity, so management got nervous... even though the reason why there wasn't much activity was because of the meetings we had during the first two days... In my mind iterations are the perfect level of detail here. | |
| Jun 9, 2011 at 14:40 | history | edited | Martin Wickman | CC BY-SA 3.0 | value => work |
| Jun 9, 2011 at 14:40 | comment | added | Martin Wickman | @Thomas: Feel free to substitute points for value if that is important, or create two charts. You can use years, iterations, days or whatever time unit suits your project best. | |
| Jun 9, 2011 at 14:31 | comment | added | Thomas Owens♦ | I was under the impression that Burn Down Charts shows work remaining on a sprint in terms of story points while a Burn Up Chart shows the total delivered earned value to the customer. Story points and earned value are different - story points relate to time and effort required to complete the tasks as assigned by developers and earned value is the worth of each story as assigned by the product owner. Burn Down focuses on a per-sprint basis for developers, while Burn Up focuses on project level for managers and customers. Is this not the case? | |
| Jun 9, 2011 at 14:28 | history | answered | Martin Wickman | CC BY-SA 3.0 |