Confirmed users
1,193
edits
Scrum/Tools: Difference between revisions
Jump to navigation
Jump to search
Added Agilo and stubs for other good products.
(Alphabetical order.) |
(Added Agilo and stubs for other good products.) |
||
| Line 1: | Line 1: | ||
== Bugzilla == | ==Agile Bench== | ||
'''The Good''' | |||
'''The Bad''' | |||
==Agilo== | |||
'''Address:''' http://www.agile42.com/agilo/ | |||
'''The Good''' | |||
* Agilo seems very powerful. Users can create tasks, move them into particular Sprints, prioritize them with a drag-and-drop interface, and perform most of the other tasks required for managing a Scrum project. Additionally, Agilo automatically generates burndown charts and other statistics. | |||
* Because Agilo is built on top of Trac, it inherits all of the features of Trac (repository integration, etc.). In addition, it can be extended by any plugin that works with Trac. | |||
'''The Bad''' | |||
* Agilo is very difficult to use. Though this seems minor, it makes the benefits of the software almost a moot point -- it doesn't matter how poewrful Agilo is if no one can figure out how to use it. | |||
==Bugzilla== | |||
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]. | ||
'''The Good''' | |||
* The bug dependency feature seems very useful. Scrum recognizes that a product cannot be fully defined from the start. As a result, Scrum encourages teams to write basic descriptions of distant requirements and add specific details as they become apparent. The bug dependency tool may allow for this. | * The bug dependency feature seems very useful. Scrum recognizes that a product cannot be fully defined from the start. As a result, Scrum encourages teams to write basic descriptions of distant requirements and add specific details as they become apparent. The bug dependency tool may allow for this. | ||
** For example, a team building a website might create a user story for user login early in the project. Without much information, this story would be fairly high-level, for example "A user should be able to log into the site." Later, the team could add specific details as additional stories -- "A users should be able to log into the site with his email addresses", "The user should be able to find the 'Login' link in the top-right corner of the site", etc. These stories could depend on the first. | ** For example, a team building a website might create a user story for user login early in the project. Without much information, this story would be fairly high-level, for example "A user should be able to log into the site." Later, the team could add specific details as additional stories -- "A users should be able to log into the site with his email addresses", "The user should be able to find the 'Login' link in the top-right corner of the site", etc. These stories could depend on the first. | ||
| Line 8: | Line 27: | ||
* The Songbird team has written a tool which generates reports from Bugzilla tickets. The tool, called [https://code.google.com/p/sdpbot/ sdpbot], is released under an open-source license. | * The Songbird team has written a tool which generates reports from Bugzilla tickets. The tool, called [https://code.google.com/p/sdpbot/ sdpbot], is released under an open-source license. | ||
'''The Bad''' | |||
* 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. | ||
| Line 15: | Line 34: | ||
== | ==Jira== | ||
'''The Good''' | |||
'''The Bad''' | |||
==Open Atrium== | |||
'''The Good''' | |||
* Open Atrium provides a very good task-tracking tool called "Case Tracker". Case Tracker allows cases to be categorized (bug, feature, or task), assigned, and grouped into projects. Additionally, Case Tracker can send a notification to some or all team members when a case is updated. | * Open Atrium provides a very good task-tracking tool called "Case Tracker". Case Tracker allows cases to be categorized (bug, feature, or task), assigned, and grouped into projects. Additionally, Case Tracker can send a notification to some or all team members when a case is updated. | ||
* Open Atrium is extremely customizable. Because Open Atrium is based on Drupal, it can even be extended with the thousands Drupal modules that already exist. | * Open Atrium is extremely customizable. Because Open Atrium is based on Drupal, it can even be extended with the thousands Drupal modules that already exist. | ||
* Like all Development Seed software, Open Atrium is extremely easy to use | * Like all Development Seed software, Open Atrium is extremely easy to use | ||
'''The Bad''' | |||
* As a beta product, Open Atrium has some design flaws. The notification system is especially problematic, often encouraging users to spam one another unnecessarily. | * As a beta product, Open Atrium has some design flaws. The notification system is especially problematic, often encouraging users to spam one another unnecessarily. | ||
* Open Atrium's Case Tracker does not allow cases to be assigned to multiple team members. This can cause problems when two or more team members are assigned a collaborative task, as only one of them will see the task in her list of assigned tasks. | * Open Atrium's Case Tracker does not allow cases to be assigned to multiple team members. This can cause problems when two or more team members are assigned a collaborative task, as only one of them will see the task in her list of assigned tasks. | ||
| Line 30: | Line 55: | ||
* Open Atrium does not provide a burndown chart, and there do not seem to be any Drupal modules that can provide one | * Open Atrium does not provide a burndown chart, and there do not seem to be any Drupal modules that can provide one | ||
* Though Open Atrium is very customizable, many customizations are wiped out whenever the system is upgraded. Though not impossible, building customizations in such a way that they do not interfere with future updates can be difficult and time-consuming. | * Though Open Atrium is very customizable, many customizations are wiped out whenever the system is upgraded. Though not impossible, building customizations in such a way that they do not interfere with future updates can be difficult and time-consuming. | ||
==Trac== | |||
'''The Good''' | |||
'''The Bad''' | |||