I am writing a system where both the system owner and myself are developers, and we are currently the only source of 'requests' or requirements for the system, which I would like to capture in user stories tied to features{1}. My urgent priority now is to get a managaeble backlog captured. How should I go about capturing the level of technical spec I am used to to working with in users stories, which aren't supposed to be too technical.
{1} I am evaluating agile project management service TargetProcess, and each user story must be tied to a parent feature. The system seems a good fit, so this small constraint is something I would rather work with than work around.
Best Answer
The typical story template is very easy to visualize:
The interesting thing is that the importance of the components are reversed.
WHY is more more important than WHAT and that is more important than ROLE
Example using this Question
Anything more is over complicating the intent and the implementation of User Stories.
Additional Tools ( Integration is best )
Tools can be used to capture additional detail information about the stories that is captured when discussing them to assign points/estimation, but that detail should not be part of the story itself. Something as simple as a Wiki with 1 Page per story to put details/transcripts of discussions on is a good enough solution. Excel spreadsheet is a terrible solution.