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

Cisco Commerce - 20 stories


  • #0

    As a public services staff in the Preservation Conservation and Digital Imaging services group, a researcher wants to order an image and Houghton PS staff needs to tell the researcher what the size or resolution of the image is without looking it up via DRS Webadmin.

    Not atomic

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

    Suggestion: As a public services staff in the Preservation Conservation and Digital Imaging services group, a researcher wants to order an image and Houghton PS staff needs to tell the researcher what the size or resolution of the image is without looking it up via DRS Webadmin.

    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, So

  • #1

    As a programmer building image display applications, I need to obtain admin metadata access rights for public/private DRS content (URNs)

    Not minimal

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

    Suggestion: As a programmer building image display applications, I need to obtain admin metadata access rights for public/private DRS content (urns)

    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, So

  • #2

    As a humanities faculty member, I want the DRS to support image content delivery via the International Image Interoperability Framework API so that web applcations from Stanford, Yale, and Johns Hopkins can compare Harvard digitized manuscripts with versions from their institutions and I can use those comparisons for research and teaching

    Indicator Repetition

    This user story contains multiple roles or actions. You should split these in separate user stories.

    Suggestion: As a humanities faculty member, I want the DRS to support image content delivery via the International Image Interoperability Framework API so that web applcations from Stanford, Yale, and Johns Hopkins can compare Harvard digitized manuscripts with versions from their institutions and I can use those comparisons for research and teaching

    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, So

  • #3

    As a cataloger, I want to be able to create linked open data using persistent links to content (URNs) in the DRS

    Not minimal

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

    Suggestion: As a cataloger, I want to be able to create linked open data using persistent links to content (urns) in the DRS

  • #4

    As a collection owner, I want to be able to hire a programmer to write custom DRS content delivery services (PDS, IDS, SDS), pulling up some descriptive metadata (Citation), structural metadata, and enough technical metadata to know the file type to be rendered) for meeting the special needs of my users.

    Not atomic

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

    Suggestion: As a collection owner, I want to be able to hire a programmer to write custom DRS content delivery services (PDS, IDS, SDS), pulling up some descriptive metadata (Citation), structural metadata, and enough technical metadata to know the file type to be rendered) for meeting the special needs of my users.

    Not minimal

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

    Suggestion: As a collection owner, I want to be able to hire a programmer to write custom DRS content delivery services (pds, ids, sds), pulling up some descriptive metadata (citation), structural metadata, and enough technical metadata to know the file type to be rendered) for meeting the special needs of my users.

  • #5

    As a public user, I want a web application that can locate all the DRS objects related to a specific collection or topic, e.g. ''Eleanor Roosevelt.''

    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 public user, I want a web application that can locate all the DRS objects related to a specific collection or topic, e.g. ''Eleanor Roosevelt.''

    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, So

  • #6

    As a provider of DRS imaging services, I need access to terms of use statements for objects. For example, aA limited menu of HL use-permissions statements could be formulated, stashed in DRS, and associated with individual resources, or whole classes of resources. When we allow our digital resources to be used outside of our library systems (e.g. within DPLA, or other applications like the Library Lab funded Zeega project), the object can travel with the requisite use-permissions.

    Not atomic

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

    Suggestion: As a provider of DRS imaging services, I need access to terms of use statements for objects. For example, aA limited menu of HL use-permissions statements could be formulated, stashed in DRS, and associated with individual resources, or whole classes of resources. When we allow our digital resources to be used outside of our library systems (e.g. within DPLA, or other applications like the Library Lab funded Zeega project), the object can travel with the requisite use-permissions.

    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 provider of DRS imaging services, I need access to terms of use statements for objects. For example, aA limited menu of HL use-permissions statements could be formulated, stashed in DRS, and associated with individual resources, or whole classes of resources. When we allow our digital resources to be used outside of our library systems (e.g. within DPLA, or other applications like the Library Lab funded Zeega project), the object can travel with the requisite use-permissions.

    Not minimal

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

    Suggestion: As a provider of DRS imaging services, I need access to terms of use statements for objects. For example, aA limited menu of HL use-permissions statements could be formulated, stashed in DRS, and associated with individual resources, or whole classes of resources. When we allow our digital resources to be used outside of our library systems (e.g. within dpla, or other applications like the library lab funded zeega project), the object can travel with the requisite use-permissions.

    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, So

  • #7

    As a provider of DRS imaging services, I need access to preferred citations. Default digital object citations could be formulated by script from catalog records, and repositories could be allowed to replace these programmatically-produced citations with customized citations, if needed, using the DRS Web Admin user interface.

    Not atomic

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

    Suggestion: As a provider of DRS imaging services, I need access to preferred citations. Default digital object citations could be formulated by script from catalog records, and repositories could be allowed to replace these programmatically-produced citations with customized citations, if needed, using the DRS Web Admin user interface.

    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 provider of DRS imaging services, I need access to preferred citations. Default digital object citations could be formulated by script from catalog records, and repositories could be allowed to replace these programmatically-produced citations with customized citations, if needed, using the DRS Web Admin user interface.

    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, So

  • #8

    As a collection manager (Amy Benson), I want to be able to pass in a set of URNs, possibly as a result of a HOLLIS search), and get that content back.

    Not atomic

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

    Suggestion: As a collection manager (Amy Benson), I want to be able to pass in a set of URNs, possibly as a result of a HOLLIS search), and get that content back.

    Not minimal

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

    Suggestion: As a collection manager (amy benson), I want to be able to pass in a set of URNs, possibly as a result of a HOLLIS search), and get that content back.

  • #9

    As a developer who presents images, I need the granularity to get information about the images associated with a VIA URN, so I can present the user with choices.

    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, So

  • #10

    As a university press, I want to be able to request publication rights throu a S/W interface, so taht I can speed e-book publication

    Indicator Repetition

    This user story contains multiple roles or actions. You should split these in separate user stories.

    Suggestion: As a university press, I want to be able to request publication rights throu a S/W interface, so taht I can speed e-book publication

  • #11

    As a developer, I would like to access individual data fields, such as full text. (Andy Silva)

    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 developer, I would like to access individual data fields, such as full text. (Andy Silva)

    Not minimal

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

    Suggestion: As a developer, I would like to access individual data fields, such as full text. (andy silva)

    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, So

  • #12

    As a customer, I would like to deposit and retrieve ALTO OCR data. (Andy Silva)

    Not atomic

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

    Suggestion: As a customer, I would like to deposit and retrieve ALTO OCR data. (Andy Silva)

    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 customer, I would like to deposit and retrieve ALTO OCR data. (Andy Silva)

    Not minimal

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

    Suggestion: As a customer, I would like to deposit and retrieve ALTO OCR data. (andy silva)

    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, So

  • #13

    As a user, I want an RSS feed so I can collect records as new titles go online, since HL will digitize pamphlets for years.

    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, So

  • #14

    As a data discovery service, I want to harvest metadata so that our users can discover and download original content.

    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, So

  • #15

    As a developer, I need bulk access to metadata (TBD) so I can preprocess the data set.

    Not minimal

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

    Suggestion: As a developer, I need bulk access to metadata (tbd) so I can preprocess the data set.

    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, So

  • #17

    As a developer, I would like to be able to search the DRS passing in an XML file of search parameters rather than a query string on the URL.

    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, So

  • #18

    As an admin user, I would like to have granular access to all external metadata about the object, e.g. HOLLIS metadata, annotation metadata.

    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 an admin user, I would like to have granular access to all external metadata about the object, e.g. HOLLIS metadata, annotation metadata.

    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, So

  • #19

    As a programmer working with images from the DRS, I need to be able to look up technical metadata about images so that I can properly size and position them in my web application e.g. image height/width for the ARTstor SharedShelf project, image resolution).

    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 programmer working with images from the DRS, I need to be able to look up technical metadata about images so that I can properly size and position them in my web application e.g. image height/width for the ARTstor SharedShelf project, image resolution).

    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, So