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

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


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


  • Who
  • What
  • When
  • Where
  • Why


  • Card
  • Conversation
  • Confirmation

Definition of Done

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

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
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 The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.