The biggest problem in an agile Project is determining the Product Backlog — what will be built? We know we don’t want «Big Analysis Up Front» because we know that over-specifying will get us into trouble; but we also need to know what we’re building so that we can discuss it with our Stakeholders and can estimate how much time and effort it will take. How do we reconcile these two (seemingly) inconsistent needs? In this talk Dan describes a strategy that begins with usability studies and ends with actionable Stories. The strategy involves Story Mapping (from Jeff Patton), Atomic Use Cases, and StoryoTypes (from Gerard Meszaros). This blended approach is both straightforward and effective – come see how it’s done!