User Story Creation

Agile Lean Product User story

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

Get PDF

Tags

Abbreviation Agile image Infographic Poster Scrum Software development User story User Story Creation User Story Example User Story Template What Is User Story

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.

Resources

mountaingoatsoftware.com easyagile.com medium.com acronymat.com mountaingoatsoftware.com acronymat.com

Similar posters

Eisenhower Matrix

Eisenhower Matrix The Eisenhower Matrix, also known as the Urgent-Important Matrix, is a tool for organizing tasks by their urgency and importance to improve productivity and decision-making. It divides tasks into four quadrants based on these criteria. Do Important and Urgent Tasks in this quadrant require immediate attention and are essential to your goals. These are often...

Maker's vs Manager's schedule

Maker's vs Manager's schedule The differences between a maker’s and a manager’s schedules stem from their respective workflows’ distinct nature. Makers rely on uninterrupted time blocks to tackle complex, creative problems requiring deep focus and sustained attention. Managers need flexibility to oversee multiple responsibilities, make decisions, and collaborate effectively across teams. As such, it is essential to thoughtfully assess...

Mission Statement

Mission Statement Long-term organization purpose, values and objectives. It should describe why it matters. This way it contributes to identity creation.

Value Stream Mapping

Value Stream Mapping The Value Stream Mapping is a Lean technique for managing flow and improving processes allowing to track the flow through a process.

Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively

Spotify Health Check

Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.

Maslow's Hierarchy Of Needs

Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.

RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.

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.