GSA/christopher

---
title: Use Case Examples
category: Agile
audiences:
  - Developers
  - Designers
  - Project Managers
---

[Use Cases]({{ site.baseurl }}/guides/glossary/#use-cases) can be effective when engaging business users / user groups to perform acceptance testing for a project’s [user stories]({{ site.baseurl }}/guides/glossary/#user-stories). While the Product Owner must provide final sign-off on the  work the Scrum Team completes within a sprint, they can leverage business users for acceptance testing by providing use cases to help expose defects and garner feedback.

In acceptance testing, use cases provide a user (i.e. tester) direction without leading. Use Cases provide a sequence of steps in business terms, that describe the “happy path” for a specific interaction. Unlike system test cases, the use case interaction is defined in terms of the user, describing the user actions and experience versus the system inputs and outputs. The user compares their experience to the defined Success Criteria, documenting success or failure, along with any results. Results may expose bugs, defects, misspellings, updates to the user interface or process flow, or even new user stories identified.

[Download this Sample Use Case Document]({{site.baseurl}}/assets/downloads/DRAFTUseCaseTemplate.xlsx)

### Good Reads
These are good references for  incorporating Use Cases into user acceptance testing:
* [Use Cases Are User Stories With Acceptance Tests](http://wiki.c2.com/?UseCasesAreUserStoriesWithAcceptanceTests)
* [What is Use case testing in software testing?](http://istqbexamcertification.com/what-is-use-case-testing-in-software-testing/)
* [Writing Test Cases from User Stories & Acceptance Criteria](https://blog.testlodge.com/writing-test-cases-from-user-stories-acceptance-criteria/)