Scrum/Tools: Difference between revisions

Jump to navigation Jump to search
Line 18: Line 18:


==Bugzilla==
==Bugzilla==
'''Address:''' https://bugzilla.mozilla.org/
Some of these thoughts are based on Songbird's experience with Bugzilla, documented in their post [http://blog.songbirdnest.com/2008/12/15/songbird-path-to-agility-part-iii/ Songbird path to Agility – Part III].
Some of these thoughts are based on Songbird's experience with Bugzilla, documented in their post [http://blog.songbirdnest.com/2008/12/15/songbird-path-to-agility-part-iii/ Songbird path to Agility – Part III].


Line 31: Line 33:
* 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 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.


==Jira==
==Jira==
Confirmed users
1,193

edits

Navigation menu