job-stories

To write job stories, use the format: "When [situation], I want to [motivation], so I can [outcome]". This structure captures user needs and desired outcomes based on specific situations rather than user roles.

Job stories focus on the underlying motivations and situations driving user behavior, whereas traditional user stories emphasize user roles. This shift centers product development on the "job to be done" (JTBD) rather than persona attributes.

Generating acceptance criteria from a job story involves defining detailed, outcome-focused conditions that validate the user's motivation and desired outcome. This ensures backlog items directly map to user needs.

You need to provide product and feature context, design links, and user scenarios. Supplying these inputs ensures the generated job stories comprehensively capture the specific user situations and motivations.

Use the JTBD framework when you need to articulate user needs in a structured format that focuses on motivations and situations. It is particularly useful for creating backlog items that express desired user outcomes.

Yes, job stories can be generated with detailed, outcome-focused acceptance criteria. This provides development teams with clear conditions to validate that the feature meets the expressed user motivation and outcome.