User Stories to Requirements

Agile methodologies allow development teams to better handle multiple projects and deliverables. One issue I have with User Stories is the inability to specify hard requirements. Use cases, functional requirements, and cognitive walkthroughs.

http://en.wikipedia.org/wiki/User_story

As a user, I should be able to edit my content
As a user, I should be presented with the potion to save my content when I close

The Issue is that we have been using Epochs thinking they are User Stories and not breaking them down to smaller, testable stories.

Keeping all this in mind, I have recently started sketching ideas for a system that allows us to maintain our stories and epochs (and allowing stories to evolve into an epoch with it’s own smaller user stories) and apply true requirements to these stories.

Over time, the project may evolve with sprint breakdown and planning tools.