Agile requirements

One-day workshop. Structuring requirements in agile projects with user stories and smart use cases

One of the important and often underestimated aspects of agile and Scrum projects is how to deal with requirements. Where does the backlog actually come from? Many projects rely solely on user stories. However, with more complex agile projects in large organizations, a more structured approach might lead to better results.

2014-03-26-13.56.42_thumb5

During this one day workshop Sander Hoogendoorn, global agile thought leader at Capgemini and international speaker and author, will illustrate different models of working with requirements in agile projects. Next to user stories he will also elaborate on smart use cases, presenting a more structured approach to use cases.

Topics

Participants will learn different aspects of working with agile requirements and the speaker will address the following topics:

  • How are agile, Scrum and Kanban different from traditional linear approaches?
  • What is the role of the backlog and requirements in agile projects?
  • How and when should requirements be identified in agile projects?
  • Different levels of requirements
  • Epics, features and user stories
  • Structuring agile requirements with smart use cases
  • Estimating agile requirements

During the day participants will join in a number of fun and helpful exercises that include comparing waterfall, agile and Kanban; identifying different levels of requirements; scoping features and user stories; modeling smart use cases and relative versus absolute estimation.