Douglas Talbot & Sandy Mamoli One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements. Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?