User Story Creation

Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Read more
Article

User Story Creation is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.


Based on the 3Cs process, a User Story creation starts with writing it using the user/persona, his goal, and the resulting benefit on a CARD (virtual/physical) to enable starting a CONVERSATION.


User story - card

The content of the card should be clarified via CONVERSATIONs with the team/relevant people about the created story and refine it. Repeatedly check if the story meets INVEST criteria and answers the 5W questions. Acceptance criteria may be refined or added, as well as schemas, wireframes, mock-ups, specifications, etc.


User story - conversation

The CONVERSATIONs may lead to the conclusion that the story is too big for one iteration (INVEST-Small/Estimable), and decision to split it into 2 new stories (INVEST-Negotiable).


Split stories

Based on the previous, the CONFIRMATION of what will be built needs to be achieved. The content of the story should answer all the 5Ws questions and meet the INVEST criteria. Now you should have a story that is ready to be worked on, relevant people are familiar enough with it and the team should accept the story to be ready for development. The user story quality is dependent on the Definition of Done (DoD) and it has to be possible to meet the DoD after the implementation.


Used concepts

INVEST

  • Independent
  • Negotiable
  • Valuable
  • Estimable
  • Small
  • Testable

5Ws

  • Who
  • What
  • When
  • Where
  • Why

3Cs

  • Card
  • Conversation
  • Confirmation

Definition of Done

The shared understanding of when a User Story is considered done.

Similar posters

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...
STEEPLED
STEEPLED STEEPLED - Social, Technological, Economical, Environmental, Political, Legal, Ethical and additional compared to STEEPLE is Demographic.