I have found that often a project leader or project team will confuse the concept of project scope with that of product scope. Product scope is the complete list of features, functions, or characteristics that a product or service is intended to provide. The activities needed to complete the product scope are elements of the project scope. However, the project scope will include many additional activities that are unique to managing the project but are not deliverables within the product. For example, the project scope includes preparation and support for meetings, reviews, supplier management, and preparation of documentation. When a project leader or project team member only considers product scope while planning the project, they will under plan the amount of time and resources needed to complete the project.
Many organizations have customized tools or templates to assist the project team with scope planning. I recommend that you use those if they are available. I have found five scope planning tools or techniques to be helpful, depending upon the uncertainty and complexity of the project. These are the Traceability Matrix, the Scope Statement, a Deliverables Deployment, the Work Breakdown Structure (WBS), and the WBS Dictionary.
The Traceability Matrix is most commonly used on Complex projects. The matrix is a table that traces each requirement through any related sub-project's requirements and through the project life cycle to ensure that it is fully satisfied. It is both a planning tool, showing the project management team's intention with respect to meeting the requirement, and a tracking tool, as it also shows the results of any test or analysis that demonstrates the requirement has been partially or fully met.
The types of requirements included in a traceability matrix typically include:
Business goals or objectives
Business process requirements
Logistical support requirements
Regulatory or agency requirements
Project safety or security requirements
When these requirements are flowed down to sub-projects, the allocation methodology is documented and, if necessary, interfaces control documents are used to control the interaction between sub-projects.
Project Scope Statement
The Project Scope Statement is a document that is used to provide clarity for both the project team and project stakeholders. The scope statement describes the major deliverables, provides a high-level description of acceptance criteria, and many times will also include constraints and project exclusions. On a Simple or Focused project, the Scope Statement can usually be captures within a paragraph or two. On a Full-scale or Complex project, the Scope Statement may be several pages in length.
When a large project has many divers stakeholders and project work is being accomplished in several locations, the Scope Statement becomes a continuing reminder of what the project is supposed to do, and what it is not supposed to do. It is referred to at Tollgate reviews to ensure the project stays on course and does not suffer scope creep.
Deliverables Deployment Diagram
The Deliverables Deployment Diagram is a socpe planning technique for Extreme or Adaptive projects. This technique starts with a deliverable of the project and then asks the question, "What is needed to create that deliverable?" This question may need to be asked several times to break the project deliverables down into actionable activities. This technique is especially powerful when the project deliverable has been changed and a revised scope must be established. I normally will create this diagram in fishbone or mind-map layout. Once all of the activities are identified, I then transfer them into a WBS Dictionary.
Work Breakdown Structure
There are several different ways to decompose the major project deliverables. They can be decomposed based upon subdividing deliverables as described in the Deliverables Deployment Diagram. They can also be decomposed based upon business process. They can be decomposed based upon which organization or department will do the work. It can also be decomposed based upon which project phase in which different elements of the work will be done. Any of these methods is acceptable and often a WBS is developed in a mix and match mode where different levels are developed using different approaches. My recommendation is to organize the decomposition based upon the way you intend to control the project. When organized in that manner, you can roll up lower levels of performance to quickly provide a high-level assessment of project status. However, on Complex projects, often there is a WBS structure that is mandated for the sub-projects. This aids the program manager in his or her effort to consolidate the sub-project inputs into an overal program plan and status. This approach is a benefit for the program manager but is often a bureacratic nightmare for the sub-project leader.
A WBS can be presented in two different modes. One mode is a diagram that looks like an organizational chart. The top of the chart is the major deliverables. As each layer is decomposed, additional levels are shown on the chart. The second mode is a table. The left column(s) shows the level of decomposition. Typically a numbering system or code is used to identify each item in the table. Each digit in the identifier number represents a different layer of decomposition. The table mode often is soon transformed into a WBS Dictionary which is discussed in the next section.
When managing a project using a spreadsheet as the project management information system the WBS Dictionary is the primary planning tool and tracking tool. Many Simple and Focused projects are managed using the spreadsheet approach. When that approach is chosen, the WBS Dictionary documents the result of the planning processes. As the project unfolds and additional activities are identified or if the project needs to be rebaselined at a Tollgate meeting, the spreadsheet is updated.