# Use Case 2.0
Use Case 2.0 is a technique for using use cases in an agile development. Use cases are very useful for identifying requirements. Companies with use cases plan them in an agile manner. The concept can be used in classic waterfall projects and also in agile development.
Business and customer value
Unlike user stories, which are usually managed in a product backlog, use case stories offer a better overview of the system through the connection to use cases and use case diagrams. Dependencies between requirements are made transparent and are understood in this way. In addition, use case stories help to get an overview of already completed system parts during implementation.
The following terms are important for this method, especially: Flow: Describing a full or partial path through a narrative use case. There is always one basic flow and there can be alternative flows. Basic flow: The description of the normal, straight-line walk through the use case. It is therefore the most important part of the narrative use case and is used most frequently by the actors. Alternative flow: Description of the variant or the optional behavior as part of a narrative use case. Story: By using a story, the user gets the option to use a valuable system. In Use Case 2.0, a story is described by the narrative use case, one or several flows, requirements and one or several test cases. A story is in consequence not identical to a user story from Scrum. Use case model: A use case model consists mainly of a number of actors and use cases, as well as diagrams that visualize their relationships. Use case slice: A use case slice unites one or more stories that are selected from a use case and represent a unique value for users. Rules for defining use case slices: Use case slices have to be cut so small that they can be implemented in one sprint. The first use case story is called basic flow. It will be implemented first. Each slice needs to have at least one test case. If two use case slices contain the same use case stories, they must contain different test cases.
How can use cases be generated? There are two ways: Top-down, i.e. determine individual steps, processes and alternatives based on the use case. And bottom-up, i.e. by using brainstorming, brainwriting or brain dumping and to combine them in use cases.
Agile coach/agile master
The entire team
Flipchart, pens, sticky notes