|
|
Scrum for Team System - Feature Requests
Started by Robzilla at 08-19-2008 5:12 AM. Topic has 2 replies.
  
|
|
Sort Posts:
|
|
|
|
 08-19-2008, 5:12 AM
|
Robzilla
Joined on 07-07-2008
Posts 6
|
|
|
Hi all
Sometimes during a sprint planning meeting we will be in a room without access to a PC. It would be really nice to have some kind or printout that shows us
a) Any SBIs that were not "done" in the sprint just finished (inc current status)
b) Any PBIs and accociated SBIs that haven't been assigned to a sprint yet (in order of business priority)
c) Sprint Burndown chart for each SBI. This allow us to isolate SBIs that went well or went really badly.
Regards
Rob
|
|
|
|
|
Report
|
|
|
|
|
08-21-2008, 4:16 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
|
|
|
Hi Rob,
I've moved this thread hear as it realates to template features and not really task board features. Suggestions made in this forum are reveived regually for consideration in the next SfTS template release.
Crispin
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
|
08-22-2008, 1:27 AM
|
Robzilla
Joined on 07-07-2008
Posts 6
|
|
|
|
|
Hi Crispin
No problem, also just to clarify the last point regarding a burndown chart for each SBI. This doesn't have to be on separate graphs. Each SBI burndown chart can be overlayed upon each other. If the burndown chart becomes too busy (lots of SBIs) then you could perhaps produce 3 sets of burndown charts with overlaid graphs. The fist chart showing SBIs that were delivered and didn't deviate much from the expected velocity (Good SBIs). The second being SBIs that were delivered but jumped all over the graph in a volatile way (OK SBIs). The third being for SBIs that were not delivered (Bad SBIs).
Regards
Rob
|
|
|
|
|
Report
|
|
|
|
|
Scrum for Team ... » Scrum for Team ... » Scrum for Team ... » Printed Reports
|
|
|
|