When adding a story to CardConversationConfirmation.com (CCC) the user has a choice of adding the data in one of two forms. This is derived from the forms available on PlanningPoker.com (PP) to ensure compatibility between the two tools. To get the best from CCC add the data in the structured form to get the best agile benefit from the tool and the project - in order to be agile the method needs to be well factored - well optimised to reduce waste as much as possible. One might think that a simple list achieves this best but in fact adding just a little more information to that list improves agile benefit and then adding more begins to reduce that benefit again. This is can be represented on a distribution curve thus:

The simple list is where one might be using CCC with the free form user stories in terms of agile benefit. The structured list is using the AS A, I WANT TO and SO THAT fields to record user stories and this offers a greater agile benefit to the data that represents the requirements without adding in too much additional data to supply the structure. Beyond this the description of the requirement whether it remains structured or not is likely to contain more information - the agile benefit tails off because recording this level of information now may not be necessary and the level of detail may never be necessary - if it is then it should be added as sub user stories in the structured form and grouped into themes rather than some free-form extended prose.

This is excellently qualified by Mike Cohn's recent blog which you should read for the detail - but here is a summary of the agile benefits described there.

1. They are written in the first person which helps the team to empathise with the requirement.

2. The product owner can prioritise without additional effort.

3. The boiler plate as Mike puts it, or structure template, makes the user stories easy to read and the style becomes familiar.

4. Acceptance tests (Confirmation in CCC) or satisfaction criteria are easy to derive.

5. The SO THAT statement emphasises to the team why the requirement is needed.

6. Estimating with planning poker is facilitated and a consensus can be reached in a shorter time.

7. Great for socialising the requirements across the whole team.

8. Helps identify alternative solutions.