User Stories vs Use Cases

If you are on an agile team, do you write user stories, use cases, or both? My take is that until you know how to think in use cases to analyze the functional requirements on-the-fly, you need to write them to be sure you’ve got a clear and complete view of what the software needs to do.

What's more, use cases are an incredibly powerful analytical tool to avoid missing functional or software requirements.

Then, if you are on an agile software development team, you might break apart your use case into multiple user stories to help manage the requirements through the software development process.

This is why we continue to teach use cases as a core, fundamental skill at Bridging the Gap as part of our online courses - because knowing how to write use cases makes you a better business analyst.

What’s your take? Leave a comment below.

DOWNLOAD THE USE CASE TEMPLATE (it's free):
http://bridging-the-gap.com/uctemplate

WATCH THESE VIDEOS NEXT:

How to Write a Use Case
How to Write a Use Case

Requirements Elicitation - What Questions to Ask:
Requirements Elicitation – What Quest...

View the Full-Text Transcript Here:
http://www.bridging-the-gap.com/user-...