Agile Requirements Decomposition
Download as PPTX, PDF22 likes14,644 views
The document discusses decomposing a vision into user stories through epics and features. It provides examples of a vision, epics, features, and user stories for a peer-to-peer payment system. Teams worked through exercises to identify features and create corresponding user stories. Story mapping was used to arrange the stories by priority and identify an initial product release slice.
Agile Requirements Decomposition
- 1. Agile Requirements DecompositionEpic to User Story
- 2. What Are We Doing Tonight?Decomposing a vision into storiesVision -> Epics/Features -> StoriesThe use of story mapping to prioritize and plan a releaseWork through an example togetherHave fun
- 3. Do you use a Vision today?Do you find it valuable?How do you use it?
- 4. VisionDescribes the problem being solved for a releaseDescribe a product solutionProvides a list of features delivered in the releaseCreates shared understanding of purpose
- 7. EpicsLarge initiatives delivering new products, solutions, or services to customersComprised of a large collection of features which may span releasesRepresents a theme and are “fuzzy” requirements – at this point
- 8. FeaturesCapabilities that the product owner is interested inAre delivered within releasesProvides value to usersRealized by some number of user stories
- 9. Features: ShipFlixUsers can cancel their accountTen DVDs can be added to viewing queueUsers can create an account with a valid CCTwo DVDs can be out at any one time# DVDs out can be increased with higher feeStreaming will be supported in IE and Firefox….Movies can be streamed to Windows computers
- 10. What is a story?Once upon a time there was a misunderstood wolf that…
- 11. User StoryRepresents a user’s needPlanning itemCauses a conversation to occur
- 12. User StoriesA user story describes functionality that will be of value to a userRepresents smallest increment of valueContained within a sprint or less
- 13. The 3 C’s of a User StoryWritten on note cards
- 14. Can be annotated with estimates, value, notes, etc.CardDetails of the story come out through conversations with the customerConversationAcceptance tests are defined to confirm the story is completeConfirm
- 15. Story written as:Starts with a titleDescription: As a <role>, I want to <goal>, so that <benefit>Acceptance criteria to define when we’re done
- 16. INVEST Model for StoriesThere should be no dependencies between storiesIndependentDescribes functionality to be negotiated between the customer and development NegotiableValuable to the user or purchaserValuableHave enough detail to estimate without being too detailedEstimatableThey should be small, one sprint or lessSmallWorded in a way that they can be testedTestable
- 17. Stories: ShipFlixAs a user, I want to keep 2 DVDs at any time, so I have viewing choices at homeAs a user, I want pre-paid envelopes for returning DVDs, so I don’t have extra costs.As a shipping clerk, I want to see how many disks are out, so I don’t send too many to a customer.As a warehouse receiver, I want to scan returned disks, so I can quickly credit the customer’s account
- 18. Benefits of Story MappingProvides visibility of the workflow across the systemPoints out relationships between storiesHelps to spotlight missing storiesProvides a prioritization mechanismRelease planning is improved by focusing on valuable slices
- 19. Story MappingUsage SequenceFeature 3Feature 1Feature 4Feature 2Arrange features or activities in the order they are done.
- 20. Story MappingUsage SequenceFeature 3Feature 1Feature 4Feature 2User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryIdentify stories that support features or activitiesUser Story
- 21. Prioritize storiesUsage SequenceMore importantFeature 3Feature 1Feature 4Feature 2User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryLess ImportantUser StoryArrange stories so most necessary are at the topUser Story
- 22. Create horizontal sliceUsage SequenceMore importantFeature 3Feature 1Feature 4Feature 2User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryLess ImportantUser StoryPick necessary stories that are required for a first releaseUser Story
- 23. A Skeleton ReleaseUsage SequenceMore importantFeature 3Feature 1Feature 4Feature 2User StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryUser StoryLess ImportantUser StoryPrioritization considers business workflow and value of stories within the context of the whole systemUser Story
- 24. Example Problem
- 27. FeaturesRequest money from another userSend money to another userConfigure funding accountSign up for a P2P accountAdminister P2P systemManage money transfer disputes
- 28. Exercise – FeaturesGoal: Based on the problem statement and product position, define a set of featuresBreak into teamsChoose someone in your team to present your featuresYou have 10 minutes to define features
- 29. Review FeaturesEach team will describe the featuresPlace your “features” on the wallOther teams should listen for duplicates and remove them from their set of featuresOrder features horizontally by usage
- 30. Exercise - StoriesEach team will be given one or two featuresCreate a set of stories for those featuresFor each story think about:The kind of user who uses itHow often it is used (often, sometimes, rarely)How valuable is it (high, medium, low)You have 15 minutes for this exercise
- 31. Features arranged by orderOrder of activitiesSend money to another userSign up for a P2P accountRequest money from another userConfigure funding account
- 32. Identify stories by featureOrder of activitiesMore importantSend money to another userSign up for a P2P accountRequest money from another userConfigure funding accountSign into P2PSign into P2PSign into P2PRegister for P2PSign into P2PConfigure bank accountSend money to P2P userSend money request to P2P userLess ImportantConfirm bank accountConfigure credit card account
- 33. Create horizontal sliceOrder of activitiesMore importantSend money to another userSign up for a P2P accountRequest money from another userConfigure funding accountSign into P2PSign into P2PSign into P2PRegister for P2PSign into P2PConfigure bank accountSend money to P2P userSend money request to P2P userLess ImportantConfirm bank accountIdentifies a first releaseConfigure credit card account
- 34. For Each Release:Give it a name or statement that describes the purposeDescribe the benefits and goals for the businessDescribe the benefits or value the users getRelease 1: Two DVDs out to customersBusiness Value: Begin creating a user base to offer more profitable capabilitiesUser Value: Ability to have two DVDs out for viewing at home without the hassle of storefront rentals.
- 35. Exercise – Story MappingGoal: Create a slice of the system for an initial releaseArrange stories under each featureOrder stories vertically by importanceIdentify missing stories and fill inDetermine what stories must exist in an initial release – creating a slice
- 36. Story Mapping Wrap UpSets an overall context for the backlogTargets business and user goals for deliveryPrioritization capability for release roadmaps*Release N: the necessities (skeleton)Release N+1: more capabilities and flexibilityRelease N+x: comfort, performance, luxury* As described by Jeff Patton
- 37. Rick AustinEmail: [email protected]: rickaustinBlog: http://blog.capabilitydevelopment.net