Be the first to like this
The practice of agile software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust within the organization. Jared Richardson shows how good acceptance tests can reduce misunderstanding of requirements. A testable requirement provides a single source that serves as the analysis document, acceptance criteria, regression test suite, and progress-tracker for any given feature. Jared explores the creation, evaluation, and use of testable requirements by the business and developers. Learn how to transform requirements into stories—small units of work—that have business value, small implementation effort, and easy to understand acceptance tests. This tutorial features an interactive exercise that starts with a high level feature, decomposes it into stories, applies acceptance tests to those stories, and estimates the stories for business value and implementation effort. The exercise demonstrates how big requirement stories can be decomposed into business-facing stories, rather than technical tasks that are not understood by the business.