Search:

ProjectConnections Print View


Got a Question?
Drop us an email, or call us toll free:
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.


Learn more about ProjectConnections and who writes our content. Want to learn more? Take a site tour and compare our membership levels.


Can user stories be used in the testing process?

How can we leverage some of the early requirements work to develop our testing program? Can user stories be used in the testing process?
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...

This resource requires a Premium Subscription
Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the full answer! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.
15-day free trial period for new Premium subscribers! Learn more
Username:

Password:












©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