Project Scope Management

Clearly defining the scope of a project can be a challenge. The scope definition establishes the value that the project will deliver. Some of the tools include the scope statement, the work breakdown structure, and your change management system.

Collecting Requirements

Requirements include the quantified and documented needs, wants, and expectations of the sponsor, customer, and other stakeholders.

Typically written requirements are recorded, linked, and traced through a “Requirements Traceability document”. Traditionally user requirements begin with a U and system requirements begin with an S. There are often many S requirements that trace to one U requirement.

Types of requirements-gathering facilitated workshops:

JAD: Joint Application Development (or Design) sessions – used by the Software industry. Bring users and the development team together to help plan the development process.

QFD. Quality Function Deployment – helps determine critical characteristics for new product development. This starts by collecting customer needs, also known as the Voice of Customer (VOC), which are then prioritized.

“Running a project without a WBS is like going to a strange land without a roadmap.”     – J. Phillips