Scrum/Tools: Difference between revisions

Jump to navigation Jump to search
→‎The Bad: Phrasing.
(→‎The Bad: Phrasing.)
Line 25: Line 25:
* The authors of sdpbot note that they "made no attempt to make it generic" and that people using the software should expect to "do some work to customize it" for their needs.
* The authors of sdpbot note that they "made no attempt to make it generic" and that people using the software should expect to "do some work to customize it" for their needs.
* 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.
* The Songbird team uses priorities to create an informal release backlog, and it seems that sdpbot assumes priorities will be used this way. As the Scrum Guide [[Scrum/Guide#Release_Backlog|explains]], release backlogs are rarely useful and sometimes detrimental.
* The Songbird team uses priorities to create an informal release backlog. Though it can be modified, it seems that sdpbot by default assumes that priorities will be used this way. As the Scrum Guide [[Scrum/Guide#Release_Backlog|explains]], release backlogs are rarely useful and sometimes detrimental.
* 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.
Confirmed users
1,193

edits

Navigation menu