
User stories (also called requirements cards) can play a useful role throughout the project lifecycle. They can help with the separate stages of planning, development, testing, and implementation. Ideally, user stories will be documented as early as possible in the project, because they help identify the scope and sequence of the project work. The user stories are then reviewed throughout the requirements process, with an eye out for changes to the feature or the business value that might impact prioritization, sequencing, and testing.
Log in or Subscribe now to read the full answer...
©Copyright 2000-2012 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy