In a previous post, I contended that requirements are still an important part of most enterprise environments, even those that might be using Agile lifecycle methodologies. However, I didn't specify exactly how those requirements should be captured -- or what even constitutes a requirement. This is an important question that spans both Agile and Waterfall methodologies. Many organizations feel that user stories are sufficient to build both code and project structures around. Is it out of the question to consider that use cases might be used within an Agile approach? Before answering that, let's take a look at user stories, use cases and requirements in context again:
