Create better user stories

The Grimm Tool analyzes user stories in real-time and immediately notifies you about quality defects in your user stories.

Sign up with email

No defects? Then we can automatically generate functional models of a role or sprint's user stories for you. Contact g.lucassen@uu.nl to learn how!

Example Grimm Tool output

Mashhacks - 50 stories


  • #0

    As a user, when I hear a strange noise, I want to be able to look up what it might be, and get information.

    Not atomic

    A user story should consist of only one feature. Avoid using conjunctions such as and or &.

    Suggestion: As a user, when I hear a strange noise, I want to be able to look up what it might be, and get information.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #1

    As a user, when the plane drops in altitude, I want to know what happened, what the pilot is trying to do, and obtain general information on it.

    Not atomic

    A user story should consist of only one feature. Avoid using conjunctions such as and or &.

    Suggestion: As a user, when the plane drops in altitude, I want to know what happened, what the pilot is trying to do, and obtain general information on it.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #3

    As a user, I want to know flight weather conditions for my journey.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #4

    As a user, I want potential causes of turbulence. (weather, unstable air)

    Not minimal

    User stories should not include additional information aside from core user story text. Move this to the description, acceptance criteria or comments.

    Suggestion: As a user, I want potential causes of turbulence. (weather, unstable air)

    Not minimal

    User stories should not include additional information hidden in brackets. Move this to the description, acceptance criteria or comments.

    Suggestion: As a user, I want potential causes of turbulence. (weather, unstable air)

    Irregular format

    This user story its format deviates from the format used by the majority of your user stories

    Suggestion: Use the most common template: As a, I want to

  • #5

    As a user, I want to know when we are about to land, and obtain expectations in terms of altitude and related noises.

    Not atomic

    A user story should consist of only one feature. Avoid using conjunctions such as and or &.

    Suggestion: As a user, I want to know when we are about to land, and obtain expectations in terms of altitude and related noises.

  • #6

    As a user, I want to look at my pilot’s turbulence record prior to and during a flight.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #7

    As a user, I want to look at my flight’s turbulence record prior to and during a flight.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #12

    As a user, I want to be alerted to upcoming potential turbulence before it occurs (can be crowdsourced based on previous data)

    Not minimal

    User stories should not include additional information hidden in brackets. Move this to the description, acceptance criteria or comments.

    Suggestion: As a user, I want to be alerted to upcoming potential turbulence before it occurs (can be crowdsourced based on previous data)

  • #16

    As a user, I want to know flight weather conditions for my journey.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories

  • #22

    As a user, I want to find flights by airline (by current/upcoming flights)

    Not atomic

    A user story should consist of only one feature. Avoid using conjunctions such as and or &.

    Suggestion: As a user, I want to find flights by airline (by current/upcoming flights)

    Not minimal

    User stories should not include additional information hidden in brackets. Move this to the description, acceptance criteria or comments.

    Suggestion: As a user, I want to find flights by airline (by current/upcoming flights)

  • #29

    As a user, I want to look at my pilot’s turbulence record prior to and during a flight.

    Duplication

    There is another user story in this set identical to this one. Why not remove one?

    Suggestion: Remove all duplicate user stories