Stories, Tasks and Bugs

Posted by rs picture rs on Tue 03 Mar, 2009 05:23:19 +0000

I do realise that I have been postponing the elusive wiki guide on using as a full agile development tool, and I do appologise for that.

So, to kick off the article trail, I’ve written some short notes on what I think Stories, Tasks and Bugs mean in Here is the wiki article.

However, this article (and future ones) are only guidelines – you are free to decide on how you’d like to use

For example, KeyKeeper uses Bugs as a general TODO list. I on the other hand a “personal” project in and use the wiki to share ideas and information with my significant other.

I would love to hear some feedback on the article. Do put your comments on entry, or drop a note in the forums, or just raise a support ticket.

View 2 comments


Floris picture

Floris on Wed 04 Mar, 2009

Clear explanation, thanks ;-)

I use stories as ‘subprojects’, e.g. you develop a website like XP-Dev (agile development tools), the stories are:
- Work out the idea (subtasks: design, structure, etc.)
- Create a simple user system (subtasks: login page, user settings, etc.)

But I think it’s useless and unclear to use that classification, to adopt stories in that way. So I’ll give the usage mentioned on the wiki page a try.

depasquale picture

depasquale on Fri 06 Mar, 2009

Very useful explanation.

I’m using you application simply referring the standard Project Management terms.

  • Story = Milestone: describe a series of objectives to reach in a given planned time (possibly) during development – for reference) -.
  • Tasks describe any activity to perform in a planned time during a Milestone life cicle.
  • Bugs are used to trace eventual problems occurred during testing and/or project validation.

This classification gives me the possibility to quickly assign a revision label to my projects. For example AAA 1.3.29 is the label for a project named AAA where 1 represents a generic state in project development (could be a phase such as proof of concept, prototyping, industrialization, and so on), 3 represent the current open milestone, and 29 is the last bug fixed since milestone 3 has been opened.

Anyway thanks a much for this service...


You do not have sufficient permissions to comment

Blog Entry Options

Blog Options

Blog Archives


Blog Entry and Comments