Four horsemen of user stories

In this interactive workshop, the audience experiences a user story from its creation using the storymatic game, to clarification with conversations, learning about the story from examples that then become automated tests and estimation exercises that lead to splitting into smaller stories using the INVEST model

 
 

Outline/Structure of the Workshop

This is an interactive workshop that requires round tables.
The break up of the session is as follows
10 mins - Introduction and setup
15 mins - Tell stories using Storymatic - https://www.amazon.com/Storymatic-Classic-Stories-Booklet-Activities/dp/B004PICKDS/ref=sr_1_1?ie=UTF8&qid=1527305085&sr=8-1
10 mins - Audience share stories
15 mins - Tell stories for your product and have a conversation
20 mins - estimation
20 mins - Split them just right while continuing to estimate

20 mins - Acceptance test driven development using acceptance criteria and converting into test code using cucumber and gherkin
10 mins - conclusion

This is an interactive workshop using the principles of "Training from the back of the room" for the audience to learn by doing


Learning Outcome

- Explain how to tell stories and never write them
- Practice how examples help clarification as well as ATDD (acceptance test driven development)
- Estimate stories
- Split stories

Target Audience

Scrummasters, Product Owners, Development teams

Prerequisites for Attendees

None

schedule Submitted 3 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Oana Juncu
    By Oana Juncu  ~  2 months ago
    reply Reply

    Hi Anil,

    Thank you for your submission,

    Can you give some more detail why the  four horseman of User Stories  you have proposed will enhance the Agile Mindset?

    Kind regards,

    Oana

    • Anil Jaising
      By Anil Jaising  ~  2 months ago
      reply Reply

      Hi Oana,

       

      The workshop features 

      1. Simulation of a backlog refinement where the participants work in groups to create acceptance criteria in gherkin language so that they inculcate test first mentality

      2. Stories are refined just in time to demonstrate "Simplicity" principle

      3. Stories are created collaboratively to demonstrate "individuals and interactions" & "customer collaboration" values

      4. The estimation scenario clearly demonstrates "Responding to change" value

       

      kind regards

      Anil