The Three C’s Of User Story
Agile User story

The Three C’s Of User Story

There are three critical aspects known as The Three C’s of User Story, namely Card, Conversation, and Confirmation.
Read more
Get PDF
Tags
Abbreviation Agile Card Confirmation Conversation image Infographic Picture Poster Scrum Software development the three c's User story what are the three c's
Article

The Three C’s Of User Stor


User Story is a short description of the value to be delivered to a customer. In addition to that, there are three critical aspects known as The Three C’s of User Story, namely Card, Conversation, and Confirmation. These three aspects describe the successful creation of a User Story.


Card

A written description of the story. It includes just enough to identify the requirement, so it can be used for planning. It can capture the cost and priority of the User Story.


Conversation

The next step is the discussions with others to gain a shared understanding. The conversation is mostly verbal and supplemented with documentation.


Confirmation

Agreement on what to build needs to be reached, which can be recorded as acceptance tests. They define when the story can be considered as done.


The Three C's of User Story steps

Resources
agilealliance.org ronjeffries.com uxdesign.cc enfocussolutions.com www.visual-paradigm.com

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
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
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.