π Lecture 23 β WORK BREAKDOWN STRUCTURE
π Overview: This lecture focuses on the Work Breakdown Structure (WBS), providing preparation guides, checklists, and methods for structuring it effectively. It also examines common reasons why project plans fail, emphasizing the responsibilities of project managers and other stakeholders in avoiding these failures.
ποΈ Topics Covered
The lecture covers four main areas: Preparation Guides for Work Breakdown Structure (WBS), Checklists for Preparing Work Breakdown Structure (WBS), Methods for Structuring Work Breakdown Structure (WBS), and Why Do Plans Fail?. Each section provides practical guidelines, tools, and insights for creating robust WBS and understanding planning pitfalls.
π Lecture Summary
Preparation Guides for Work Breakdown Structure (WBS)
Preparation guides are essential for developing a robust Work Breakdown Structure (WBS). First, develop the WBS by subdividing the total effort into discrete and logical sub-elements, typically starting from a program level down to a manageable-size element. Include more than one cost center or contractor if it reflects reality. Next, check the proposed WBS for completeness, compatibility, and continuity. Ensure the WBS satisfies both functional (engineering/manufacturing/test) and program/project requirements, including recurring and nonrecurring costs. Also, verify that the WBS provides a logical subdivision of all project work, establish assignment of responsibilities to specific organizations, and finally, check the WBS against the reporting requirements of involved organizations.
Checklists for Preparing Work Breakdown Structure (WBS)
These checklists provide step-by-step guidance for creating the WBS. Focus on developing a preliminary WBS down to at least the top three levels for solicitation. Ensure the contractor extends this preliminary WBS in their solicitation response. After negotiations, the Contract Work Breakdown Structure (CWBS) should not normally extend lower than the third level. Assure the CWBS is compatible with reporting requirements and the contractor's organization and management system. Review CWBS elements for correlation with the specification tree, contract line items, end-items, data items, work statement tasks, and configuration management requirements. Define CWBS elements down to a meaningful level for management (WBS dictionary), specify reporting requirements for selected elements, and ensure the CWBS covers measurable effort, level of effort, apportioned effort, and subcontracts. Finally, assure that total costs at a particular level equal the sum of costs of constituent elements at the next lower level. For simple projects, a "tree diagram" or logic flow method can be used.
π Definition β Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
π Example: The WBS can be constructed as a tree diagram, where lower-level functional units are assigned to one, and only one, upper-level unit, ensuring clear accountability.
Methods for Structuring Work Breakdown Structure (WBS)
Companies often develop a "generic" methodology for the top three levels of the WBS, which remain the same across projects. Differences appear at levels 4, 5, and 6. The three most common methods for structuring the WBS are presented in Table 23.1:
| Method | Description | Best Suited For |
|---|---|---|
| Flow Method | Breaks work down into systems and major subsystems. | Projects less than two years in length |
| Life-Cycle Method | Similar to the flow method, uses project life-cycle phases. | Longer-duration projects (more than two years) |
| Organization Method | Structures work based on the organizational units (divisions, departments). | Repetitive projects or those requiring very little integration between functional units |
π‘ Why this matters: Choosing the correct WBS structuring method is critical for aligning the project's decomposition with its duration, complexity, and organizational context, directly impacting control and manageability.
Why Do Plans Fail?
Planning is not perfect, and plans fail for several reasons. Key reasons include: corporate goals not understood at lower levels, plans encompassing too much in too little time, poor financial estimates, plans based on insufficient data, no systematized planning process, planning performed by a planning group alone, unknown ultimate objectives, unknown staffing requirements, unknown major milestone dates, project estimates being best guesses, insufficient time for estimating, ignoring personnel skill availability, people not working towards the same specifications, and constant shuffling of personnel.
Responsibility for failure is often shared. If corporate goals are not understood, corporate executives are negligent. If plans fail due to extreme optimism, both project and line managers are responsible for not assessing risk. Erroneous financial estimates are the line manager's responsibility. If plans fail due to poor definition of requirements, the project manager is totally at fault.
Project managers must be willing to accept failure but also recognize problems from upper management or other groups. For example, a project manager might discover a project should have started "last month" to meet its completion date. In such cases, project managers become more dedicated when they are active members during planning and understand the assumptions and constraints. If a project manager is part of a planning group that prepares a schedule three years in advance, functional managers may not accept it later due to changes in technology, learning curves, or salary escalation.
Small mistakes accumulate to cause big damage, such as neglecting to inform a line manager about a prototype delay or not verifying resource availability. Plans can also fail if the project manager "bites off more than he can chew," leading to overburdening and potential failure if the manager becomes ill and was the only one who knew what was going on.
β Key Takeaways
The lecture provides a comprehensive toolkit for creating a Work Breakdown Structure (WBS) through specific preparation guides and checklists, emphasizing the importance of logical decomposition, compatibility with requirements and reporting, and integration with the contractor's management system. The three common methods for structuring a WBSβflow, life-cycle, and organizationβcater to different project durations and complexities. Understanding why plans fail is critical: failures often stem from unclear goals, poor estimates, and lack of systematized processes, with responsibility distributed among corporate executives, project managers, and line managers. A key lesson is that project managers must be active participants in the planning process to ensure commitment and realistic assumptions, and they must avoid overburdening themselves with all project knowledge.
π§ Quick Revision Questions
- What are the six key preparation guides for developing a Work Breakdown Structure (WBS)?
- What is a Contract Work Breakdown Structure (CWBS), and to what level should it normally extend after negotiations?
- Name the three common methods for structuring a Work Breakdown Structure (WBS) and describe the type of project each is best suited for.
- List four reasons why project plans fail.
- According to the lecture, who is responsible for a plan failing due to a poor definition of requirements?
π Lecture 24 β Schedules and Charts
π Overview: This lecture explores the critical role of schedules and charts in project management, detailing how they serve as master plans for integrating resources, tracking performance, and communicating with stakeholders. It covers the guidelines for schedule preparation, the sequence of scheduling activities, master production scheduling, and the comprehensive framework of a program plan. Understanding these elements is essential for effective project control and successful project completion.
ποΈ Topics Covered
This lecture covers detailed schedules and charts, including their purpose and the role of a scheduler. It then provides guidelines for schedule preparation, the sequence of preparing schedules, and the definition and objectives of a Master Production Schedule (MPS). Finally, it delves into the program plan, its importance, structure, and role in providing direction for a project.
π Lecture Summary
Detailed Schedules and Charts
The first major requirement after a program is approved is the scheduling of activities. For large programs, input from functional management is needed. A program scheduler may be assigned to develop and update activity schedules, which are crucial for tracking work and providing information to the program office, functional management, and the customer. Activity scheduling is a key tool for determining how company resources should be integrated to produce synergy and for projecting time-phased resource utilization. Schedules serve as master plans for accurate cost estimates.
π Definition β Scheduler: An individual responsible for continuously developing and updating activity schedules to provide a means of tracking program work.
π‘ Why this matters: Activity schedules are the single most important tool for integrating resources and tracking performance, making them fundamental to project success.
Guidelines for Preparation of Schedules
When preparing schedules, certain guidelines should be followed. First, all major events and dates must be clearly identified, especially those from the customer's statement of work. The exact sequence of work should be defined through a network showing interrelationships between events. Schedules must be directly relatable to the Work Breakdown Structure (WBS). Finally, all schedules must identify time constraints and required resources. The complexity of schedules depends on the number of events, the level of technical detail, and the intended audience, leading to the development of multiple schedules: summary schedules for management and detailed schedules for the doers. A key problem to identify is a hedge position, where a contractor may not meet a milestone date without incurring risk.
π Definition β Hedge Position: A situation in which the contractor may not be able to meet a customer's milestone date without incurring a risk, or may not be able to meet activity requirements following a milestone date because of contractual requirements.
π Example: A contractor has a milestone to deliver a prototype by June 1st. Due to a potential supplier delay, meeting this date is risky. The contractor is in a hedge position regarding this milestone.
Preparation Sequence of Schedules
The program office is responsible for integrating all detailed schedules into one master schedule. The program office first submits a request for detailed schedules to functional managers. These managers then review their schedules with the program office. The program office integrates all plans and verifies that contractual dates can be met. Before publication, rough drafts should be reviewed with the customer to verify completeness and prevent early revisions. The program office also develops organization charts and linear responsibility charts (LRCs) to clarify responsibility for each activity. The primary objective of detailed schedules is to coordinate activities into a master plan to complete the project with the best time, least cost, and least risk, constrained by factors like calendar dates and limited resources.
π Definition β Linear Responsibility Charts (LRCs): Charts established by the program office to clarify responsibilities for activities, especially when functions overlap between different organizational units.
π Formula: Primary objective of detailed schedules = Best time + Least cost + Least risk
π Example: For a construction project, the program office asks the engineering and procurement managers for their detailed schedules for designing and sourcing materials. After reviewing and integrating these, they create a master schedule showing that design must be complete before material procurement begins.
Master Production Scheduling
Master production scheduling is a concept used to develop a production plan, often over a three-month period, based on customer order backlogs. This plan is then exploded to determine what parts must be purchased or manufactured. However, rapidly changing customer requirements and fluctuating lead times can disrupt this process.
Master Production Schedule (MPS) Definition
A Master Production Schedule (MPS) is a statement of what will be made, how many units will be made, and when they will be made. It is a production plan, not a sales plan. The MPS considers the total demand on a plant's resources, including finished product sales, spare part needs, and interplant needs. It must also consider plant capacity and vendor requirements.
π Definition β Master Production Schedule (MPS): A statement of what will be made, how many units will be made, and when they will be made; it is a production plan that considers total demand on plant resources and capacity.
π‘ Why this matters: The MPS is a production plan that drives all other planning for materials, manpower, equipment, and financing.
Objectives of the Master Production Schedule (MPS)
The objectives of the MPS are to provide top management with a means to authorize and control manpower, inventory, and cash flow. It also aims to coordinate marketing, manufacturing, engineering, and finance activities by a common performance objective. Other objectives include reconciling marketing and manufacturing needs, providing an overall measure of performance, and providing data for material and capacity planning.
π Example: A car manufacturer uses an MPS to plan production of 10,000 SUVs in Q1. This authorizes the procurement of 10,000 engines, coordinates the marketing launch campaign, and ensures the finance department has allocated the necessary funds.
Program Plan
A program plan is a documented plan that is fundamental to project success. For large, complex programs, customers may require it to document all activities. The program plan serves as a guideline for the lifetime of the program and provides a framework to eliminate conflicts, provide a standard communication tool, verify understanding of customer objectives, and identify risks early. Its development can be time-consuming and costly, with input from all levels of the organization. The plan is a standard for measuring performance and serves as a "cookbook" by answering what, how, where, when, and why.
π Definition β Program Plan: A documented plan that serves as a guideline for the lifetime of a program, providing a framework to eliminate conflicts, standardize communication, and measure performance.
Most program plans are subdivided into four main sections:
- Introduction: Defines the program and its background.
- Summary and Conclusions: Identifies targets and objectives, and includes the program master schedule.
- Management: Contains procedures, charts (e.g., linear responsibility chart), and key personnel assignments.
- Technical: The largest section (up to 75-90%), including detailed breakdowns of charts, testing procedures, material specifications, and risk identification.
The program plan is used to provide program direction and is distributed to the program team and functional managers. It serves as a guide, not a complete set of all answers. While the plan may specify more than the contractual Statement of Work (SOW) , the contractor can revert to the SOW's minimum requirements if needed.
π Definition β Statement of Work (SOW) : A document that specifies the customer's requirements for a program, often including minimum requirements for tasks like testing.
π Example: A government contract's SOW requires testing 15 missile systems. The contractor's program plan initially shows testing 25. If the contractor faces a cost overrun, they can contractually revert to testing only 15 systems without informing the customer, though notification is typical.
β Key Takeaways
The most critical takeaways from this lecture are that schedules are the primary tool for integrating resources and tracking performance, and their preparation must follow clear guidelines, including alignment with the WBS. A Master Production Schedule (MPS) is a production plan that drives all other planning for materials and capacity, distinct from a sales plan. Finally, the program plan is a comprehensive, multi-section document that serves as a "cookbook" for the entire project, providing direction, measuring performance, and eliminating conflicts, with the Technical section being the largest part for R&D projects.
π§ Quick Revision Questions
- What are the four key guidelines for preparing project schedules?
- What is a "hedge position" in project scheduling?
- What is the difference between a Master Production Schedule (MPS) and a sales plan?
- What are the four main sections of a program plan, and which one is typically the most extensive?
- What are the three primary objectives that detailed schedules aim to achieve (the "best" outcomes)?
π Lecture 25 β Total Project Planning
π Overview: This lecture explores the comprehensive nature of total project planning, moving beyond simple scheduling and budgeting to include administrative structures, leadership styles, and conflict management. It emphasizes the critical importance of establishing project charters, management controls, and effective project managerβline manager interfaces for project success.
ποΈ Topics Covered
This lecture covers six main topics: Total Project Planning, including the development of Linear Responsibility Charts and factors affecting delegation of authority; The Project Charter as an internal legal document defining authority and scope; Management Control for establishing guidelines and policies; The Project ManagerβLine Manager Interface, including the "Brick Wall" concept; Project Fast-Tracking as a schedule acceleration technique; and Configuration Management for formal change control.
π Lecture Summary
25.1 Total Project Planning:
Planning is one of the most significant functions of management. Project planning involves planning for schedule development, budget development, project administration, leadership styles (interpersonal influences), and conflict management. The first two items involve quantitative aspects of planning, while project administration includes developing the Linear Responsibility Chart (LRC).
Although each project manager has authority to establish project policies and procedures, these must fall within general guidelines established by top management. The LRC can result from customer-imposed requirements above and beyond normal operations. For example, a customer may require a specific engineer to supervise and approve all testing of a certain item, requiring LRCs that can cause disruptions and conflicts within an organization.
Several key factors affect delegation of authority and responsibility from upper-level management to project management, and from project management to functional management: maturity of the project management function, size/nature/business base of the company, size and nature of the project, life cycle of the project, and capabilities of management at all levels.
Once agreement is reached on the project manager's authority and responsibility, results may be documented to delineate the role regarding: focal position, conflict between project manager and functional managers, influence to cut across functional and organizational lines, participation in major management and technical decisions, collaboration in staffing, control over allocation and expenditure of funds, selection of subcontractors, rights in resolving conflicts, input in maintaining team integrity, establishment of project plans, provisions for cost-effective information systems, maintaining customer liaison, promoting improvements, establishing project organization, and eliminating red tape.
Documenting the project manager's authority is necessary because: all interfacing must be kept simple, the project manager must have authority to "force" functional managers to depart from existing standards, gaining authority over uncontrolled elements is essential, and the project manager should not fully describe exact authority of team membersβproblem solving rather than role definition should be encouraged.
Power and authority are often discussed together but differ. Authority comes from people above you (by delegation), while power comes from people below you. You can have authority without power or power without authority. Most individuals maintain position power in traditional structures, but in project management, the reporting level may be irrelevant, especially with a project sponsor. The project manager's power base emanates from expertise, credibility with employees, and sound decision-making ability. The last item is usually preferredβif the project manager is regarded as a sound decision maker, employees give the project manager great power.
Leadership styles refer to interpersonal influence modes a project manager can use, and may require several different styles depending on project personnel makeup. Conflict management is important because if the project manager can predict conflicts and when they will occur, resolution can be planned through project administration. The objective is to develop a plan showing complete resource distribution and costs.
The project manager begins with a coarse arrow diagram network, then decides on the Work Breakdown Structure (WBS). The WBS is essential to the arrow diagram and should be constructed so reporting elements and levels are easily identifiable. For each WBS element, there will eventually be an arrow diagram and detailed chart. If too much detail exists, the project manager can refine by combining all logic into one plan and deciding work assignments. There is a risk of losing clarity by condensing diagrams. All charts and schedules can be integrated into one summary-level figure at each WBS level until the desired plan is achieved.
Finally, project, line, and executive management must analyze internal and external variables before finalizing schedules: product acceptance in the marketplace, present or planned manpower availability, economic constraints, degree of technical difficulty, manpower availability, personnel training availability, and project priority. In small companies, certain items like the LRC may be omitted.
π Definition β Linear Responsibility Chart (LRC): A chart that shows the relationships between tasks and the individuals or departments responsible for them, often resulting from customer-imposed requirements.
π‘ Why this matters: Understanding the difference between power and authority is crucial for project managers, as they may need to lead teams without formal hierarchical authority.
25.2 The Project Charter:
Originally, the concept behind the project charter was to document the project manager's authority and responsibility, especially for projects away from the home office. Today, the project charter has been expanded to become more of an internal legal document identifying to line managers and personnel not only the project manager's authority and responsibility, but also the management- and/or customer-approved scope of the project.
In theoretical terms, the sponsor prepares the charter and affixes their signature, but in reality, the project manager may prepare it for the sponsor's signature. At a minimum, the charter should include: identification of the project manager and authority to apply resources, the business purpose including assumptions and constraints, and summary of conditions defining the project.
A charter is a "legal" agreement between the project manager and the company. Some companies supplement the charter with a "contract" as an agreement between project and line organizations. Recently, some companies have converted the charter into a highly detailed document containing: scope baseline/scope statement, scope and objectives (Statement of Work/SOW), specifications, Work Breakdown Structure (template levels), timing, spending plan (S-curve), management plan, resource requirements and man loading, rΓ©sumΓ©s of key personnel, organizational relationships and structure, responsibility assignment matrix, support required from other organizations, project policies and procedures, change management plan, and management approval.
The project charter may function as the project plan when it contains a scope baseline and management plan. This is not really an effective use of the charter but may be acceptable on certain internal customer projects.
π Definition β Project Charter: An internal legal document identifying the project manager's authority and responsibility, as well as the management- and/or customer-approved scope of the project.
π‘ Why this matters: The charter serves as the foundational document that formally authorizes the project and the project manager's authority to proceed.
25.3 Management Control:
Careful management control must be established because the planning phase provides fundamental guidelines for the remainder of the project. Since planning is an ongoing activity for various programs, management guidelines must be established on a company-wide basis to achieve unity and coherence.
All functional organizations and individuals working directly or indirectly on a program are responsible for identifying scheduling and planning problems requiring corrective action during both the planning and operating cycles. The program manager bears ultimate and final responsibility for identifying requirements for corrective actions.
Management policies and directives are written specifically to assist the program manager in defining requirements. Without clear definitions during the planning phase, many projects run off in various directions. Many companies establish planning and scheduling management policies for project and functional managers, as well as a brief description of how they should interface.
π Formula: Management Control System β Policies + Directives + Clear Definitions = Project Unity and Coherence
25.4 The Project ManagerβLine Manager Interface:
Good project planning requires a good working relationship between project and line managers. The utilization of management controls does not necessarily guarantee successful project planning.
At this interface, the project manager answers: What is to be done? (using SOW, WBS), When will the task be done? (using summary schedule), Why will the task be done? (using SOW), and How much money is available? (using SOW). The line manager answers: How will the task be done? (technical criteria), Where will the task be done? (technical criteria), and Who will do the task? (staffing).
Project managers may be able to tell line managers "how" and "where" if the information appears in the SOW as a requirement. Even then, the line manager can take exception based on technical expertise.
Figures 25.2 "The Brick Wall" and 25.3 "Modified Brick Wall" show what happens when project managers overstep their bounds. In Figure 25.2, the manufacturing manager built a brick wall to keep project managers away from his personnel because they were telling his line people how to do their job. In Figure 25.3, subproject managers (equivalent to project engineers) had career paths to Assistant Project Managers, but they still felt technically competent to give technical direction, creating havoc for engineering managers.
π Definition β Brick Wall Concept: A metaphorical representation of the barrier that line managers create when project managers overstep their bounds by telling line personnel how to do their technical work.
π‘ Why this matters: The simplest solution is for the project manager to provide technical direction through the line managers, as line managers are supposedly the true technical experts.
25.5 Project Fast-Tracking:
No matter how well we plan, sometimes constraints change. Consider Figure 25.4 "The Information Explosion"βif execution time is one year, preparing working drawings and specifications down through level 5 of the WBS requires an additional 35% of expected execution time. If a feasibility study is required, an additional 40% is added. So if execution is one year, the entire project is almost two years.
If management wishes to keep the end date fixed but the start date is delayed due to lack of funding, how can this be accomplished without sacrificing quality? The answer is fast-tracking the project. Fast-tracking means activities normally done in series are done in parallel. An example is when construction begins before detail design is completed.
Fast-tracking can accelerate the schedule but requires additional risks. If risks materialize, either the end date will slip or expensive rework will be needed. Almost all project-driven companies fast-track projects. The danger is when fast-tracking becomes a way of life on all projects.
π Definition β Fast-Tracking: A project schedule compression technique where activities that are normally done in series are done in parallel, such as beginning construction before detail design is completed.
π Formula: Fast-Tracking β Parallel Activities = Schedule Acceleration + Increased Risk
π Example: A one-year construction project with 35% additional time for working drawings and 40% for feasibility study would normally take almost two years. If the start date is delayed but the end date must remain fixed, fast-tracking allows construction to begin before detailed design is complete, compressing the schedule.
25.6 Configuration Management:
Configuration management or configuration change control is one of the most critical tools employed by a project manager. As projects progress through various life-cycle phases, the cost of engineering changes can grow boundlessly. It is not uncommon for companies to bid on proposals at 40% below their own cost hoping to make up the difference downstream with engineering changes. It is also common for executives to "encourage" project managers to seek out engineering changes because of their profitability.
Configuration management is a control technique, through an orderly process, for formal review and approval of configuration changes. If properly implemented, it provides: appropriate levels of review and approval for changes, focal points for those seeking to make changes, and a single point of input to contracting representatives for approved changes.
At a minimum, the configuration control committee should include representation from the customer, contractor, and line group initiating the change. Discussions should answer: What is the cost of the change? Do the changes improve quality? Is the additional cost justifiable? Is the change necessary? Is there an impact on the delivery date?
Changes cost money, so configuration management must be implemented correctly. Implementation steps include: define the starting point or "baseline" configuration, define the "classes" of changes, define necessary controls or limitations on both customer and contractor, and identify policies and procedures (board chairman, voters/alternatives, meeting time, agenda, approval forums, step-by-step processes, expedition processes for emergencies).
Effective configuration control pleases both customer and contractor. Overall benefits include: better communication among staff, better communication with the customer, better technical intelligence, reduced confusion for changes, screening of frivolous changes, and providing a paper trail. Configuration control is not a replacement for design review meetings or customer interface meetingsβthese are still an integral part of all projects.
π Definition β Configuration Management: A control technique, through an orderly process, for formal review and approval of configuration changes to maintain project integrity.
π Definition β Baseline Configuration: The defined starting point configuration from which all changes are measured and evaluated.
π‘ Why this matters: Configuration management prevents uncontrolled changes that could lead to cost overruns, schedule delays, and quality problems, while still allowing necessary changes through a formal process.
β Key Takeaways
The most critical points from this lecture are: (1) Total project planning encompasses schedule, budget, administration, leadership, and conflict managementβnot just quantitative aspects. (2) The project charter is a formal document authorizing the project manager's authority and responsibility, serving as an internal legal agreement between the project manager and the company. (3) The project managerβline manager interface requires clear boundaries: project managers define what, when, why, and how much; line managers define how, where, and whoβoverstepping creates "brick walls." (4) Fast-tracking accelerates schedules by running activities in parallel but introduces significant risk of rework or schedule slippage. (5) Configuration management provides formal control over changes through a committee process, preventing uncontrolled cost growth while maintaining project quality and schedule.
π§ Quick Revision Questions
- What are the five components of project planning according to this lecture, and which two are considered quantitative aspects?
- What is the difference between power and authority in project management, and from where does each originate?
- What is the minimum content that a project charter should include, and who typically prepares it?
- What does the "Brick Wall" concept illustrate about the project managerβline manager interface, and what is the recommended solution?
- What are the key questions that a configuration control committee should answer when evaluating a proposed change?