Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Story Workshop


Published on


Published in: Social Media
  • Be the first to comment

  • Be the first to like this

Story Workshop

  1. 1. Story WorkshopOctober 18, 2016
  2. 2. Whyare wehere? If we don't get the user needs right, it doesn't matter how well we execute the rest of the product because the purpose of a software development project is to build a product that provides value to a particular set of customers.
  3. 3. Whyare wehere? We're here to refine the backlog, our list of items that need to be completed in order to keep our customers happy and continue to deliver them a product that they find valuable. This is a good platform to discuss and clarify stories in the product backlog and update our priorities.
  4. 4. Whyare YOUhere? Your expertise Your voice We are all a team collectively responsible for our product
  5. 5. ProductOwner Responsible for our product's vision Responsible for return on investment Has the final say Can't do it all alone, needs the team's help. What are your current priorities?
  6. 6. What'sina ticket? A feature is a set of related requirements that allows the user to satisfy a business objective or need. Features are articulated in the backlog through user stories that tell who, what, and why a feature would be useful. As a [role] I want [something] so that [benefit]. If a story doesn't meet the INVEST criteria, it is probably an epic that needs to be broken down into user stories. We need to estimate the size of each story (how long it will take) and also decide what is more important for our customers that we get done first. Acceptance Criteria can be further added to the story to ensure developers build what the customer wants. Given [some precondition] when [I do some action] then [I expect some result]. I N V E S T ndependent egotiable aluable stimable mall estable