The user stories is the most imperative part of agile development and when we see the user stories more closely then it has three imperative aspects. These aspects are known as three C’s provided by Ron Jeffries as a good user story creation framework. They are known as Card, Conversation and confirmation respectively.
Why is it useful?
It is a known fact of that user stories are having a currency value in the agile development process as they provide focus of the estimation, team activities, sprint planning and ensure that the team is actually delivering the product customer wants.
These give us the complete framework, abstract ideas that we can discuss it with the team in order to get better results. These stories ought to be constructed in a manner that they can be executed and improved as per demands with time.
Let us have a deep look on this three C’s of user stories that how these are going to help in agile development.
- First C of this series is for Card, as the stories are written on the cards and there is a lot of room to write more information according to the requirement. But, there is no need to fill up the whole card rather the main idea is written which will reflect the cost and priority.
- Second C is for Conversation, now when the team is going to work on this story, they will have to read the card and get the idea and then they go for conversation with the owner so that they can communicate everything needed.
- The third and last C is for Confirmation, the team needs to confirm in the end that of the story that whatever needed to work is attained or not.
This was all about the three C’s and their importance.
— Slimane Zouggari