Confirmed users
1,193
edits
Scrum/Tools: Difference between revisions
→Bugzilla
No edit summary |
|||
| Line 32: | Line 32: | ||
* 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. 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. | * 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 | * 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 hints at this -- the first section is named "Wrestling Bugzilla into shape" and the next sentence explains that the team primarily chose Bugzilla for managing Scrum because they had already been using it. | ||
==Jira== | ==Jira== | ||