LIVE Fireside Chat with Bob Galen: Putting the "story" back in User Story
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
If you're using User Stories for your agile requirements, you're not alone. It has become the ubiquitous vehicle for communicating customer requirements to agile teams. However, many teams are experiencing problems with it.
You see, we often forget the "conversation" part of the story and, more importantly, the story-telling part. When Kent Beck originated the idea of the User Story, this was his original intent. It was to initiate or inspire a story-level conversation between a stakeholder or customer and the team implementing something to meet their needs. It was face-to-face and interactive. It was intended to inform but also inspire. Join Bob Galen as we practice improving your story narrative.
Bob Galen on LinkedIn: https://www.linkedin.com/in/bobgalen/, and Bob's own website.
In this session Bob refers to the following resources:
- Nordstroms sunglass video agile
- User Story mapping's original blog post by Jeff Patton
- The book User Story Mapping by Jeff patton
- The book Made to stick, Chip & Dan Heath
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.