Leadership > Stories/Acceptance Criteria

Presented By: Mike Stout & Jay Packlick

Leadership Track: 9:45am-10:45am

Presentation Materials: Download

Successful projects depend on deeply understanding users needs. Too often though, during the transition from traditional methods to Agile, teams move too far to the left interpreting “working software over comprehensive documentation” as an excuse to abandon capturing and communicating requirements.  User Stories can be an extremely effective technique to communicate requirements, but they require the disciplined application of new skills.  The good news is those skills can be acquired with a little guidance.

Join Mike and Jay as they share their experience from the trenches coaching teams to achieve proficiency in this technique.  They’ll be covering the fundamentals such as

•    Why you should care about User Stories

•    How to write and use them effectively without resorting to ‘comprehensive documentation’

•    Simple techniques you can apply so that teams understand what ‘done’ means

•    Common pitfalls and how to avoid them

•    What to do when your team’s situation doesn’t mirror the agile ideal

In true agile form, you’ll have an opportunity to submit your own ‘requirements’ for the session so that we can address the most pressing questions and concerns about User Stories.