Use Cases - Drowning in Stories

Drowning in a sea of Stories with no way of seeing the big picture?

Got hundreds of disconnected User Stories but you really only have a dozen or so key system uses? Then you need a use case model fast…​

Stories arrive in the backlog all too easily. However they can soon become overwhelming when you have hundreds of seemingly disparate threads and you find it impossible to see the big picture. You are convinced there are some stories missing, but to find them is like finding a needle in a haystack, sound familiar? If so, you need to unleash the power of Use Cases…

Do you need a better agile requirements solution?

  • When you just have hundreds of text-only statements, getting a simple summary of what the system should do is incredibly hard. ‘It is easy to drown in the detail’.
  • With classic declarative / functional requirements approaches, scope creep is a massive danger. If you can’t visualize the system boundary then you simply don’t know where it is.
  • How do you know if you have missing requirements? Scanning a sea of words for what is not there is very difficult.
Use Cases Improve Requirements image

Ok, so you probably agree that a requirements technique:

  • that handles detail whilst providing a simple big-picture view​
  • and that supports iterative and agile working practices

…is critical for the success of your product development?

Use Case Certification Badge image

Then Use Cases are for you because…​

  • Use cases effortlessly communicate the value of the system or system increment under construction. This provides a great way to bridge the gap between the key stakeholders and the development team.​
  • The logical and simple structure within a use case provides an intuitive way to get to the detail you need. Our guidance and patterns give you the tools you need to capture and manage the things that other techniques struggle with.​
  • Use cases can be logically ‘sliced down’ to provide the perfect granular unit of requirements to support agile working. Use case slices, representing one or a few stories, can be easily identified to form a backlog of items that teams can get ‘done’ iteratively.​
  • They ‘jump-start’ your design and architecture thinking. The detailing of use cases naturally uncovers business terms and rules that can be used to drive design, coding and testing activities.
Use Case Benefits image

Contact Us