XP-Dev.com Concepts of Stories, Tasks and Bugs

Text: h1. XP-Dev.com Concepts of Stories, Tasks and Bugs Page has been moved to our "documentation site":http://docs.xp-dev.com/user-guide/stories-tasks-bugs.html http://docs.xp-dev.com/user-guide/stories-tasks-bugs.html → h1. XP-Dev.com Concepts of Stories, Tasks and Bugs Page has been moved to our "documentation site":https://xp-dev.com/docs/d/user-guide/project-bug-tracking/stories-tasks-and-bugs https://xp-dev.com/docs/d/user-guide/project-bug-tracking/stories-tasks-and-bugs

Text: h1. XP-Dev.com Concepts of Stories, Tasks and Bugs {toc} h2. Stories Stories are meant to capture business requirements. It should contain business language and try to capture a single functionality, task or role that a certain entity in a system does. It should be kept short, simple and to the point. For example, when building a blogging platform, a typical user story might be: bq. Bloggers would like to import their blog posts from Wordpress Wikipedia has a full entry on "user stories":http://en.wikipedia.org/wiki/User_story. Stories are answers to *What ..* questions. h2. Tasks For each story, you should define some tasks that implement the story. These are technical steps that are taken to complete and deliver the story. Taking the example from above, tasks that deliver the story might be: bq.. 1. Add a SAX parser to read Wordpress XML export format 2. Add a file upload form in the _Admin Area_ 3. Store parsed sections of SAX parser to Blog table in the database p. Tasks should answer the *How ..* questions. For each one of these tasks, you should estimate how long they are going to take. The total of this estimate will be displayed under the *Stories* tab of your project. h2. Bugs Bugs are defects that get discovered in your application/system. They are just a flat list of problems. They do not attempt to categorise or group themselves into specific functionality as what _stories & tasks_ do. You could use Bugs as a general _TODO_ list as well, and depending on your development processes, using the Bugs list as the exclusive task/issue management is perfectly fine. Just like tasks, you can estimate how long a certain bug will take and add the hours that you've worked on it. All the statistics will be shown under the *Bugs* tab of your project. → h1. XP-Dev.com Concepts of Stories, Tasks and Bugs Page has been moved to our "documentation site":http://docs.xp-dev.com/user-guide/stories-tasks-bugs.html http://docs.xp-dev.com/user-guide/stories-tasks-bugs.html