How to mess up your user stories

User Stories are more or less the standard format for managing your product backlog in agile projects. So this is my trigger to let you know how to completely mess them up 😉 I collected a short list of my favorites, let’s start.

Missing Roles

Don’t define any roles! It is much more fun to write a user story from the view of a generic user. Don’t waste your time to define all these useless roles. If I write a story about the possibility to delete any user from the database it should be clear for anyone that I was talking about some kind of admin.

This blog post has been moved to


12 thoughts on “How to mess up your user stories”

  1. * Don’t have a Product Owner: the Scrum Master is able to easily be the Product Owner. And as the Scrum Master should be someone of the development team, the team has full responsibility and freedom!
    * Don’t write User Stories at all: as the team has full responsibility and freedom to define the product, there’s no need to have any User Stories or any other kind of specifications.

    Have fun :-)
    Marc Bless

  2. *The scrum master as product owner? Just a manager should be enough. She can write the user stories….
    *Don’t let anybody know what is on the productbacklog. It will save you al lot of questions!
    *If you make a productbacklog make sure is has at least enough stories for the next 2 years. You don’t want the change priorities all the time!

  3. Pingback: (Agile) Testing
  4. User Stories are documentation. Documentation can be easily out-sourced to an external junior consultant who is new to the industry …

  5. Generally I don’t read article on blogs, however I wish to
    say that this write-up very pressured me to take a look at and
    do it! Your writing style has been surprised me.
    Thanks, very nice post.

Leave a Reply

Your email address will not be published. Required fields are marked *


Notify me of followup comments via e-mail. You can also subscribe without commenting.