Confirmed users
1,193
edits
Scrum/Tools: Difference between revisions
→The Bad: Added note about Songbird assuming release backlog exists.
(→The Bad: Added note about difficulty of setting Bugzilla up for Scrum.) |
(→The Bad: Added note about Songbird assuming release backlog exists.) |
||
| Line 24: | Line 24: | ||
* SDPBOT does not seem to generate burndown charts from Bugzilla data, and there do not seem to be any other tools that do. | * SDPBOT does not seem to generate burndown charts from Bugzilla data, and there do not seem to be any other tools that do. | ||
* Unlike some other tools, Bugzilla aims to be fairly generic. It was not built specifically for managing Scrum user stories, so it may take some work, frustration, and training to set it up appropriately. The writeup from the Songbird team seems to confirm this -- the first section is named "Wrestling Bugzilla into shape" and they explain that their primary reason for using Bugzilla was that their workflow was already built around it. | * Unlike some other tools, Bugzilla aims to be fairly generic. It was not built specifically for managing Scrum user stories, so it may take some work, frustration, and training to set it up appropriately. The writeup from the Songbird team seems to confirm this -- the first section is named "Wrestling Bugzilla into shape" and they explain that their primary reason for using Bugzilla was that their workflow was already built around it. | ||
* The Songbird team uses priorities to create an informal release backlog. As the Scrum Guide [Scrum/Guide#Release_Backlog explains], release backlogs are rarely useful and sometimes detrimental. | |||