Use-Case 2.0: Scaling Up, Scaling Out, Scaling In for Agile Projects by Ivar Jacobson

Use-cases continue to be a popular way of working for both business and system requirements.  Googling "use-case" yields a search volume six times greater than Googling "user story", but software development should not be driven by popularity. Instead we should use the most practical way of working, one that allows us to continuously improve.  Over the years we have learnt how to be truly successful with use cases, and of course we have learnt something from other techniques, such as user stories and aspect-orientation, which have inspired us to make use-cases even better while maintaining their core values.

Distinctive features of the new use cases are:

  • As agile and light as you want it to be
  • Scaling up, scaling out and scaling in - to meet your needs
  • It’s not just about requirements - it's for the whole lifecycle
  • It's also for non-functional requirements
  • It’s not just for software development - it's for business as well

The presenation at IIBA was received very well by the around 400 participants.  Afterwards IJI staff were busy explaining the new use-cases and how to find slices of use cases to populate the backlog to support Scrum or Kanban like projects. Participants signed up for the new eBook on use-case 2.0, to be released shortly.

You can register to receive the powerpoint presentation here.

Follow the conversation with me on Twitter.

  1. Emilie Vodinh-Morris | January 30, 2012 at 11:15 am Reply


    Hello Ivar, I attended your presentation at the IIBA conference in London and I have read the eBook with great interest. I have a question for you: How would you document the use case slices? The diagrams in the eBook are good pictorial representations (figures 3 and 4), but I’m not sure I can draw something similar for a whole project. What do you recommend? Many thanks.