At a glance

Duration:
1 day
Contact us for any enquiries
including in-house delivery.
Business Analysis

Agile User Stories

To successfully deliver a project, the team needs to gather information from a wide number of people and communicate this information sensibly to developers, testers, trainers, business owners and other stakeholders.  Over time, many practices have been developed to bring order and predictability to software projects by detailing requirements in an increasingly more ordered and focussed manner. 

Yet chaos still seems to win over order - with last minute changes, misunderstood requirements and foreseeable gaps that somehow slipped through all the signoff gateways between the initial dream and the realisation of the project. 

The story approach to requirements turns the traditional way of working on its head, gathering just enough information to make the necessary decisions at the right point in time. 

In this way, low priority requirements - those that will probably not see the light of day - do not consume too much of the team's (and customers') valuable time.  The story approach also allows relatively painless changes to the scope as the project progresses.

The use of stories requires a defined and disciplined series of steps and practices to ensure the project team can estimate and plan releases, deliver what the customer really needs and be able to test the result sufficiently. 

This course provides an end to end approach to developing and using stories effectively in a project setting.

This course been been designed alongside Practices of Agile Teams and Agile Estimation and Release Planning to be delivered in-house, mixing and matching content from the three courses to provide an individually tailored training solution. If you are interested in running a tailored version of these three Agile courses in-house then please contact us
 

Intended For

Anyone involved in a project which uses stories to identify business and customer needs

Prerequisites

Learning Outcomes

By the end of the course participants will be able to:

  • Explain what user stories are and when they can add value on a project
  • Write, challenge and improve user stories
  • Elaborate stories to the right level of detail to add the most value to the project
  • Test stories and use them in development activities.

Content

  • What's a story?
  • Who should be involved in story discovery?
  • How big is a story?
  • Identifying stories
  • Isn't this just requirements or use cases by another name?
  • Characteristics & content of stories
  • What does “Done” mean?
  • Quality stories
  • Stories & Epics
  • Acceptance tests and verifying stories
  • The story “smells” that predict trouble
  • Elaborating stories to be useful without wasting time or effort

Method Used

Lecturing is kept to the minimum necessary, most of the learning is achieved through applying the practices and techniques in group exercises and a case study.

Software Education Associates Limited
Freecall: 0800 268 773
Software Education Australia Pty Ltd
Freecall: 1800 145 152
Proud to support World Vision