Scrum/Tools: Difference between revisions

Scrum/Tools (view source)

18 bytes removed , 3 June 2011

Confirmed users

1,193

edits

@@ Line 16: / Line 16: @@
 === 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 the team 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 login early in the project. Without much information, this story would be fairly high-level, for example "Users should be able to log into the site." Later, the team could add specific details as additional stories -- "Users should be able to log into the site using their email addresses", "Users should be able to log into the site from their mobile devices", etc. These stories could be added as dependencies of the first.
+** For example, a team building a website might create a user story for login early in the project. Without much information, this story would be fairly high-level, for example "Users should be able to log into the site." Later, the team could add specific details as additional stories -- "Users should be able to log into the site using their email addresses", "Users should be able to log into the site from their mobile devices", etc. These stories could depend on the first.
 * The Songbird team has written a tool named SDPBOT which generates reports from Bugzilla tickets. The team additionally released SDPBOT under an open-source license.