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

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
User Story Creation
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.
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...