Can extensive written requirements be dispensed with in favor of lighter weight 'stories'? It sounds easier, but can it really be as good? We'll start this session by staging a showdown between traditional and agile requirements. Participants will form teams, create requirements documents, do development (no technical skill or computers needed), and evaluate the results. Next, participants will learn by doing, as we build a 3-part model for agile requirements: User Story, Conversation, and Acceptance Criteria. Participants will leave with a solid understanding, and practical skills.