Background on what User Stories are:

The UX of User Stories


An ideal tool would:

  1. Be online
  2. Enable quick collecting of story titles
  3. Enable to map/share/group the collected stories
  4. Allow open discussion around stories
  5. Enable collaboration for collecting stories and elaborating their meanings

I'm quite sure I saw something published recently, but can't find it.

  • Good question. Tools I know and have used are more issue tracking tools (redmine.org, asana.com and pivotaltracker.com). They're not explicitly for managing user stories but they support issues with title, description + comments (-> discussions) and also prioritization. Mar 26, 2012 at 9:32
  • Maybe 'idea management' tools or software is a good search term for further research? Mar 26, 2012 at 9:33
  • User Stores are part of the Agile process. Research SCRUM and Agile management tools. There's dozens of them out there.
    – DA01
    Mar 26, 2012 at 13:24
  • Sorry to bump a "closed" thread but YET AGAIN this is another example of a thread being closed for no good reason. This is a valid question, it is good for Q&A format and I found it because I typed exactly this in google.
    – Mrk Fldig
    Oct 13, 2014 at 20:09
  • This question is being discussed on meta
    – stevec
    Feb 28, 2021 at 11:19

5 Answers 5


There are many tools for this task. The closest I'm aware of that explicitly focuses on users story management is sprint.ly.

Most issue tracking systems have plugins for this purpose too; the two that I use—Redmine and Jira—both have so-called Agile plugins for tracking user stories and managing story points, burndown charts, etc.


We use Confluence, a great tool for user stories! It works like a Wiki, but with richer UI and functionality.

Be online

Confluence can be used as an intranet and at the same time be accessed outside of the company via Internet.

Enable quick collecting of story titles

Confluence have built in macros like table of content and other useful content containers such as children display. Content containers in Confluence

Enable to map/share/group the collected stories

You can filter content by users, groups, labels and tags, which is shared instantly. tags in Confluence

Allow open discussion around stories

Every page have comments, which is threaded if there are many comments.

add comment button

Enable collaboration for collecting stories and elaborating their meanings

Since it’s a Wiki, you can


Trello is the tool we use. It's a board with lists which contains cards.

User stories and sprints We write down the userstories as titles of the cards. When all user stories are collected we subdivide them onto the different lists. The lists stand for the sprints. When we begin with sprint 1, we add soms more list next to it: working on, test and done.

Working on, test and done When a ticket (card) is picked up by a team member, it's dragged to the working on list. After the ticket is ready to test by the client, the tickets is dragged to the test list. When the client approved the ticket, it will be dragged to done.

Discussion around stories A card can be opened. On the card checklists and comments can be submitted. Very useful for making a task list and keep track of the communication about a user story. Also a team member can be attached to a card so everyone can see who's working on that ticket.

And yes, our clients also use the same board (per project). This way they have a nice inside view in the project.


We've used VersionOne at Western Union Business Solutions successfully for several years. It supports all of the features you've mentioned and a lot more.


Checkout https://easybacklog.com/ it's still in beta and while it doesn't exactly hit what you're looking for it does offer a solid structure to agile user stories.

I should also say that I haven't used this for a project. I'm still trying to figure out how to help my company make the shift to agile user stories instead of big requirements docs.

Not the answer you're looking for? Browse other questions tagged or ask your own question.