Directory
Agile Technique Brief: Requirements Cards
Agile methodologies like Scrum and Extreme Programming (XP) often build on "user stories" as a way of capturing and tracking feature requirements. Kent McDonald, who authored this technique brief, prefers to call them requirements cards in order to include customers and stakeholders. Whichever term you prefer, the idea is to create only enough requirements detail to scope the project, without burying the team or the schedule in exhaustive feature details that are likely to change anyway.
As a bonus, this technique also includes a means of describing what "done" means for that particular feature, by describing potential scenarios and the expected result. We can't promise happy ever after, but at least you'll know where the treasure is hidden.
