AgileManifesto Follow Some of These Principles When Creating User Stories: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. The best architectures, requirements, and designs emerge from self-organizing teams.
What is a User Story? Wikipedia defines it as “a software system requirement formulated as one or more sentences in the everyday or business language of the user”.
Layman's Terms I like to say “it is a quicker way of detailing requirements without having to create large documents and minimizing the time to administer the documents through the entire life-cycle of the project”.
User Story Layout Follow these 3 steps for easy creation of your user stories. Step One is to create the headline. Use patterns like: As a (role), I will be able to (feature) so that I can (reason) Example: “As a manager, I will be able to access my account online so that I can modify it 24/7”.
User Story Layout Follow these 3 steps for easy creation of your user stories. Step Two is to use index cards. Index cards just by design (3X5) will force you to keep the story short and sweet. No big soliloquy here, just the facts needed to convey the story to the development team and business in a clear and concise manner.
User Story Layout Follow these 3 steps for easy creation of your user stories. Step Three is to create the acceptance tests for this story. Each test has instructions for setting up and then running the test. Example: ”Create account, add funds, subtract some of the funds then check the balance for expected results”.
Summary User Stories must contain just enough information, remember short and sweet. User Stories should be written in the business user’s language . Indicate the priority that are prioritized by your project stakeholders. Use a unique identifier for traceability between the user story and acceptance tests.