Fit tables help solve three major problems in software development: communication, balance, and agility.
Fit tables provide a way for people who want a system to communicate that need in a concrete way. As we've seen in Part II, it's usually best to let Fit tables evolve through using concrete examples of business rules. As the examples get more comprehensive or more complex, the language of the tests needs to evolve to find the best means of expression.
Good Fit tests can mean that we spend less time unbalanced because of bugs that need to be fixed. Fit tests do this by reducing the number or severity of problems, catching them early, and making sure that they don't return. Better quality leads to improved customer satisfaction and lower costs in rework owing to errors and misunderstandings.
Fit tables help keep the software in good shape so that changes can be made quickly and effectively to support business change.