Summary

In this chapter, we've introduced the Vision document, a seminal artifact in an effective requirements process. This document provides an overview of both stakeholder needs and product features, as well as a vision of both the problem space and the solution space. It gives the team a "stake in the ground" around which all can rally or discuss and debate, as the case may dictate . But, in all cases, your team should produce a Vision document and you may be confident that the project will benefit from having done so. Indeed, no effective software team should ever "leave home without one."