Integrate User Stories + Use Cases

  Agile   Requirements Management   ProjectsAtWork  

Many project teams shy away from incorporating use cases into their Agile approaches because they resemble the non-Agile techniques of elicitation and analysis. But there are golden opportunities to leverage the power of use cases with user stories when developing Agile requirements. Let’s look at when and how.

As the Agile movement continues to gain momentum and managing projects using Agile methods becomes more and more prolific, project professionals must become more savvy in their use of Agile methods. While the techniques and processes associated with Agile are different than those associated with Waterfall, many innovative project teams are incorporating non-Agile techniques into the Agile environment, with great success.

There is a common misconception that Agile replaces the need for use cases with user stories. Questions on this topic have been posted on social network sites such as Skillsharks, blogs, Twitter, Facebook, etc. The question shouldn’t be “Do user stories replace use cases?” Rather, the question should be framed: “How do we leverage the power of use cases with user stories when developing effective Agile requirements?”

Many shy away from use cases within an Agile approach because they resemble the ways of elicitation and analysis from the Waterfall approach. However, regardless of how one approaches requirements …

Please log in or sign up below to read the rest of the article.