Join us to review and create a new “picture” that depicts the fundamental elements of the perfect user story.  Using a series of small group discussions and collaborative activities, participants will review user story writing essentials including: story hierarchy; the 3-C’s of user stories; canonical story form; proper language to use within user stories; splitting stories using a thin vertical slice; capturing metrics for complexity and business value; and adding acceptance criteria to user stories.  During the workshop, participants will be challenged to sketch the outcome of their group collaboration to create their own visual depiction of the perfect user story that they will be able to take with them after the workshop to help them recall what they learn.  Workshop participants will leave having reviewed the essential elements to write effective user stories for agile software development, while also experiencing the power of sketch and visual thinking as tools that can enable improved communication and understanding of complex information.  All will be engaged and have a bit of fun creating their own unique sketch of the perfect user story while also admiring the visual creations of fellow workshop participants.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Presentation Background

This submission is a BRAND NEW workshop that was inspired Lynne Cazaly’s presentation of “Girl with the Chisel Tip Marker” at the Agile2014 conference in Orlando, FL.  In the brief period between Lynn’s presentation at Agile2014 and the deadline for AgileDC submissions, this workshop has been presented and well received in agile training workshops held during early August 2014.  The workshop consists of a series of small group discussions to review the elements of a user story.  As groups discuss each user story element, participants add the element to their sketch to reinforce why each element of the story is needed and capture the value/information provided by each element of a user story.  At the beginning of the workshop, we’ll touch briefly on the benefits of sketch and visual thinking, discuss the benefits provided by posting “visual information radiators” within a team area, and conduct a brief drawing “warm-up” to prepare participants to sketch the details of their user story discussions.  At the end of the workshop, participants share their sketches with their fellow group members and other workshop participants to add further reinforcement to the value that is provided by each element of a concise and fully-defined user story.

 

Workshop Timing (60 minutes) - elapsed time is shown in parentheses

  • 5 minutes (0:00 - 5:00) - Welcome, Background & value of sketching to convey complex information
  • 5 minutes (5:00 - 10:00) - Drawing Warm-Up (lines, boxes, circles, triangles)
  • 10 minutes (10:00 - 20:00) - Discuss and Sketch - Story Hierarchy, Story Form, Story Language/Lexicon
  • 10 minutes (20:00 - 30:00) - Discuss and Sketch - Story Sizing and Slicing
  • 10 minutes (30:00 - 40:00) - Discuss and Sketch - Metrics (Business Value & Complexity)
  • 5 minutes (40:00 - 45:00) - Discuss and Sketch - Acceptance Criteria
  • 10 minutes (45:00 - 55:00) - Group Sketch Sharing
  • 5 minutes (55:00 - 60:00) - Final Q&A and Thanks for attending

 

Presentation Materials:

As this is a sketch based workshop, presentation materials will be sketched live during the workshop - items sketched on tablet will be projected to the audience (A/V needs noted below)

Learning Outcome

  • Participants will review the essentials that go into effective user story writing including: story hierarchy, 3-Cs, INVEST, story sizing & thin vertical slicing, appropriate story language/lexicon, story syntax, business value & complexity metrics, and acceptance criteria.
  • Participants will challenge their visual thinking and sketch skills by creating their own sketch of the essential elements of user stories (sketch paper will be provided for participants).
  • Participants will engage in collaborative discussions / activities within small groups to review / reinforce the essential elements of user stories.

Target Audience

Any agile practitioner that writes and/or works with user stories, as well as those interested in sketch and visual thinking

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • John Sextro
    John Sextro
    schedule 2 years ago
    Sold Out!
    60 mins
    Demonstration
    Intermediate

    Spend Less Time on Your Estimates

    Most teams would rather work to deliver value to customers than spend time estimating stories.  In order to spend less time estimating and more time delivering value to the customer, many teams have adopted “Affinity Estimation”.  Using “Affinity Estimation” many teams have significantly reduced the time required to estimate and I have personally been involved in sessions that used to take 60 minutes and are now taking 15 minutes.  By using “Affinity Estimation” to compare new stories to real stories that were recently completed, teams are able to quickly and confidently provide an estimate without lengthy discussions and worries of the unknown. 

    What to Expect

    The session will begin with a brief presentation highlighting everyday problems that coaches deal with when estimating stories.  Then, using volunteers from the audience, we will work through a series of exercises/games demonstrating the value of "Affinity Estimation" while teaching the audience and the volunteers how to coach these exercises for their own teams.

    All Teams are Not Created Equally

    This session will provide you with exercises that you can use for existing teams, as well as, new teams. 

  • Jason Tice
    Jason Tice
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Agile and Lean principles call for teams to delay decisions and activities until the “last responsible moment” so as to minimize rework and waste.  While this sounds good in concept, sometimes teams fall victim to waiting until it is “too late” to make a decision or get started on a needed activity resulting in missed opportunities and/or down-to-the-wire heroic efforts to meet a deadline.  This workshop entails a competitive LEGO simulation where participants will divide into small teams, each team will be given the same simple LEGO build challenge, and then each team will be able to conduct their own experiments as to when the “last responsible moment” really is.  Following the LEGO build challenge, participants will engage in a debrief to discuss the outcome of the challenge, identify factors that helped to successfully identify the last responsible moment, establish linkages between the LEGO simulation and agile software development activities, and of course congratulate the winners of the challenge.  During the debrief, participants will complete a debrief worksheet to reinforce key learnings and takeaways from the simulation that they will be able to take with them from the session.  Best of all, this is a LEGO session, so you will get to play with LEGO and fun will be had by all!

  • Jason Tice
    Jason Tice
    schedule 2 years ago
    Sold Out!
    30 mins
    Demonstration
    Intermediate

    I have the privilege of coaching a few teams building a product and I have the ability to show their real team metrics LIVE - I might add the team has also given me permission to show their metrics to others, as we know that some metrics that a team keeps may only be intended for use by the team (we’ll highlight what these metrics are in the session).  Hence in this short demonstration session, we will pull up the team’s metrics live and see what’s going on - the "good" stuff and the "bad" stuff, as the reason to use metrics to guide team improvements is they tell us the TRUTH about what's really going on.  We will look over metrics such as cumulative flow across the full value stream, story cycle time, story lead time, block time and others.  We will go over how to review the data from multiple metrics and look for trends resulting from changes to the team and/or the team’s process - such analysis can stimulate lively discussion in team retrospectives so as to assess the impacts of changes the team makes to their process and also to identify adverse trends and/or bottlenecks to target with future changes and improvements.  We will also review how the team’s data is communicated to other teams via a monthly Operations Review meeting focused on program-level / multi-team improvements where teams exchange information on what they are working to improve, why they are seeking to improve, and what indicators / metrics are being used to assess the impact of changes.  Attendees will leave having observed a demonstration how to use quantitative data to achieve improvements using the scientific method.