If you are going for your PMP this year, make sure you know the three Cs of user story creation for your agile team. They are a simple framework for how agile teams gather and refine requirements.
Card
The first C is the card. Write the user story requirement on a physical or digital user story card. The card captures the user need in a simple format: “As a [user], I want [capability] so that [benefit].”
Conversation
The second C is conversation. This is where the real work happens. The customer describes what they need. The developers explain what is technically possible. The testers define quality requirements and acceptance criteria. The product owner facilitates. These conversations build a shared understanding of what needs to be built and how to know when it is done.
Confirmation
The third C is confirmation. Once the work is complete, confirm that you built exactly what was needed. This might happen during a sprint review where the product owner and stakeholders see the completed feature. Or it might happen through direct validation with the customer. Confirmation means the user story is truly done.
Why It Matters
These three Cs prevent the common agile pitfall of teams building the wrong thing. A card alone is not enough. Conversation builds shared understanding. Confirmation ensures delivery matches intent.
Know the three Cs and you understand how agile teams gather and validate requirements.
– David McLachlan
You can see what people are saying about David McLachlan here: REVIEWS
Navigate to Free Project Management and Leadership Articles through the links on the right (or at the bottom if on Mobile)
Also available are my Project Management Templates – they’re a great way to save 100s of hours when you’re first starting out:
 50+ Project Management Templates in Excel and PowerPoint (Excel Gantt Chart, Risk Matrix, RACI, Stakeholder Matrix and more!) |
 Pre-made Project Management Plan Templates: Save 100 HOURS! |
