User and Job Stories

A catalog of distinct user actions

User stories are an industry standard way to express the requirements of different user groups. Wherever possible, write stories that target a single persona. User stories follow this formula: As a __(user persona)__ I want to __(perform some action)__ so that __(outcome or rationale)__.

Core Elements

"As a"... (Persona)

This is simply the user persona segment that the story describes

If you find yourself writing a lot of "as any user" stories, keep in mind an emerging trend toward incorporating Job Stories, which substitute a "when" scenario for the persona and reflect a more pragmatic (some argue more "why" driven) way of expressing requirements. The good news is that Userforge lets you combine user and job stories in one place!

"I want to"... (Action)

Keep actions short and to the point. When exported, into PM software, these will be the "summary" line and so should stand alone to orient a reader to the core of the functionality.

"So that"... (Rationale or Outcome)

This is where the "why" of the feature or functionality can begin to be expressed. It may be necessary to express practical outcomes, but often these are better listed as Acceptance Criteria

Acceptance Criteria

Acceptance Criteria (a/c for short) express the minutiae of a feature and can become quite granular. The more complex a story is, the greater its need for some detailed a/c to ensure clarity and common understanding.

Too many or overly complex acceptance criteria may indicate an opportunity to break large stories into several smaller ones.

Additional Info

Userforge provides several "Additional Info" sidebar options to enrich stories. These make space for research insights and production notes that add relevant context without cluttering the core story.

Userforge Stories in Jira:

The beautiful clarity of user stories written in Userforge extends to our Jira Software integration as well:

Stories and acceptance criteria are specially formatted in Jira for extra clarity

Additional Integration Features

  • Changes made in Userforge are updated and logged to Jira history tab

  • Comments made in Jira are visible in Userforge (maintains a single source of truth)

  • On some plans, story status and estimates are also visible in Userforge