Running the meeting

The meeting format is simple enough – step through the feature specification, read each requirement to see if there are any disagreements, and sign it off. Was it the behavior the product owner wants? Has the developer implemented it (or have they agreed to implement it)? This is a form of static testing – testing without running the code. This lets team members step through design documents, technical specifications, or, in this case, functional specifications to look for errors or issues. This contrasts with dynamic testing, where you run the code to see how it behaves in practice. Only this chapter, Chapter 2, Writing Great Feature Specifications, and parts of Chapter 6, White-Box Functional Testing cover static testing; the remainder of this book focuses on different types of dynamic testing.

With a large specification that you are already familiar with, you may find it tempting to breeze through the requirements quickly. Don’t. Take...