One. Introduction
Requirements
It is a good idea to decide what you want to build before you build it. This is true for any human endeavor in which the person using an item is different from the person building it. This principle is especially true in software development, because software requires such a high degree of precision and coordination among team members in order to achieve acceptable levels of quality. If we did not seek agreement up front about what to build, we would likely end up with many more unsatisfactory systems, many more unhappy customers, and more software systems that fail because of assumptions that are incompatible with users’ needs.
That is the primary reason that we write requirements: to document a common understanding ...
Get Just Enough Requirements Management: Where Software Development Meets Marketing now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
