π Lecture 21 β Project Planning (Contd.)
π Overview: This lecture continues the discussion on project planning by focusing on the Statement of Work (SOW) β a critical document that narratively describes the work required for a project. It explains the importance of clear SOW preparation, common causes of misinterpretation that lead to costly scope creep, and provides detailed guidelines and checklists for creating effective SOWs.
ποΈ Topics Covered
The lecture covers two main topics: first, The Statement of Work (SOW), including its definition, who prepares it for internal versus external projects, the distinction between proposal SOW and Contract Statement of Work (CSOW), and common misinterpretation causes; second, Guidelines for Preparing SOW, which provides 12 specific preparation guidelines followed by a comprehensive 16-point checklist for SOW writers.
π Lecture Summary
21.1 The Statement of Work (Sow):
The Statement of Work (SOW) is a narrative description of the work required for the project. Its complexity is determined by the desires of top management, the customer, and/or user groups. For internal projects, the SOW is prepared by the project office with input from user groups because user groups tend to write in overly scientific terms. The project office, having skilled writers, prepares the SOW and submits it to user groups for verification and approval.
For external projects (competitive bidding), the contractor may prepare the SOW for the customer who lacks trained preparers. The contractor submits the SOW to the customer for approval. It is also common for the project manager to rewrite a customer's SOW so line managers can price out the effort.
π Definition β Statement of Work (SOW): a narrative description of the work required for the project
In a competitive bidding environment, there are two SOWs β the SOW used in the proposal and a "Contract Statement of Work" (CSOW) . Similarly, there may be a proposal "Work Breakdown Structure" (WBS) and a "Contract Work Breakdown Structure" (CWBS) . Special care is needed to discover all discrepancies between SOW/WBS and CSOW/CWBS, or additional costs may be incurred. A good proposal does not guarantee mutual understanding. For large projects, fact-finding is usually required before final negotiations to ensure agreement on the SOW, required work, proposed work, cost basis, and related elements.
π‘ Why this matters: Misunderstandings between the proposal SOW and the signed Contract SOW can lead to unbudgeted work and financial losses.
SOW preparation is not easy. Three examples illustrate costly misinterpretations:
- A SOW requiring "a minimum of fifteen tests" β contractor priced 20 tests "to play it safe," but customer demanded another 15 tests after inconclusive results, causing a $40,000 cost overrun.
- The Navy's SOW stating prototype must be tested in "water" β contractor used a swimming pool, but the Navy meant the Atlantic Ocean, costing $1 million to transport equipment.
- A SOW requiring transport using "aerated" boxcars β contractor used open-top boxcars (air from above), but customer wanted aeration from below; goods were ruined by rain, leading to a court case.
Common causes of SOW misinterpretation include:
- Mixing tasks, specifications, approvals, and special instructions
- Using imprecise language ("nearly," "optimum," "approximately")
- No pattern, structure, or chronological order
- Wide variation in size of tasks
- Wide variation in how to describe details of the work
- Failing to get third-party review
Misinterpretations lead to creeping scope (also called "creeping elegance"). The best control is a good upfront requirements definition, though not always possible. In aerospace, defense, and MIS industries, creeping scope had become a way of life. An example showed a project manager refusing scope changes once requirements were defined, instead putting all change requests into a follow-on enhancement project that was later neither funded nor approved.
21.2 Statement of Work (Sow) Preparation Guidelines:
Guideline 1: Every SOW exceeding two pages should have a table of contents conforming to the Contract Work Breakdown Structure (CWBS) coding structure. Items in the SOW should rarely be absent from the CWBS, though it is not absolutely necessary to restrict items to those cited.
Guideline 2: Clear and precise task descriptions are essential. The writer must consider varied readers (lawyers, buyers, engineers, cost estimators, accountants, specialists). A good SOW states precisely the product or service desired. Clarity affects contract administration since it defines scope β work outside that scope means new procurement with increased costs.
Guideline 3: Avoid ambiguity by considering how writing affects readers. Spell out all government obligations. For government approval actions, set a time limit. For Government-Furnished Equipment (GFE) or services, state the nature, condition, and delivery time if feasible.
π Definition β Government-Furnished Equipment (GFE): equipment and/or services provided by the government to the contractor for use in performing the contract
Guideline 4: Any provision taking control of work from the contractor, even temporarily, may relieve the contractor of responsibility.
Guideline 5: Use active terminology rather than passive. Say "the contractor shall conduct a test" rather than "a test should be conducted." Use the mandatory term "shall" for firm requirements, not the permissive "should."
Guideline 6: Limit abbreviations to common usage. Provide a list of all pertinent abbreviations and acronyms at the beginning of the SOW. When first using a term, spell it out and show the abbreviation or acronym in parentheses.
Guideline 7: When defining a division of responsibilities between contractor and other agencies, include a separate SOW section to delineate such responsibilities.
Guideline 8: Include procedures for when immediate decisions cannot be made (e.g., "as approved by the contracting officer" or "the contractor shall submit a report each time a failure occurs").
Guideline 9: Do not over-specify. Depending on work nature and contract type, specify required results or end-items and let the contractor propose the best method.
Guideline 10: Describe requirements in sufficient detail for clarity and practical application. For every deliverable hardware, report, or immediate action, do not say "as necessary" β specify who makes the judgment (contractor or government). For expensive services like technical liaison, provide a ceiling (e.g., a level of effort or man-hour pool).
Guideline 11: Avoid extraneous material and requirements that add unnecessary cost. Screen out unnecessary data requirements; specify only what is essential and when. Recommend specifying data requirements separately in a data requirements appendix.
Guideline 12: Do not repeat detailed requirements already in applicable documents β incorporate them by reference. If amplification, modification, or exceptions are needed, make specific reference to applicable portions and describe the change.
A checklist is provided for SOW writers:
- Is the SOW (with preliminary CWBS) specific enough for a contractor to tabulate manpower and resources needed for each SOW task element?
- Are specific duties stated so the contractor knows what is required and the contracting officer's representative can verify compliance?
- Are all parts written so there is no question about what the contractor is obligated to do and when?
- When referencing other documents, is the proper document described, properly cited, and cross-referenced to applicable SOW task elements?
- Are any specifications or exhibits applicable? If so, are they properly cited and referenced?
- Are directions clearly distinguishable from general information?
- Is there a time-phased data requirement for each deliverable item? Does elapsed time specify calendar or work days?
- Are proper quantities shown?
- Have headings been checked for format and grammar? Is the numbering system cross-referenced with CWBS?
- Have appropriate procurement regulations been followed?
- Has extraneous material been eliminated?
- Can SOW task/contract line items be summarized to discrete third-level CWBS elements?
- Have all data requirements been specified separately in an appendix or equivalent?
- Have all extraneous data requirements been eliminated?
- Are security requirements adequately covered if required?
- Has its availability to contractors been specified?
Finally, there should be a management review of the SOW preparation interpretation. During development, the project manager should hold frequent reviews with project and functional specialists to ensure technical and data requirements conform to guidelines. The CWBS/SOW matrix should analyze completeness. After incorporating comments, a final team review produces a draft SOW for functional and project managers. A final draft is prepared and reviewed with the program manager, contracting officer, or higher management. The final review includes a briefing on the total Request for Proposal (RFP) package. Concurrence from other program offices or government agencies should be obtained.
π Key Framework: CWBS/SOW Matrix β a tool to analyze the Statement of Work for completeness by cross-referencing each SOW element with the Contract Work Breakdown Structure
β Key Takeaways
The Statement of Work is the foundational document defining project work scope; internal SOWs are prepared by the project office while external SOWs may be prepared by contractors for customers. Misinterpretations of SOW language β caused by imprecise terms, mixing tasks and instructions, or lacking structure β lead to costly creeping scope and financial losses. To prevent this, SOW writers must use active mandatory language ("shall"), avoid ambiguity, specify responsibilities clearly, and never over-specify or add extraneous requirements. A final management review using the CWBS/SOW matrix is essential to ensure completeness and alignment with the contract structure before the Request for Proposal is released.
π§ Quick Revision Questions
- Who typically prepares the Statement of Work for internal company projects, and why?
- What are the two different SOWs that exist in a competitive bidding environment?
- List at least four common causes of SOW misinterpretation.
- What is the recommended term to use for firm requirements: "shall" or "should"?
- What is the purpose of the CWBS/SOW matrix during the SOW review process?
π Lecture 22 β WORK BREAKDOWN STRUCTURE
π Overview: This lecture introduces the Work Breakdown Structure (WBS), a fundamental planning tool in project management that breaks work into manageable, independent, integratable, and measurable elements. It explains the six-level indented structure, characteristics of each level, work packages, and the critical role of WBS in cost control, scheduling, and responsibility assignment.
ποΈ Topics Covered
The lecture covers the introduction to Work Breakdown Structure and its importance as a common framework for planning, budgeting, and tracking. It then examines characteristics of various WBS levels (levels 1-6), work package characteristics and their role as the critical management level. Guidelines for contractor-developed WBS are discussed, followed by criteria for developing WBS. The lecture addresses WBS decomposition problems including the risks of excessive detail and the use of "hammock" activities. It concludes with practical uses of WBS for cost control and scope management.
π Lecture Summary
22.1 Introduction
To successfully accomplish contract and corporate objectives, a plan is required that defines all effort, assigns responsibility, and establishes schedules and budgets. The detailed planning is established in accordance with company budgeting policy before contractual efforts begin. In planning a project, the project manager must structure work into small elements that are manageable (specific authority can be assigned), independent (minimum interfacing with other elements), integratable (total package can be seen), and measurable in terms of progress.
After project requirements definition, the first major planning step is developing the Work Breakdown Structure (WBS). A WBS is a product-oriented family tree subdivision of the hardware, services, and data required to produce the end product. It is structured according to how work will be performed and reflects how costs and data will be summarized and reported. Preparation of WBS also considers scheduling, configuration management, contract funding, and technical performance parameters. It is the single most important element because it provides a common framework from which: total program can be described as a summation of subdivided elements; planning can be performed; costs and budgets can be established; time, cost, and performance can be tracked; objectives can be linked to company resources; schedules and status-reporting procedures can be established; network construction and control planning can be initiated; and responsibility assignments can be established.
The WBS acts as a vehicle for breaking work down into smaller elements, providing greater probability that every major and minor activity will be accounted for.
The most common WBS is the six-level indented structure:
- Level 1: Total program (composed of a set of projects)
- Level 2: Project level
- Level 3: Task level
- Levels 4-6: Lower levels for detailed control
The summation of activities and costs at each level must equal the total at the next higher level. Program management becomes synonymous with the integration of activities, and the project manager acts as the integrator using WBS as the common framework.
WBS provides the basis for: responsibility matrix, network scheduling, costing, risk analysis, organizational structure, coordination of objectives, and control (including contract administration).
22.2 Characteristics of Various Levels of the Work Breakdown Structure (WBS)
The upper three levels of WBS are normally specified by the customer (if part of Request for Proposal/Request for Quotation) as summary levels for reporting. The lower levels are generated by the contractor for in-house control. Each level serves a vital purpose: Level 1 is used for authorization and release of all work, budgets are prepared at level 2, and schedules are prepared at level 3.
Generalized characteristics for these levels include:
- The top three levels of WBS reflect integrated efforts and should not be related to one specific department. Effort required by departments should be defined in subtasks and work packages.
- The summation of all elements in one level must be the sum of all work in the next lower level.
- Each element of work should be assigned to one and only one level of effort (e.g., foundation construction of a house should be in one project, not extended over multiple levels).
- The level at which the project is managed is generally called the work package level, though work packages can exist at any level below level one.
- WBS must be accompanied by a description of scope of effort, otherwise only those who issue it will fully understand what work must be accomplished. It is common to reproduce the customer's statement of work as the description.
- It is best policy for the project manager to allow all line managers to assess risks in the WBS, as they are usually the recognized experts.
Project managers typically manage at the top three levels and prefer to provide status reports at these levels. Some companies try to standardize the top three levels for every project, with differences only in levels 4-6. This works well for companies with similar projects but is often impossible for companies with diverse projects.
A work package is the critical level for managing WBS, though line managers typically supervise and perform work packages with status reporting provided to the project manager at higher levels. Work packages are natural subdivisions of cost accounts and constitute the basic building blocks used by the contractor in planning, controlling, and measuring contract performance. A work package is simply a low-level task or job assignment that describes work to be accomplished by a specific performing organization or group of cost centers and serves as a vehicle for monitoring and reporting progress.
π Definition β Work Package: The generic term used to identify discrete tasks that have definable end results. Ideal work packages are 80 hours and less than 2-4 weeks, though this may not be possible on large projects.
Work package documentation need not contain complete, stand-alone descriptions; supplemental documentation may augment descriptions. However, descriptions must permit cost account managers and work package supervisors to understand and distinguish one work package from another.
The cost account intersection occurs where the WBS and organizational structure meet, as shown in Figure 22.3. Short-term work packages are desirable for evaluation of accomplishment. This is not intended to force arbitrary cutoffs, but work packages should be natural subdivisions planned according to how work will be done. With short work packages, little assessment of work-in-process is required; evaluation is based mainly on work package completions. Longer work packages make assessment more difficult and subjective unless subdivided by objective indicators like discrete milestones with pre-assigned budget values.
In setting up WBS, tasks should: have clearly defined start and end dates; be usable as a communications tool where results can be compared with expectations; be estimated on "total" time duration, not when tasks must start or end; and be structured to minimize project office control and documentation.
22.3 Characteristics of Work Package
For large projects, planning will be time phased at the work package level of WBS. The work package has the following characteristics:
- Represents units of work at the level where work is performed
- Clearly distinguishes one work package from all others assigned to a single functional group
- Contains clearly defined start and end dates representative of physical accomplishment
- Specifies a budget in terms of dollars, man-hours, or other measurable units
- Limits work to relatively short periods to minimize work-in-process effort
π WBS Numbering System Example: A simple WBS numbering system follows the work breakdown: 01-03-00 represents project 3 of program 01, while 01-03-02 represents task 2 of project 3. This numbering system is not standard; each company may have its own system depending on how costs are controlled.
π Example: Table 22.1 shows a WBS for New Plant Construction and Start-Up where the first number (01) represents the total program, the second number represents the project, and the third identifies the task.
The preparation of WBS is not easy. WBS is a communications tool providing detailed information to different management levels. If it does not contain enough levels, integration of activities may prove difficult. If too many levels exist, unproductive time will be spent. Each major work element should be considered by itself. WBS establishes the number of required networks for cost control. On many programs, the customer establishes the WBS.
22.4 Guidelines for WBS by Contractor
When a contractor is required to develop a WBS, certain guidelines must be considered:
- Complexity and technical requirements of the program (statement of work)
- Program cost
- Time span of the program
- Contractor's resource requirements
- Contractor's and customer's internal structure for management control and reporting
- Number of subcontracts
Applying these guidelines serves to identify the complexity of the program. These data must then be subdivided and released with detailed information to different organizational levels. WBS should follow specified criteria because although the program office prepares WBS, the actual work is performed by the doers, not the planners. Both doers and planners must be in agreement on what is expected.
22.5 Criteria for Developing Work Breakdown Structure (WBS)
Following is a sample listing of criteria for developing WBS:
- WBS and work description should be easy to understand
- All schedules should follow the WBS
- No attempt should be made to subdivide work arbitrarily to the lowest possible level; the lowest level should not have a ridiculous cost compared to other efforts
- Since scope can change during a program, maintain flexibility in the WBS
- WBS can act as a list of discrete and tangible milestones so everyone knows when milestones are achieved
- Level of WBS can reflect the "trust" you have in certain line groups
- WBS can be used to segregate recurring from nonrecurring costs
- Most WBS elements (at the lowest control level) range from 0.5 to 2.5 percent of the total project budget
22.6 Work Breakdown Structure (WBS) Decomposition Problems
There is a common misconception that WBS decomposition is an easy task. In WBS development, the top three levels (management levels) are usually roll-up levels. Preparing templates at these levels is becoming common practice. However, at levels 4-6, templates may not be appropriate for the following reasons:
- Breaking work down to extremely small work packages may require creating hundreds or thousands of cost accounts and charge numbers. This could increase management, control, and reporting costs to a point where costs exceed benefits. While a typical work package may be 200-300 hours and approximately two weeks in duration, consider a large project with more than one million direct labor hours.
- Breaking work down to small work packages can provide accurate cost control if, and only if, line managers can determine costs at this level of detail. Line managers must have the right to tell project managers that costs cannot be determined at the requested level of detail.
- WBS is the basis for scheduling techniques like Arrow Diagramming Method (ADM) and Precedence Diagramming Method (PDM). At low WBS levels, interdependencies between activities can become so complex that meaningful networks cannot be constructed.
π Definition β Hammock Activity: An activity that encompasses several activities where exact cost identification cannot be accurately determined. For example, "management support" or "project office" includes overall project management, data items, management reserve, and possibly procurement. The advantage is that charge numbers are under direct control of the project manager.
Another misconception is that work packages should be approximately 80 hours and less than two weeks to a month. While this may be true on small projects, it would necessitate millions of work packages on large jobs, which is impractical even if line managers could control packages of this size.
Cost analysis down to the fifth level is advantageous from a cost control viewpoint. However, the cost to prepare data to each lower level might increase exponentially, especially if the customer requires data in a specified format not part of the company's standard operating procedures. Level-5 work packages are normally for in-house control only. Some companies bill customers separately for each level of cost reporting below level 3.
WBS can be subdivided into sub-objectives with finer divisions of effort as we go lower. By defining sub-objectives, we add greater understanding and clarity of action for individuals who will complete the objectives. When work is structured, understood, easily identifiable, and within individual capabilities, there will be high confidence the objective can be reached.
WBS can also structure work for objectives like lowering cost, reducing absenteeism, improving morale, and lowering scrap factors. In such cases, the lowest subdivision becomes an end-item or sub-objective, not necessarily a work package as described.
π‘ Why this matters: Understanding the balance between sufficient detail for control and excessive detail that creates management overhead is critical for effective WBS design.
22.7 Uses of Work Breakdown Structure (WBS)
Once WBS is established and the program is "kicked off," it becomes very costly to add or delete activities or change reporting levels because of cost control. Many companies do not give careful forethought to the importance of a properly developed WBS and ultimately risk cost control problems downstream.
One important use of WBS is that it serves as a cost control standard for any future activities that may follow on or be similar. A common mistake is combining direct support activities with administrative activities. For example, a department manager for manufacturing engineering may provide administrative support (attending team meetings) throughout the program. If this administrative support is spread over each project, a false picture is obtained of actual hours needed to accomplish each project. If one project is canceled, support man-hours for the total program would be reduced when, in fact, the administrative and support functions may be constant regardless of the number of projects and tasks.
WBS accompanying customer Requests for Proposals (RFPs) often contains much more scope of effort than existing funding will support. This is done intentionally by the customer hoping a contractor may be willing to "buy in." If the contractor's price exceeds customer funding, eliminating activities from WBS must reduce scope of effort. By developing a separate project for administrative and indirect support activities, the customer can easily modify costs by eliminating direct support activities of the canceled effort.
Finally, the usefulness and applicability of WBS varies. Many companies and industries have been successful in managing programs without WBS, especially on repetitive-type programs.
β Key Takeaways
The Work Breakdown Structure is the single most important planning element in project management, providing a common framework for defining all work, assigning responsibility, and establishing budgets and schedules. The six-level indented structure works from total program (level 1) down to work packages (levels 4-6), with the critical management point being the work package level where actual work is performed and controlled. Work packages should have clear start/end dates, budgets, and be short-term (ideally 80 hours, 2-4 weeks) to minimize work-in-process assessment problems. Proper WBS development requires balancing sufficient detail for control against the risk of creating excessive cost accounts that increase management costs beyond benefits. The WBS must remain flexible as scope changes, and careful forethought is essential since modifying WBS after program kickoff is very costly.
π§ Quick Revision Questions
- What are the four characteristics that project work elements should have, and why is each important for project control?
- Explain the six-level indented structure of WBS: what does each level represent, and who typically specifies the upper three levels versus the lower levels?
- What is a work package, what are its key characteristics, and why are short-term work packages (80 hours, 2-4 weeks) desirable?
- What problems can arise when decomposing WBS to extremely detailed work packages at levels 4-6, and how do "hammock activities" help address these problems?
- Why is it important to separate direct support activities from administrative activities when developing WBS, and what cost control risk arises if they are combined?