"I was asked the question today, again, "why user stories - why not use
cases in your project?" Please keep in mind that a couple of years ago
I was writing use cases like nobody's business, and became one of the
key change agents in our organization to adopt use cases.
Since moving to agile methodologies (Scrum/XP primarily) and adopting
user stories, I have found that user stories are essential, and use
cases help work out the bugs of the user stories."
And I respond:
Yes. The question about why one and not the other is like asking "Why
talk about an object and not the interaction of multiple objects?" Of
course you want to do both.
The interesting questions about *how* you treat the one and the other.
Are you being effective with them? Are you being wasteful?
So I need to say that by "Use Case" I am not referring to anyone's
specific definition of what they are and how they are represented. I am
referring in general to discussions about "expressions of business value
larger than a story." Treat these as "use cases", "workflows", "business
processes", "scenarios". They are mean somewhat different things but in
general represent (to me) expressions of business value larger than a
story in the same way there are interactions in a solution that are
larger than an object.