Skip to content
Browse
BABOK Guide
BABOK Guide

7. Techniques

7.4 Job Stories

Agile Extension to the BABOK® Guide

Job Stories are used to represent a product backlog item (PBI) or requirement in terms of a job to be done by a stakeholder.

Job Stories focus on the motivation of the stakeholder and provide as much context as possible for the motivations, anxieties, and struggles of the stakeholder. They add contextual information that can affect how a stakeholder wants a desired feature to be and enables helps with making the right implementation decisions.

Job Stories also serve as a communication tool for stakeholders. They facilitate interaction and collaboration among individuals and focus the delivery team on the customer need, while leaving implementation details to be determined.

.1 Format

A job story follows a specific format. It can be written in first person or third person format.
A job story can be formatted as follows:

When <situation> I want to <motivation> so I can <expected outcomes>

When someone <situation>, actor(s) <motivation> so that <expected outcomes>

Example

When I want to withdraw money from my bank account, I want to know I have enough money in my account to withdraw some now so I can go out to dinner with my friends.

When someone wishes to withdraw money from his/her account, the customer wants to know if funds are available, the teller wants to know if the person banks with us, so that the person requesting can received the desired cash amount.

.2 Situation

The first element of the job story syntax is situation.

Situation provides context for when the job needs to be completed. The context of the situation encourages the delivery team to think of a wide variety of possible solutions. The more context provided, the better the delivery team can design the solution.

When there are multiple roles that would complete a job, those roles are included in the “when” statement.

The persona is not included in the situation specifically so the delivery team can focus on real customers.

.3 Motivation

The second element of the job story syntax is motivation.

Motivation focuses on the customer motivation. It can include internal and external forces for motivation.

Desired features or solutions are specifically not included in Job Stories in order to focus on the customer.

.4 Expected Outcomes

The third element of the job story syntax is expected outcomes.

The outcome should satisfy or alleviate the motivation which prompted the situation.

.1 Strengths

  • This format reduces assumptions regarding the role and removes the persona biases.

  • It can be set up for cause and effect scenarios.

  • This format focuses on stakeholder motivations instead of defining implementation.

  • It is helpful for user experience design.

  • Teams find it easier to empathize with the stakeholder.

  • Removes focus on features and instead focuses on the stakeholder's desired future state.

  • Teams can use Job Stories and User Stories together on backlog. The job story indicates the motivation and outcome for the stakeholder, while the user story indicates features that could solve the problem.

.2 Limitations

  • This format has a tendency to be more verbose than User Stories because of the context, roles, and outcomes included.

  • Job Stories can decompose into multiple smaller Job Stories which require management through refinement and prioritization.

  • If Job Stories and User Stories are both on the product backlog, teams can get confused when switching between formats.