Thursday, July 24, 2014    
   You are here : PM Topics  >  Scope Mgmt
Register   Login   
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. 

 

A solid WBS is the key tool for the entire project plan - and even turn the project execution, a WBS at the right level of detail can help you negotiate scope trade-offs. It's the one thing that no good project should be without.

 
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.

 

This is a link to a traceability document Excel template.

 
Types of requirements-gathering facilitated workshops

JAD: Joint Application Development (or Design) sessions – used by the SW 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.

 
Tips for creating a good WBS

Need some pointers on creating a good WBS for your project or for a course assignment? Here's a short but helpful tipsheet. (Read now.)

 

 

"Running a project without a WBS is like going to a strange land without a roadmap."

   - J. Phillips

 
Copyright 2013 by Successful Projects