General Scope Document: Project Strategy

This month, we will discuss the fifth component of the general scope document: project strategy. Components of a General Scope Document

1. purpose and justification of the project
2. scope description
3. high-level project requirements
4. project boundaries
5. project strategy
6. project deliverables
7. acceptance criteria (owner)
8. project constraints
9. project assumptions
10. cost estimates
11. cost-benefit analysis

As we move through each portion of the general scope document, specific details begin to emerge. Project strategy outlines in detail how the project team (remember this is a team effort) will execute the project. Obviously, strategy may vary depending on the size of the project. For example, a simple pump upgrade will require significantly less detail than a major plant expansion. You still need to do your homework, and all parties with vested interest in the project must be involved. What does a typical project strategy statement look like? Let us explore a simple pump upgrade project as an example.

Sample Project Strategy Statement

The project team will use a pumping system specialist from XYZ engineering. XYZ consulting will support the project leader and team in developing a flow model (using state-of-the-art flow modeling software) of the system in question to determine the most efficient, reliable pump package that will ensure the upgraded system will meet current and future requirements as defined by the project leader and team members.

Details

The project team has also determined that they do not have the in-house resources to perform this work and (as a team) have identified and agreed on a specific engineering firm with the necessary skill sets that the team members feel is necessary to ensure the success of the pump or system upgrade. The team also clearly stated that the flow model must be performed using state-of-the-art flow modeling software and that the pump upgrade must meet current and future requirements (as defined by the team). As you can see, details begin to emerge in the general scope document—details that may or may not have been identified had the project leader not had the input of those with a vested interest in the system in question. Next month, we will address project deliverables and more details.