FunctionalRequirementsDefined by IEEE 830Contractual in natureExample:3.4) The product shall have a gasoline-powered engine.3.5) The product shall have four wheels. 3.5.1) The product shall have a rubber tire mounted to each wheel.3.6) The product shall have a steering wheel.3.7) The product shall have a steel body.
Use CasePart of Rational Unified Process (RUP)Large in scopePermanent artifactsPurpose is to document agreement
Interaction ScenarioDetailed description of a user’s interactionwith a systemLarger in scope than a use caseEmphasis on realism and detailCharacteristics: Setting Actors Goals Events
Benefits of storiesFocus is on user goals rather than systemattributesDefer detail till neededPromote tacit knowledge across teamHumans remember storiesNo illusion of precisionStories are not contractual obligations
ResourcesScrum.org - http://www.scrum.org/Scrum Alliance - http://www.scrumalliance.org/All Things Product Owner - http://www.romanpichler.com/blog/user-stories/User story tools: http://www.userstories.com/productsUser Stories Applied by Mike Cohn
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.