Chapter 17. Defining Project Scope
Every software team talks about project scope, and team members often complain about unending scope creep. Unfortunately, the software industry lacks uniform definitions of these terms. Even worse, the requirements engineering literature is short on clear guidance regarding how to represent scope. In this chapter, I present some definitions, describe three techniques for defining project scope (the context diagram, the use case diagram, and feature levels), and offer some tips for managing scope creep.
Vision and Scope
The vision and scope document is a key software project deliverable (Wiegers 2003a). You can find ...
Get More About Software Requirements: Thorny Issues and Practical Advice 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.
