This class is taught by a Certified Scrum Trainer but is not a certification course.

Effective User Stories for Agile Requirements

Projects start with their requirements. How those requirements are documented or expressed has a tremendous influence on the rest of the project. User stories originated in the agile processes but are useful even if you are not planning to use an agile process.

The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. However, user stories are an effective approach on all time-constrained projects. In this course, we will look at how to identify and write good user stories. We’ll see the six attributes all good stories must exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories.

During this hands-on course we will have the opportunity to practice identifying user roles and writing stories on a case study.

You Will Learn

• The six attributes of a good story and how to achieve them
• A useful template for writing user stories
• Practical techniques for gathering user stories
• How much work to do up-front and how much to do just-in-time

Combine This Class With Other Training

This class will be preceded by a Certified ScrumMaster class and followed by a Certified ScrumMaster in the same location. You can attend these classes separately or together.

What’s Provided

Participants will receive printed and bound course materials. Continental breakfast, lunch, snacks and drinks will be served.

Professional Development Units (PDUs)

PMPs: You can receive 8 PDUs for this course. 

• It's a communication problem
• What user stories are
  • Card, conversation, confirmation
  • Some examples
  • Adding detail
  • The product backlog iceberg
  • Augmenting user stories
• Users and user stories
  • Proxy bias
  • User roles
  • User role modeling
  • Personas
  • Extreme characters
• Gathering stories
  • Questionnaires
  • Observation
  • User interviews
  • Story-writing workshops
• INVEST in good stories
  • Independent
  • Negotiable
  • Valuable
  • estimatable
  • Sized Appropriately
  • Testable
  • Additional guidelines
• A tools interlude
• Created case studies
  • Creating and selecting case studies
  • Writing the product backlogs
  • Lessons Learned
• What user stories are not
  • Use cases
  • IEEE 830 Software Requirements Specs
• Why user stories
• Why not user stories

This course is equally suited for programmers, testers, managers, analysts and even customers and product owners who are interested in applying these agile techniques to their projects.