Writing Excellent Executable Requirements

Many teams build software that does not behave as their customers and users want-and expect. To build the right software the first time, teams need more than written user stories or even detailed specs. Adding "executable requirements" to your specifications toolbox is a way to ensure that the software does what users expect and need day-one. Until now, writing executable requirements mostly has been considered a dark art. Eric Landes shares methods of building executable requirements-automated acceptance tests-that deliver immediate value for your customers. Eric describes ways to create these “excellent” requirements even in difficult situations-collaborating over different time zones, refining vague needs, and product owners speaking with different voices. Demonstrating FitNesse and Specflow (a Cucumber-like BDD tool) as implementation tools, Eric walks through steps for creating test fixtures, test scenarios, and choosing test data. You'll take back new approaches for developers and testers to collaborate, improve productivity, and ultimately, "wow" your customers.