I’d like to add the instructions note to the HTML output, maybe as a command line option. It’s rather useful as a reminder for clients who aren’t familiar with the process.
Each user story describes a single requirement as something you would like to do in a given role, preferably with a clear motivation or reason. You can add notes for questions that can be answered later, for issues that need to be discussed, and for additional explanation. User stories are organized in themes which group related requirements.
Writing the initial user stories is the shared responsibility of everyone involved in the project.
Once everyone agrees that the user story list is sufficiently complete, the developer will estimate the expected amount of work needed to implement each story. At the same time, the client will give each story a priority ranging from ‘must have’, ‘should have’, ‘could have’ to ‘won’t have now’ that shows the value of the story with regard to the goal of the project.
Based on the estimates and priorities, the implementation of the stories will be planned in one- or two-week iterations.
Each story also has a status which is initially set to ‘todo’. Once the story has been implemented it will be set to ‘done’. During development, everything that’s not ‘done’ can still be changed; you can add new stories, move a stories to a different iteration, or set the status of a story to ‘dropped’ if it’s no longer needed.
Below the user story list you’ll find a list of descriptions for all roles and themes and a list of definitions of terms used in the project.
In theory you can do this:
saga template my_templates
saga --template my_templates requirements.txt
But I guess in most cases this might be too much work?
Well, it’s a possibility. I do think it might be nice to just have it in there by default. Do you have any objections against that? It’s at the bottom of the HTML version, so it’s easy to ignore if you already know what you’re doing.