MGMT627 — Final Term Summary (Lectures 23–45)

📘 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:

💡 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

1. What are the six key preparation guides for developing a Work Breakdown Structure (WBS)?
2. What is a Contract Work Breakdown Structure (CWBS), and to what level should it normally extend after negotiations?
3. Name the three common methods for structuring a Work Breakdown Structure (WBS) and describe the type of project each is best suited for.
4. List four reasons why project plans fail.
5. 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:

1. Introduction: Defines the program and its background.
2. Summary and Conclusions: Identifies targets and objectives, and includes the program master schedule.
3. Management: Contains procedures, charts (e.g., linear responsibility chart), and key personnel assignments.
4. 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

1. What are the four key guidelines for preparing project schedules?
2. What is a "hedge position" in project scheduling?
3. What is the difference between a Master Production Schedule (MPS) and a sales plan?
4. What are the four main sections of a program plan, and which one is typically the most extensive?
5. 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

1. What are the five components of project planning according to this lecture, and which two are considered quantitative aspects?
2. What is the difference between power and authority in project management, and from where does each originate?
3. What is the minimum content that a project charter should include, and who typically prepares it?
4. What does the "Brick Wall" concept illustrate about the project manager–line manager interface, and what is the recommended solution?
5. What are the key questions that a configuration control committee should answer when evaluating a proposed change?

📘 Lecture 26 — PROJECT SCOPE MANAGEMENT

📖 Overview: This lecture covers the critical concept of project scope, detailing what a project contains or delivers and why scope definition is essential for project success. It explores the differences between scope, objectives, and goals, explains the phenomena of scope creep, and outlines the formal processes of project scope management including initiation, planning, definition, verification, and change control.

🗂️ Topics Covered

The lecture covers the definition and importance of scope in project management, the distinction between scope (in/deferred/out), objectives, and goals, and the differences between business case, project charter, and scope document. It explains scope creep including features/technology scope creep and customer-pleasing scope creep, the scope management plan, and the five processes of project scope management: initiation, scope planning, scope definition, scope verification, and scope change control with detailed inputs, outputs, and components.

📝 Lecture Summary

26.1 Scope

Scope is what the project contains or delivers. When starting to plan the scope of the project, think about the big picture first — concentrate on major deliverables and not get bogged down with detail. The scope of a project is the sum total of all of a project's products and their requirements or features. Sometimes the term scope is used to mean the totality of work needed to complete a project.

In traditional project management, the tools to describe a project's scope (product) are the product breakdown structure and product descriptions. The primary tool to describe a project's scope is the Work Breakdown Structure (WBS) . Extreme project management advocates the use of user stories, feature lists and feature cards to describe a project's scope. If requirements are not completely defined and described and if there is no effective change control in a project, scope creep or requirements creep may ensue.

💡 Why this matters: Without clear scope definition, projects face uncontrolled expansion of requirements, leading to budget overruns and schedule delays.

26.2 Difference Between Scope (In/Deferred/Out), Objectives and Goals

Goals and objectives are what the business wants to achieve through this project — they define WHY the client wants to undertake the project. Scope defines the size of the project. Scope can include such areas as: departments, geographic locations, deliverables, and features and functions. Often scope is limited by schedule and budget constraints.

Something in scope will be included in the current release or stage. Something deferred will be delivered in a later release. Something out of scope will not be included in the project. It is important to explicitly identify items out of scope to reduce misunderstandings which can generate conflict and hard feelings.

🔑 Definition — Scope (In/Deferred/Out): Items classified as "in scope" are included in the current phase, "deferred" items are postponed to later releases, and "out of scope" items are explicitly excluded from the project to prevent misunderstandings.

26.3 Difference Between Business Case, Project Charter and Scope Document

A business case is usually prepared before project approval. If you are a contractor, your proposal would be similar to a business case. A project charter providing the project manager with formal authorization to proceed with the project is issued to a team by the project sponsor before the project starts. The project scope document defines the project scope — it should be attached to the business case and to the project charter. The project scope will be refined as you proceed through the project. Scope is bound to change, and this is to be expected — as the detail becomes clearer, more complications creep in that are not foreseeable at the start.

🔑 Definition — Business Case: A document prepared before project approval that justifies the project and outlines expected benefits, costs, and risks. 🔑 Definition — Project Charter: A document issued by the project sponsor that formally authorizes the project and gives the project manager authority to apply organizational resources. 🔑 Definition — Project Scope Document: A document that defines the project scope, attached to the business case and project charter, and refined as the project proceeds.

26.4 Scope Creep

Scope creep (also called requirement creep, feature creep, and sometimes kitchen sink syndrome) in project management refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence to be avoided.

Typically, the scope increase consists of either new products or new features of already approved product designs, without corresponding increases in resources, schedule, or budget. As a result, the project team risks drifting away from its original purpose and scope on unplanned additions. Therefore, scope creep can also result in a project team overrunning its original budget and schedule.

Scope creep can be a result of:

• Poor change control
• Lack of proper initial identification of what is required to bring about the project objectives
• Weak project manager or executive sponsor
• Poor communication between parties

Scope creep is a risk in most projects. Most mega projects fall victim to scope creep. Scope creep often results in cost overrun.

🔑 Definition — Scope Creep: Uncontrolled changes in a project's scope that occur when scope is not properly defined, documented, or controlled, typically resulting in cost overruns and schedule delays.

26.4.1 Features (Technology) Scope Creep Management

Features (Technology) Scope Creep Management occurs when scope creep is introduced by technologists adding features not originally contemplated. It is developed by technologists for customer pleasing or technical gold-plating purposes where features are added to project (IT) by technologists causing scope creep.

Customer-pleasing scope creep occurs when the desire to please the customer through additional product features adds more work to the current project rather than to a new project proposal — it results from an organization and/or individual whose ultimate goal is to please the customer while acting reluctant to reject proposed changes.

Gold-plating scope creep occurs when technologists augment the original requirements because of a bias toward "technical perfectionism" or because the initial requirements were insufficiently clear or detailed. It is different and is a result of technologists adding substance or additions to original requirements because of lack of details in initial business requirements.

🔑 Definition — Customer-Pleasing Scope Creep: Scope creep driven by the desire to satisfy the customer by adding extra features to the current project rather than deferring them to a new project. 🔑 Definition — Gold-Plating Scope Creep: Scope creep caused by technologists adding extra features beyond original requirements due to technical perfectionism or unclear initial requirements.

26.4.2 Scope Management Plan

The Project Scope Management Plan documents how the project scope will be defined, managed, controlled, verified and communicated to the project team and stakeholders/customers. It also includes all work required to complete the project. The documents are used to control what is in and out of the scope of the project by the use of a Change Management system. Items deemed out of scope go directly through the change control process and are not automatically added to the project work items. The Project Scope Management Plan is included as one of the sections in the overall project management plan. It can be very detailed and formal or loosely framed and informal depending on the communication needs of the project.

🔑 Definition — Scope Management Plan: A formal document that describes how project scope will be defined, managed, controlled, verified, and communicated to stakeholders, and how scope changes will be processed through a change management system.

26.5 Project Scope Management

Project scope management consists of the processes used to identify all the work required to successfully complete the project. The five processes are:

• Initiation
• Scope Planning
• Scope Definition
• Scope Verification
• Scope Change Control

Product Scope refers to the features and functions that are to be included in a product or service. Successful completion of product scope is measured against the requirements. Project Scope refers to the work that must be done to deliver the product with specified features and functions. Successful completion of project scope is measured against the plan.

🔑 Definition — Product Scope: The features and functions to be included in a product or service, measured against requirements. 🔑 Definition — Project Scope: The work that must be done to deliver the product with specified features and functions, measured against the plan.

26.5.1 Scope Initiation

Scope initiation involves formal authority that a project exists and recognizing that it should continue its next phase. It includes: appointment of project team, introduction, needs identification, market research, opportunity studies, political input, tendering, project objectives and constraints, characteristics of objectives, strategic plan and objectives, constraints, project cost limit, performance measures, and additional input to project selection and initiation.

26.5.1.1 Project Charter

The project charter is the document that formally recognizes existence of a project. It refers to the business need the project is addressing. It describes the products to be delivered. It gives the project manager the authority to apply organizational resources to project activities.

🔑 Definition — Scope Initiation: The process of formally authorizing that a project exists and should continue to its next phase, including needs identification, market research, and defining project objectives and constraints.

26.5.2 Scope Planning

Scope planning is a written statement that includes: project justification, major deliverables, and project objectives. It refers to the criteria used to determine if the project or phase has been completed successfully. Scope planning is defining and managing the project scope influences the project's overall success. Each project requires a careful balance of tools, data sources, methodologies, processes and procedures, and other factors to ensure that the effort expended on scoping activities is commensurate with the project's size, complexity, and importance.

26.5.2.1 Scope Management Plan

The project scope management plan provides guidelines on how project scope will be defined, documented, verified, managed, and controlled by the project management team. The scope management plan describes:

• How scope changes will be identified and classified
• How scope changes will be integrated into the project
• Expected stability of the project

🔑 Definition — Scope Planning: The process of creating a written statement that includes project justification, major deliverables, and project objectives, defining criteria for successful completion.

26.5.3 Scope Definition

Scope definition is where we get down to detail. It provides the detailed information for the Scope Plan, often called the Scope Definition Document. It provides the basis for estimating cost, time and resources, performance measurement and responsibilities. Generally the scope definition document is presented in list format but development of the document requires some brainstorming activities that are best done with the key stakeholders and the project team involved.

26.5.3.1 Developing Preliminary and Detailed Project Scope Statement

The project scope statement is the definition of the project – what needs to be accomplished. The preliminary project scope statement is developed from the information provided by the initiator or sponsor. The project management team in the scope definition process further refines the preliminary project scope statement into the project scope statement. The project scope statement content will vary depending upon the application area and complexity of the project. During subsequent phases of multi-phase projects, the Preliminary Project Scope Statement process validates and refines, if required, the project scope defined for that phase.

The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverables, assumptions, and constraints that are documented during project initiation in the preliminary project scope statement. During planning, the project scope is defined and described with greater specificity because more information about the project is known.

Stakeholder needs, wants, and expectations are analyzed and converted into requirements. The assumptions and constraints are analyzed for completeness, with additional assumptions and constraints added as necessary. The project team and other stakeholders who have additional insight into the preliminary project scope statement can perform and prepare the analyses.

📌 Example: A project manager creates a preliminary scope statement from the sponsor's brief, listing major deliverables and constraints. During planning, the team interviews stakeholders, adds 15 new requirements, refines cost estimates from ±50% to ±10% accuracy, and updates the scope statement with detailed specifications, acceptance criteria, and exclusions.

Value of Sound Scope Statement: With a sound scope statement, one can clearly understand the project details, deliverables and its boundaries. Product description helps to explain and understand the details for accomplishing objectives. It is essential to be sensitive to customer's constraints, assumptions, budgetary restrictions as well as definite limitations. Thus, it is necessary to follow project scope to have concrete decision making ability during the project. As a result, the team involved begins to identify risks and issues that could cause any delay in the project. Also, any scope deviations must be communicated immediately to all stakeholders including customers.

26.5.3.2 Inputs to Defining Project Scope

The five inputs to defining project scope are:

1. Organizational Process Assets: Provide information about standards that the company has already set in place — standards that are likely to be applied to every project.
2. Project Charter: Authorizes the existence of the project and outlines the project objectives.
3. Preliminary Project Scope Statement: Provides a description of the major project deliverables, project objectives, project assumptions, project constraints, and a statement of work.
4. Project Scope Management Plan: Provides a description of how the stated project objectives will be developed within the detailed Project Scope Statement.
5. Approved Change Requests: Agreed-upon and documented amendments to project scope that will ultimately be added to the Project Scope Statement.

26.5.3.3 Outputs to Defining Project Scope

The project scope statement describes, in detail, the project's deliverables and the work required to create those deliverables. It provides a common understanding of the project scope among all project stakeholders, describes the project's major objectives, enables more detailed planning, guides execution, and provides the baseline for evaluating whether changes are inside or outside project boundaries.

1. Scope Statement: The degree and level of detail defines what work will be performed and what work is excluded. The detailed project scope statement includes:

   • Project Objectives: Measurable success criteria including business, cost, schedule, technical, and quality objectives.
   • Product Scope Description: Characteristics of the product, service, or result.
   • Project Requirements: Conditions or capabilities that must be met by deliverables.
   • Project Boundaries: What is included and explicitly what is excluded.
   • Project Deliverables: Outputs comprising the product/service and ancillary results.
   • Product Acceptance Criteria: Process and criteria for accepting completed products.
   • Project Constraints: Specific limitations on the team's options (budget, dates, contractual provisions).
   • Project Assumptions: Assumptions with potential impact if false.
   • Initial Project Organization: Project team members and stakeholders identified.
   • Initial Defined Risks: Known risks identified.
   • Schedule Milestones: Imposed dates identified by customer or performing organization.
   • Fund Limitation: Limitations on total value or time frames.
   • Cost Estimate: Expected overall cost with accuracy indication (conceptual or definitive).
   • Project Configuration Management Requirements: Level of configuration management and change control.
   • Project Specifications: Compliance documents.
   • Approval Requirements: Requirements for project objectives, deliverables, documents, and work.

2. Requested Changes: Changes to the project management plan processed through Integrated Change Control.

3. Project Scope Management Plan (Updates): Updated to include approved change requests.

🔑 Definition — Project Scope Statement: A detailed definition of the project that describes deliverables, work required, objectives, boundaries, constraints, assumptions, and acceptance criteria, providing a baseline for evaluating changes.

26.5.4 Scope Verification

Scope verification is carried out whenever one or more deliverables are ready to be handed over. It consists of obtaining the stakeholders' formal acceptance of the work completed. Verifying the project scope includes reviewing deliverables to ensure that each is completed satisfactorily. If the project is terminated early, the project scope verification process should establish and document the level and extent of completion. Scope verification differs from quality control in that scope verification is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with meeting the quality requirements specified for the deliverables. Quality control is generally performed before scope verification, but these two processes can be performed in parallel.

🔑 Definition — Scope Verification: The process of obtaining formal stakeholder acceptance of completed deliverables, focused on acceptance rather than quality compliance.

26.5.5 Scope Change Control

The scope changes that usually cause problems are those where the perception of what was in and out of scope was different between various parties. The scope management section of the project plan is a formalized document that captures the processes for handling Scope Changes. The last output of scope management is that of "Scope Control". The project manager should implement a process to ensure the project's goals and objectives will be monitored throughout the project.

The project manager must be made aware of any discrepancies of project activities or potential risks promptly that deviate from the baseline or work breakdown schedule, in order to minimize any delays to the schedule which can ultimately cause project failure. It is the project manager's responsibility to provide guidance for any corrective action and means of communications to all team members involved.

Project scope control is concerned with influencing the factors that create project scope changes and controlling the impact of those changes. Scope control assures all requested changes and recommended corrective actions are processed through the project Integrated Change Control process. Project scope control is also used to manage the actual changes when they occur and is integrated with the other control processes. Uncontrolled changes are often referred to as project scope creep.

There are two distinct ways to separate scope creep management: business scope creep and features (technology) scope creep. Business scope creep management occurs when decisions made with reference to a project are designed to solve or meet the requirements and needs of the business. Business scope creep changes may be a result of poor requirements definition early in development, or the failure to include the users of the project until the later stage of the systems development life cycle.

If the approved change requests have an effect upon the project scope, then the project scope statement is revised and reissued to reflect the approved changes. The updated project scope statement becomes the new project scope baseline for future changes.

Scope Approval: The scope management plan is a formal document that explains how the project scope will be managed and how scope changes will be factored into the project plan. Once the scope is developed, the elements are thoroughly discussed and agreed on by the project team, stakeholders, sponsors and customers. Then scope definition is signed-off formally and the changes are discussed thoroughly by the project manager. With "acceptance/signed scope approval", the project manager responds to ensure complete and monitored processing, and customers are notified for every change to avoid project creep and risks.

🔑 Definition — Scope Change Control: The process of influencing factors that create scope changes, controlling their impact, and processing all changes through Integrated Change Control to prevent uncontrolled scope creep.

⭐ Key Takeaways

The most critical concept from this lecture is that scope defines what the project contains or delivers, and it must be explicitly distinguished from goals and objectives which explain WHY the project exists. Scope creep — uncontrolled expansion of project scope without corresponding increases in resources, schedule, or budget — is a major risk that typically causes cost overruns and must be managed through formal change control processes. The five processes of project scope management (initiation, planning, definition, verification, and change control) provide a systematic framework for ensuring all required work is identified and controlled. Students must understand the critical difference between product scope (features/functions measured against requirements) and project scope (work measured against the plan), as well as the components of a detailed project scope statement including objectives, boundaries, deliverables, constraints, and assumptions. Finally, recognizing that scope verification focuses on stakeholder acceptance while quality control focuses on meeting quality requirements is essential for proper project execution.

🧠 Quick Revision Questions

1. What is the difference between scope, objectives, and goals, and why is it important to explicitly identify items "out of scope"?

2. How does scope creep typically occur, and what are the three specific types of scope creep discussed in the lecture (features/technology, customer-pleasing, and gold-plating)?

3. What are the five processes of project scope management, and what is the primary purpose of each process?

4. What are the five inputs required for defining project scope, and what are the three key outputs produced from this process?

5. How does scope verification differ from quality control, and why is it important to distinguish between product scope and project scope when measuring success?

📘 Lecture 27 — Project Scope Management

📖 Overview: This lecture introduces the concept of scope in project management, distinguishing between product scope and project scope. It details the complete process of project scope management, which is essential for defining and controlling what is and is not included in a project to ensure successful completion.

🗂️ Topics Covered

The lecture covers the definition of scope, including product scope and project scope, followed by a detailed exploration of the project scope management process. This process includes initiation, scope planning, scope definition (with a focus on the Work Breakdown Structure), scope verification, and scope change control, along with their respective sub-processes and models.

📝 Lecture Summary

27.1 Scope:

The term “scope” encompasses two distinct but related concepts. Product scope refers to the work required to deliver a project’s product or service with specific features and functions; the result can be a single product or several components. The features, functions, and characteristics to be included in a product are measured against set product requirements and are managed throughout the lifecycle. Project scope, in contrast, refers to the work that must be done to deliver a product, service, or result with specified features and functions. Project scope has a start and end date, possesses unique characteristics or attributes, and produces specific results during the lifecycle.

27.2 Project Scope Management:

Scope management is concerned with defining and controlling the scope of a project. It includes product description, any known constraints and assumptions. Project scope is defined in the project charter. It serves as a basis for the development of the Work Breakdown Structure (WBS). It must be verified and controlled throughout the life of the project. Project scope management includes the processes required to ensure that the project includes all the work required to complete the project successfully. It is primarily concerned with defining and controlling what is or is not included in the project.

The scope management process comprises of the following:

• Project initiation: Approve Business case, feasibility, budget
• Scope planning: Gather requirements
• Scope definition: Create scope components, scope divide work
• Scope verification: Get approval from all stakeholders
• Scope change control: Manage scope change requests

27.2.1 Initiation Phase:

As described in the previous lecture, it is the process of formally recognizing that a new project exists or that an existing project should continue into its next phase.

27.2.2 Project Scope Planning:

It refers to creating a project scope management plan that documents how project scope will be defined, verified, controlled and how the Work Breakdown Structure (WBS) will be created and defined. It is the process of developing a written scope statement as the basis for future project decisions including, in particular, the criteria used to determine if the project phase is completed successfully.

27.2.2.1 Applying the Process Model:

1. Define Scope: It is always essential to know what the goals of the project are. This needs to be defined in exact and quantitative terms: what the project is supposed to achieve and what it is not supposed to achieve. This is achieved through the definition and management of the project scope.
2. Identify Project Environment and Characteristics: Identify what processes are already in place. Consider if the process is fundamental to achieving the organization’s goals, if there is high risk involved in the business, what the problem areas are, what type of organizational culture exists (is it easily adaptable or adverse to change), and finally, identify what the requirements are.
3. Solicit Inputs: The requirements for the project are a major driver. The affected parties should be involved in the process. These people ensure resulting processes are: a) Feasible/useful, and b) Possible, including feedback from previous projects.
4. Select Processes, Activities and Tasks: Identify and prioritize processes or parts of processes within the standards that will be implemented. It is useful to include “mapping current processes” practices and/or methods to processes, activities, and tasks. Mapping must be used to verify and to identify gaps between the current situation and target situation.
5. Document Decisions and Rationale: Document refers to the mapping of defined processes, activities, and tasks to determine relationships and reasons for adopting this approach. This document should be included in the “Project Management Plan”.

27.2.3 Project Scope Definition:

This involves subdividing major project deliverables (as identified in the scope statement) into smaller, more manageable components. The benefit of scope definition is to improve the accuracy of estimated cost, time, and resources. The baseline for performance, measurement, and control is defined. It facilitates clear responsibility and assignments.

27.2.3.1 Work Breakdown Structure (WBS):

A deliverable-oriented grouping of project elements that organizes and defines the scope of the project. Work not in the Work Breakdown Structure (WBS) is outside the scope of the project. As with the scope statement, the WBS is often used to develop or confirm a common understanding of project scope. Each descending level represents an increasingly detailed description of project elements. A WBS is normally presented in chart form. Each item in it is generally assigned a unique identifier often known collectively as a “code of accounts”. Items at the lowest level of the WBS are known as work packages.

🔑 Definition — Work Breakdown Structure (WBS): A deliverable-oriented grouping of project elements that organizes and defines the total scope of the project. Work not in the WBS is outside the project scope. 📌 Example: A WBS for building a house might have top-level deliverables like "Foundation," "Framing," and "Electrical." The "Framing" deliverable would be subdivided into lower levels like "Walls," "Roof," and "Floors." Each of these items would be assigned a unique code, and the lowest level items (e.g., "Install drywall for walls") would be the work packages.

27.2.4 Scope Verification:

It is the process of formalizing acceptance of the project scope by stakeholders (sponsor, client, customer, etc.).

27.2.4.1 Formal Acceptance:

It is the documentation of the product, project, or phase acceptance by the client and/or sponsor. It must be prepared and distributed. Such acceptance must be conditional, especially at the end of every phase.

27.2.5 Scope Change Control:

It defines procedures by which project scope must be changed. It includes paperwork, tracking systems, and approval levels necessary for authorizing changes. The scope change control system should be integrated with the overall change control system, and in particular, with any system in place to control product scope. Scope change control is concerned with: a) Influencing factors which create scope changes to ensure that changes are beneficial, b) Determining that a scope change has occurred, and c) Managing the actual changes when and if they occur. 💡 Why this matters: Uncontrolled changes to scope, often called "scope creep," are a major cause of project failure. A formal change control process is critical for managing budgets, schedules, and stakeholder expectations.

⭐ Key Takeaways

The lecture establishes a critical distinction between product scope (features/functions) and project scope (work to deliver them). The five-step scope management process (Initiation, Planning, Definition, Verification, Change Control) provides a complete framework for managing scope. The Work Breakdown Structure (WBS) is a fundamental tool for defining and organizing all project work, with deliverables at the lowest level called work packages. Scope verification focuses on formal stakeholder acceptance, while scope change control provides a disciplined process for managing any alterations to the project's baseline. A key insight is that the cost and difficulty of making a scope change increase significantly as the project progresses.

🧠 Quick Revision Questions

1. What is the key difference between product scope and project scope?
2. List the five main processes that comprise project scope management.
3. What is a Work Breakdown Structure (WBS), and what are its components called at the lowest level?
4. What is the primary goal of the scope verification process?
5. What are the three main concerns of scope change control?

📘 Lecture 28 — Network Scheduling Techniques

📖 Overview: This lecture introduces network scheduling techniques as essential tools for modern project management, covering historical evolution from Gantt charts to PERT and CPM. It explains how these techniques provide visibility, control, and the ability to handle uncertainties in complex projects, while also addressing their limitations and practical applications.

🗂️ Topics Covered

The lecture covers the introduction and benefits of scheduling techniques, historical evolution of network scheduling including PERT's development for the Polaris missile system and CPM's origins at DuPont. It explains network fundamentals and terminology including events, activities, and critical paths, the differences between PERT and CPM, Graphical Evaluation and Review Techniques (GERT), dependencies or interrelationships including dummy activities, and slack time analysis.

📝 Lecture Summary

28.1 Introduction

In today’s highly competitive environment, management seeks new control techniques to cope with complexities, masses of data, and tight deadlines. Since World War II, scheduling techniques have become paramount. Common techniques include Gantt or bar charts, Milestone charts, Line of balance, and Networks such as Program Evaluation and Review Technique (PERT), Arrow Diagram Method (ADM) also called Critical Path Method (CPM), Precedence Diagram Method (PDM), and Graphical Evaluation and Review Technique (GERT).

28.2 Benefits and Advantages of Scheduling

The Program Evaluation and Review Technique (PERT) is perhaps the best known of all relatively new techniques. PERT forms the basis for all planning and predicting, enabling management to plan and make best possible use of resources within time and cost limitations. It provides visibility and enables management to control "one-of-a-kind" programs as opposed to repetitive situations. PERT helps management handle uncertainties by answering questions about how time delays influence program completion, where slack exists, and what elements are crucial to meet completion dates. It provides a basis for decision making, utilizes time network analysis to determine manpower, material, and capital requirements, reveals interdependencies of activities, facilitates "what if" exercises, identifies the longest path or critical paths, and allows scheduling risk analysis. These benefits apply to all network scheduling techniques, not just PERT.

28.3 Historical Evolution of Networks

PERT was originally developed in 1958 and 1959 to meet the needs of the "age of massive engineering." The Special Projects Office of the U.S. Navy, concerned with performance trends on large military development programs, introduced PERT on its Polaris Weapon System in 1958, developed with the management consulting firm of Booz, Allen, and Hamilton. At about the same time, the DuPont Company initiated a similar technique known as the Critical Path Method (CPM), particularly concentrated in construction and process industries.

The basic requirements of PERT/time established by the Navy in the early 1960s included: all individual tasks must be visualized in a network comprising events and activities following the work breakdown structure; events and activities must be sequenced under a highly logical set of ground rules allowing determination of critical and sub-critical paths; time estimates must be made on a three-way basis (optimistic, most likely, and pessimistic); and critical path and slack times must be computed, where the critical path is that sequence of activities and events requiring the greatest expected time.

28.3.1 Advantages of PERT: A major advantage is the kind of planning required to develop a major network, which reveals interdependencies and problem areas not obvious with other methods. PERT allows determining the probability of meeting specified deadlines through alternative plans. A third advantage is the ability to evaluate the effect of changes in the program, such as shifting resources from less critical activities to probable bottlenecks. PERT can also evaluate the effect of deviations in actual time required for an activity from predictions. Finally, PERT allows sophisticated data to be presented in a well-organized diagram for joint decision-making by contractor and customer.

However, PERT has disadvantages including complexity, extensive data requirements, and expense to maintain, making it most useful on large, complex programs. The PERT/LOB procedures can cut project costs, reduce time scales, coordinate planning, eliminate idle time, provide better scheduling of subcontractor activities, and develop better troubleshooting procedures. Before accepting a PERT system, management must perform a trade-off study to determine if results are worth the cost.

28.3.2 Criticism of PERT: Criticism includes: time and labor intensive effort required; reduced upper-level management decision-making ability; lack of functional ownership in estimates; lack of historical data for time-cost estimates; assumption of unlimited resources may be inappropriate; and need for too much detail.

28.4 Network Fundamentals and Terminology

The major discrepancy with Gantt, milestone, or bubble charts is the inability to show interdependencies between events and activities. These interdependencies must be identified to develop a master plan. Interdependencies are shown through network construction, which provides valuable information for planning, integration of plans, time studies, scheduling, and resource management. The primary purpose of network planning is to eliminate the need for crisis management by providing a pictorial representation of the total program.

Management information obtained includes: interdependencies of activities, project completion time, impact of late starts, impact of early starts, trade-offs between resources and time, "what if" exercises, cost of a crash program, slippages in planning/performance, and evaluation of performance.

An event is defined as the starting or ending point for a group of activities, and an activity is the work required to proceed from one event to another. In PERT networks, circles represent events, and arrows represent activities. Numbers in circles signify specific events, and numbers over arrows specify time needed. Events can be burst points (one event leading to multiple activities) or sinks (multiple activities leading to one event), similar to "and gates" in logic diagrams.

Bar charts can be converted to milestone charts, and by defining relationships between events, a PERT chart can be constructed. PERT is a management planning and control tool, like a road map where all major elements (events) are identified with their interrelations. PERT charts are often constructed from back to front because end dates are often fixed.

🔑 Definition — Event: The starting or ending point for a group of activities.

🔑 Definition — Activity: The work required to proceed from one event or point in time to another.

PERT uses time as a common denominator to analyze time, cost, and performance. Construction of the network requires two inputs: selecting whether events represent start or completion (completions are generally preferred), and defining the sequence of events relating each to its immediate predecessor. Large projects can be converted into PERT networks by answering: what job immediately precedes this job, what immediately follows, and what jobs can be run concurrently.

The critical path is established by the longest time span through the total system of events. It is vital for successful control because: there is no slack time in any events on this path, so any slippage causes corresponding slippage in the end date; and management must focus on these events to improve the total program. PERT helps identify earliest possible dates for events or activities. For levels 1–3 of the Work Breakdown Structure (WBS), project managers focus on milestones and events; for levels 4–6, concerns are activities.

28.5 Differences Between PERT and CPM

PERT and CPM share the same nomenclature and are often called arrow diagramming methods or activity-on-arrow networks. Differences include: PERT uses three time estimates (optimistic, most likely, pessimistic) with an expected time derived, while CPM uses one time estimate representing normal time. PERT is probabilistic based on a beta distribution for each activity time and a normal distribution for expected duration, allowing calculation of risk; CPM is deterministic based on a single time estimate. Both permit dummy activities. PERT is used for Research and Development projects where risks in time durations have high variability; CPM is used for construction projects that are resource dependent. PERT is used where percent complete is almost impossible to determine except at completed milestones; CPM is used where percent complete can be determined with reasonable accuracy.

28.6 Graphical Evaluation And Review Technique (GERT)

Graphical Evaluation and Review Techniques (GERT) are similar to PERT but allow for looping, branching, and multiple project end results. With PERT, one cannot easily show that if a test fails, it may need to be repeated several times, or that based on test results, one of several different branches can be selected to continue the project. These problems are easily overcome using GERT.

28.7 Dependencies or Interrelationships

There are three basic types of interrelationships or dependencies:

1. Mandatory Dependencies (Hard Logic): Dependencies that cannot change, such as erecting walls before putting up the roof.

2. Discretionary Dependencies (Soft Logic): Dependencies at the discretion of the project manager that may change from project to project. For example, one does not need to complete the entire bill of materials prior to beginning procurement.

3. External Dependencies: Dependencies beyond the control of the project manager, such as having contractors sit on the critical path.

28.7.1 Dummy Activities: It is sometimes impossible to draw network dependencies without including dummy activities. Dummy activities are artificial activities represented by a dotted line, do not consume resources or require time, and are added simply to complete the logic. For example, a dummy activity is required to show that activity D is preceded by activities A and B.

28.8 Slack Time

Since only one path through the network is longest, other paths must be shorter. Therefore, some events and activities can be completed before they are actually needed. The time differential between the scheduled completion date and the required date to meet the critical path is referred to as slack time. For example, if going from event 2 to event 5 on the critical path requires seven weeks while an alternative route requires only four weeks, then an event that requires two weeks for completion should begin anywhere from zero to three weeks after the preceding event completes. During this slack time, management might find another use for resources.

💡 Why this matters: The critical path is vital for resource scheduling and allocation because the project manager can reschedule events not on the critical path for accomplishment during other time periods when maximum utilization of resources can be achieved, provided the critical path time is not extended. This type of rescheduling through slack times provides better balance of resources throughout the company and may reduce project costs by eliminating idle or waiting time.

⭐ Key Takeaways

Network scheduling techniques, particularly PERT and CPM, transform project management by providing visibility into interdependencies and identifying the critical path that determines project duration. PERT uses probabilistic three-time estimates and is best suited for R&D projects with high uncertainty, while CPM uses deterministic single-time estimates for construction projects. The critical path concept is essential because any delay on this path directly extends project completion, while slack time on non-critical paths offers flexibility for resource optimization. Dummy activities maintain logical relationships without consuming resources, and GERT extends PERT capabilities by allowing looping and branching. Understanding these techniques enables managers to perform "what if" analyses, evaluate trade-offs between time and resources, and make informed decisions about schedule compression and resource allocation.

🧠 Quick Revision Questions

1. What are the three types of time estimates used in PERT, and how do they differ from the single estimate used in CPM?
2. Define the critical path and explain why it is crucial for project control according to the two key points mentioned in the lecture.
3. What is slack time, and how can project managers use it to optimize resource allocation?
4. What is the purpose of a dummy activity in network scheduling, and what does its representation look like?
5. How does GERT differ from PERT in terms of handling project uncertainties and branching?

📘 Lecture 29 — Network Scheduling Techniques

📖 Overview: This lecture focuses on slack (float) time in project networks — how to calculate it, identify it, and use it for effective project control. It also covers network re-planning techniques, including resource leveling and allocation, which are essential for adjusting schedules when the unexpected occurs during project execution.

🗂️ Topics Covered

The lecture covers four main areas: Slack Terminology defining TE and TL and the slack formula; Slack Time Calculation with forward and backward passes through a PERT network; Slack Identification as an early warning system for project managers including negative slack causes; and Network Re-planning discussing techniques like resource leveling, resource allocation, parallelization, and methods for reducing project time.

📝 Lecture Summary

29.1 Slack Terminology

Slack is defined as the difference between the latest allowable date and the earliest expected date for an event in a project network. Two key terms are used: TE = the earliest time (date) on which an event can be expected to take place, and TL = the latest date on which an event can take place without extending the completion date of the project. The formula for slack is straightforward.

🔑 Definition — Slack Time: The amount of time an activity or event can be delayed without affecting the project completion date. 📐 Formula: Slack time = TL – TE 📌 Example: For event 1 in Figure 29.1, TE = 0 and TL = 0, so slack = 0 – 0 = 0. This is the reference point. For event 3, TE = 2 weeks and TL = 5 weeks, giving a slack of 5 – 2 = 3 weeks.

29.2 Slack Time Calculation

The calculation for slack time is performed for each event in the network by identifying the earliest expected date and the latest starting date. Events on the critical path have no slack (i.e., TL = TE) and provide boundaries for non-critical path events. The earliest time for an event not on the critical path assumes starting as early as possible, while the latest allowable date is found by working backward.

For complex networks containing multiple paths, the earliest starting dates must be found by proceeding from start to finish through the network (forward pass), while the latest allowable starting date must be calculated by working backward from finish to start (backward pass).

The importance of knowing exactly where slack exists cannot be overstated — Donald Marquis observed that companies making proper use of slack time were 30 percent more successful than average in completing technical requirements. PERT charts can be reconstructed with time scales, requiring a decision on whether to use early or late time requirements for slack variables.

To make full use of PERT/CPM capabilities, four values are identified: ES (earliest start), EF (earliest finish), LS (latest start), and LF (latest finish). The earliest starting time of a successor activity is the latest of the earliest finish dates of its predecessors. The latest finishing time for an activity entering a node is the earliest finishing time of the activities exiting that node.

29.3 Slack Identification

The identification of slack time can function as an early warning system for the project manager. If total slack time begins to decrease from one reporting period to the next, this could indicate that work is taking longer than anticipated or that more highly skilled labor is needed — a new critical path could be forming.

Negative slack (or negative float) occurs when work units show a negative value after subtracting the earliest start from the latest start. This typically happens when performing a backward pass from the customer's end date milestone, not where the forward pass ends. If the forward pass extends beyond the customer's end date (position 4 in Figure 29.5), negative slack is created.

💡 Why this matters: Negative slack is an early warning indicator that corrective action is needed to maintain the customer's end date.

Negative slack most likely results when: the original plan was highly optimistic but unrealistic; the customer's end date was unrealistic; one or more activities slipped during project execution; assigned resources did not possess correct skill levels; or required resources would not be available until a later date.

29.4 Network Re-planning

Much iteration is normally made during the planning phase before the PERT/CPM chart is finished. Slack times form the basis from which additional iterations, or network replanning, can be performed. This is done either at program conception to reduce the length of the critical path, or during the program should the unexpected occur.

29.4.1 Network Replanning Techniques

Two network replanning techniques are based almost entirely upon resources: resource leveling and resource allocation.

• Resource leveling is an attempt to eliminate manpower peaks and valleys by smoothing out period-to-period resource requirements. The ideal situation is to do this without changing the end date, though in reality, the end date moves out and additional costs are incurred.
• Resource allocation is an attempt to find the shortest possible critical path based upon available or fixed resources. The problem is that employees may not be qualified technically to perform on more than one activity in a network.

Several other methods for reducing expected project time include: elimination of some parts of the project; addition of more resources; substitution of less time-consuming components or activities; parallelization of activities; shortening critical path activities, early activities, longest activities, easiest activities, or activities least costly to speed up; shortening activities for which you have more resources; and increasing work hours per day.

Parallelization involves accepting a risk by assuming a certain event can begin in parallel with a second event that would normally be in sequence. For example, four weeks can be saved by sending out purchase orders after contract negotiations but before signing the contract. This risk is normally overcome by issuing a long-lead procurement letter immediately following contract negotiations.

Two other common risk types: (1) manufacturing must order tooling before engineering finishes the prototype, and engineering may design the prototype to fit the tooling; (2) a subcontractor may work without completed blueprints, and blueprints are later changed to represent the as-built end-item.

For large programs, it is often better to have each department develop its own PERT/CPM networks based on the work breakdown structure, then integrate them into one master chart to identify total program critical paths. Segmented PERT charts can also be used when multiple contractors work on the same program — the prime contractor integrates all subcontractors' PERT charts.

⭐ Key Takeaways

Slack (float) is the difference between latest and earliest event times (TL – TE), and events on the critical path have zero slack. Slack time calculation requires both forward passes (left to right) and backward passes (right to left) through the network. Negative slack occurs when forward pass work extends beyond the customer's end date, serving as a critical early warning signal. Network re-planning uses resource leveling (smoothing peaks) and resource allocation (shortest path with fixed resources), plus methods like parallelization and activity shortening. For complex programs, individual department PERT charts are integrated into a master chart to identify total program critical paths.

🧠 Quick Revision Questions

1. What is the formula for calculating slack time, and what do TE and TL represent?
2. How do you identify which events are on the critical path in terms of their slack?
3. What causes negative slack, and why is it considered an early warning indicator?
4. What is the difference between resource leveling and resource allocation in network re-planning?
5. When parallelizing activities, what risk does the contractor incur, and how is it typically managed?

📘 Lecture 30 — NETWORK SCHEDULING TECHNIQUES

📖 Overview: This lecture examines the methodologies for estimating activity times and total program times in network scheduling. It covers the full PERT/CPM planning process, crash time analysis for cost-time trade-offs, common problem areas in implementing these techniques, and alternative PERT/CPM models. Understanding these concepts is crucial for effective project scheduling, resource allocation, and cost control.

🗂️ Topics Covered

The lecture covers estimating activity time using three-point estimates (optimistic, pessimistic, most likely) and the beta distribution; calculating total program time using standard deviation and variance; the six-step total PERT/CPM planning process; crash time analysis in CPM for cost-time trade-offs; common problem areas in PERT/CPM including human factors, cost control, and historical data limitations; and alternative models such as PERT/cost and PERT/performance.

📝 Lecture Summary

30.1 Estimating Activity Time:

To determine elapsed time between events, functional managers must evaluate the situation and submit their best estimates based on historical data. For non-repetitive activities, managers submit estimates using three possible completion assumptions. The most optimistic completion time assumes everything goes according to plan with minimal difficulties, occurring approximately 1 percent of the time. The most pessimistic completion time assumes maximum potential difficulties will develop, also occurring approximately 1 percent of the time. The most likely completion time is what would most often occur if the effort were repeated over and over again.

Two assumptions must be made before combining these three times into a single expression for expected time. First, the standard deviation (σ) is one-sixth of the time requirement range, based on probability theory where endpoints are three standard deviations from the mean. Second, the probability distribution of time required for an activity must be expressible as a beta distribution.

🔑 Definition — Expected Time (te): The weighted average time for completing an activity, calculated from optimistic, pessimistic, and most likely time estimates. 📐 Formula: te = (a + 4m + b) / 6 where a = most optimistic time, b = most pessimistic time, and m = most likely time 📌 Example: If a = 3, b = 7, and m = 5 weeks, then te = (3 + 4(5) + 7) / 6 = (3 + 20 + 7) / 6 = 30/6 = 5 weeks. This becomes the activity time in the PERT chart. If a = 2, b = 12, and m = 4 weeks, te = (2 + 16 + 12) / 6 = 30/6 = 5 weeks, but with higher uncertainty due to wider spread between optimistic and pessimistic times.

💡 Why this matters: The three-point estimate method accounts for uncertainty in non-repetitive activities, but managers must carefully evaluate risks since different combinations of a, b, and m can yield the same te with vastly different levels of uncertainty.

30.2 Estimating Total Program Time:

To calculate the probability of completing the project on time, the standard deviations of each activity must be known. The variance (σ²) is the square of the standard deviation and is primarily useful for comparison to expected values. The total path standard deviation is calculated by the square root of the sum of the squares of the activity standard deviations.

🔑 Definition — Variance (σ²): The square of the standard deviation, used for comparing to expected values in project time analysis. 📐 Formula for standard deviation: σ = (b - a) / 6 where b = pessimistic time and a = optimistic time 📐 Formula for total path standard deviation: σ(total) = √(σ₁² + σ₂² + σ₃² + ... + σn²) 📌 Example: From Figure 30.1, the critical path of Figure 29.1 shows activity times with their corresponding standard deviations. The total path standard deviation is calculated by taking the square root of the sum of squares of individual activity standard deviations along the critical path.

30.3 Total PERT/CPM Planning:

PERT scheduling is a six-step process. Steps one and two: The project manager lays out a list of activities and places them in order of precedence, creating logic charts (also called arrow diagrams, work flow, or networks). These diagrams look like networks but without activity times or critical paths identified.

Step three: Review the arrow diagrams with line managers (the true experts) to ensure correct activity identification and interrelationships. Step four: The functional manager converts the arrow diagram to a PERT chart by identifying time duration for each activity, based on the assumption of unlimited resources since calendar dates are not yet defined.

Step five: The first iteration on the critical path examines whether critical calendar dates satisfy project requirements. If not, the project manager must shorten the critical path by asking line managers to take the "fat" out of their estimates. Step six (often most overlooked): The project manager places calendar dates on each event, converting from unlimited resource planning to limited resource planning. If line managers cannot commit to calendar dates, replanning is necessary.

PERT re-planning should be an ongoing function during project execution. Primary objectives on a schedule are: best time, least cost, and least risk. Secondary objectives include studying alternatives, optimum schedules, effective use of resources, communications, refinement of estimating, ease of project control, and ease of time or cost revisions. These objectives are limited by constraints such as calendar completion, cash flow restrictions, limited resources, and management approvals.

30.4 Crash Times:

The basic difference between PERT and CPM lies in the ability to calculate percent complete. PERT is used in Research and Development or development activities where percent-complete determination is almost impossible, making PERT event oriented rather than activity oriented. Funding is normally provided for each milestone achieved. CPM is activity oriented because in construction-type activities, percent complete along the activity line can be determined.

Crashing involves speeding up project phases. Requirements for CPM crashing include: (1) emphasis on activities, not events; (2) consideration of both time and cost for each activity; and (3) considering only critical path activities, starting with those having the lowest crashing cost per unit time.

🔑 Definition — Crashing: The process of speeding up project activities by adding resources, typically at increased cost, to reduce total project duration. 📌 Example: In Figure 30.2, activity A (on critical path) has a weekly crashing cost of $2,000 per week for maximum 2 weeks. Activity C has lower crashing cost but is not on critical path, so it is not considered first. After A, activity F at $3,000 per week for maximum 3 weeks is considered. Total crashing from base $120,000 to $157,500 reduces time from 23 weeks to 15 weeks (Figure 30.3). Crashing non-critical path elements would cost $7,500 without reducing total project time.

💡 Why this matters: As each activity is crashed, a new critical path may develop. The purpose of balancing time and cost is to avoid wasteful resource use. Direct and indirect costs create a region of feasible budgets (Figure 30.4), bounded by early-start (crash) and late-start (normal) activities. CPM also contains the concept of slack time — the maximum time a job may be delayed beyond its early start without delaying project completion (Figure 30.6).

30.5 PERT/CPM Problem Areas:

PERT/CPM models have several disadvantages and problems. PERT is end-item oriented, making it difficult for many companies to incorporate. Upper-level managers may feel PERT/CPM removes their power and decision-making ability, especially when forced to accept it as part of contractual requirements.

A distinct contrast exists between planners and doers. Planning is performed by the program office and functional management, but once the network is constructed, planners become observers relying on doers. Management must convince doers of their obligation toward successful completion. Unless the project is repetitive, there is usually a lack of historical information for cost estimates of optimistic, pessimistic, and most likely times. Problems can involve poor predictions for overhead costs, indirect costs, material and labor escalation factors, and crash costs.

PERT networks assume all activities start as soon as possible, assuming qualified personnel and equipment are available. Cost control presents problems because the project cost and control system may not be compatible with company fiscal planning policies. Many people expect too much from PERT-type networks. Subdividing work packages further by identifying all sub-activities (Figure 30.7) has the advantage of easy direct charge number identification, but the time and cost for this detail may be prohibitive. Managers must ensure the original purpose of identifying prime and supporting objectives is still met.

30.6 Alternative PERT/CPM Models:

Advantages of PERT/time include capabilities for: trade-off studies for resource control, contingency planning in early stages, visually tracking performance, demonstrating integrated planning, providing visibility down through work breakdown structure levels, providing regimented control structure, and increasing functional members' ability to relate to the total program.

However, PERT/time has proved ineffective in controlling resources in many situations. Three parameters are necessary for resource control: time, cost, and performance. Companies developed PERT/cost and PERT/performance models. PERT/cost is an extension of PERT/time that attempts to overcome problems with optimistic and pessimistic time estimates. It is a cost accounting network model based on the Work Breakdown Structure (WBS), capable of subdivision down to work packages. Advantages include containing all PERT/time features and permitting cost control at any WBS level. The primary reason for developing PERT/cost was so project managers could identify critical schedule slippages and cost overruns in time for corrective action.

Attempts to develop effective PERT/schedule models include the Accomplishment/Cost Procedure (ACP). However, development of PERT/schedule techniques is still in its infancy, and many companies feel locked in with their present control methods.

⭐ Key Takeaways

The expected time formula te = (a + 4m + b)/6 is fundamental for estimating activity durations using three-point estimates, but managers must recognize that different combinations of a, b, and m can produce the same te with vastly different uncertainty levels. The six-step PERT planning process progresses from activity identification through unlimited resource planning to limited resource scheduling with calendar dates — step six is the most commonly overlooked yet critical step. Crashing in CPM focuses only on critical path activities starting with the lowest cost per unit time, but crashing can create new critical paths that must be monitored. The fundamental difference between PERT (event-oriented, used in R&D) and CPM (activity-oriented, used in construction) lies in ability to calculate percent complete. PERT/cost was developed to overcome PERT/time's limitations in resource control by enabling identification of schedule slippages and cost overruns in time for corrective action.

🧠 Quick Revision Questions

1. What is the formula for expected time (te) and what does each variable represent?
2. How is the standard deviation of an activity calculated from optimistic and pessimistic times?
3. List the six steps of the total PERT/CPM planning process in order.
4. Why should only critical path activities be considered for crashing, and what caution must be observed when crashing?
5. What is the primary difference between PERT and CPM regarding percent complete, and what was the main reason for developing PERT/cost?

📘 Lecture 31 — PRICING AND ESTIMATION

📖 Overview: This lecture explores the critical intersection of pricing strategies and estimation techniques in project management. It covers computerized project management software, various types of cost estimates from order-of-magnitude to definitive estimates, and the structured pricing process that integrates the Work Breakdown Structure (WBS) with functional units. Understanding these concepts is essential for developing rational, competitive bids and effectively controlling project costs.

🗂️ Topics Covered

The lecture begins with an examination of computerized software packages and their capabilities, including precedence networks and activity constraints. It then covers the art and science of pricing and estimation, including cost estimating relationships. Two global pricing strategies (Type I and Type II acquisitions) are defined. The lecture details four main types of estimates: order-of-magnitude, approximate, definitive, and learning curves. Finally, it explains the pricing process, including the role of the Work Breakdown Structure and the vertical-horizontal interface between program and functional management.

📝 Lecture Summary

31.1 COMPUTERIZED SOFTWARE PACKAGES

There has been an explosion in project management software packages, with prices ranging from a few thousand dollars to $70,000. Computerized project management can answer questions about limited resources, changes in requirements, cash flow, overtime impact, and resource needs. Sophisticated packages can provide schedule and cost answers based on adverse weather, weekend activities, unleveled manpower requirements, variable crew size, splitting of activities, and assignment of unused resources.

Most software systems today use precedence networks, which are activity-on-node methods. The arrow represents the relationship or constraint between activities, while the work is accomplished during the activity.

🔑 Precedence relationships define the logical connections between activities:

• Finish-to-Start (FS): Activity 2 can start no earlier than the completion of activity 1.
• Start-to-Start (SS): Activity 2 cannot start prior to the start of activity 1.
• Finish-to-Finish (FF): Activity 2 cannot finish until activity 1 finishes.
• Percent-Complete Constraint: A specified percentage of one activity must be complete before the last percentage of another can start (e.g., the last 20% of activity 2 cannot start until 50% of activity 1 is completed).

📌 Example: In Figure 31.1 of the lecture, task 1 and task 2 are related by a solid line. Task 3 and task 4 can begin when task 2 is half finished. Dotted lines indicate slack, and the critical path can be identified with asterisks, different colors, or boldface type.

31.2 PRICING AND ESTIMATION

Many business managers consider pricing an art. While having intelligence on customer budgets and competitor pricing helps, such information is often unreliable. A disciplined approach to pricing helps develop a rational recommendation and documents assumptions for later analysis. Estimates are not blind luck; they are well-thought-out decisions based on the best available information.

Cost estimating relationships (CERs) are typically the output of cost models. Typical CERs include:

• Mathematical equations based on regression analysis
• Cost–quantity relationships such as learning curves
• Cost–cost relationships
• Cost–noncost relationships based on physical or performance characteristics

💡 Why this matters: A disciplined pricing process not only leads to more rational bids but also creates documentation that contributes to the learning experiences needed for effective future business decisions.

31.3 GLOBAL PRICING STRATEGIES

Two specific situations prevail in competitive project acquisitions:

• Type I Acquisition: A one-of-a-kind program with little or no follow-on potential.
• Type II Acquisition: An entry point to larger follow-on or repeat business, representing planned market penetration.

The objective for Type I is to win the program and execute it profitably. The objective for Type II is often to win and perform well, gaining a foothold in a new market, sometimes in place of profit.

Effective pricing begins long before proposal development. It starts with preliminary customer requirements, well-understood subtasks, and a top-down estimate with should-cost targets. This allows functional organizations to design a baseline to meet cost targets and gives management time to review and redirect the design before submission.

31.4 TYPES OF ESTIMATES

Projects can range from feasibility studies to complete construction. The desired estimate type and accuracy differ radically. The lecture defines four main types of estimates:

1. Order-of-Magnitude Analysis: Made without detailed engineering data, with an accuracy of ±35 percent. It uses past experience, scale factors, parametric curves, or capacity estimates (e.g., $/product unit, $/KW electricity).

2. Approximate Estimate (Top-Down Estimate): Also made without detailed engineering data, with an accuracy of ±15 percent. It is prorated from similar previous projects (estimating by analogy, parametric curves, rule of thumb, indexed cost).

3. Definitive Estimate (Grassroots Buildup Estimate): Prepared from well-defined engineering data (vendor quotes, complete plans, specifications, unit prices), with an accuracy of ±5 percent.

4. Learning Curves: Graphical representations of repetitive functions showing that continuous operations lead to a reduction in time, resources, and money.

Many companies standardize procedures with an estimating manual, which usually gives better estimates than industrial engineering standards because they include downtime, cleanup time, lunch, and breaks. Estimating manuals work best for repetitive or similar tasks.

For in-house projects, the type of estimate can vary over the project life cycle:

• Conceptual Stage: Venture guidance/feasibility (minimum-scope info)
• Planning Stage: Authorization of funds (preliminary design/scope)
• Main Stage: Detailed work
• Termination Stage: Re-estimation for major scope changes

31.5 PRICING PROCESS

This activity schedules the development of the Work Breakdown Structure (WBS) and provides management with two of the three operational tools for project control. The integration of the functional unit into the project environment occurs through the pricing-out of the WBS. The total program costs obtained by pricing out activities provide the third management tool.

The WBS and activity schedules are priced out through the lowest pricing units of the company. Costing information is rolled up from the task level to the project level and then to the total program level. Cost data must be analyzed for their potential impact on company resources (people, money, equipment, facilities). Proper analysis provides management with a strategic planning model for integrating the current program with others.

🔑 Vertical-Horizontal Interface: The pricing-out of the Work Breakdown Structure provides the basis for effective communication between functional management (vertical hierarchy) and program management (horizontal hierarchy), giving both parties one common goal. After pricing, the WBS continues to be a communications tool, documenting agreed performance and establishing criteria against which performance costs will be measured.

⭐ Key Takeaways

The lecture establishes that effective pricing and estimation for projects require a disciplined, structured approach rather than relying on intuition or unreliable intelligence. The choice of pricing strategy depends on whether the project is a one-time opportunity (Type I, profit-driven) or a market entry point (Type II, market-share-driven). Project managers must understand the four key types of estimates (order-of-magnitude, approximate, definitive, and learning curves), as each provides a different level of accuracy for different stages of a project. The pricing-out of the Work Breakdown Structure is the central mechanism for integrating functional and program management, turning the WBS into a vital communications and control tool. Finally, the pricing process is not a last-minute activity; it must begin early with preliminary requirements and cost targets to allow for effective design and decision-making.

🧠 Quick Revision Questions

1. What are the four types of precedence constraints used in computerized project management software, and how does each define the relationship between activities?
2. What is the fundamental difference between a Type I and a Type II pricing strategy, and what distinguishes the basis for determining the bid price in each?
3. Name the three main types of estimates discussed in the lecture and list their respective accuracy ranges (± percentages).
4. How does the pricing-out of the Work Breakdown Structure (WBS) serve to bridge the gap between functional management and program management?
5. What is a "cost estimating relationship" (CER), and what are four examples of typical CERs?

📘 Lecture 32 — Pricing and Estimation (Contd.)

📖 Overview: This lecture continues the discussion on pricing and estimation in project management, focusing on how organizations provide input for pricing, how labor distributions are managed, and how overhead costs are calculated and controlled. Understanding these processes is critical for accurate project budgeting, cost control, and competitive bidding.

🗂️ Topics Covered

The lecture covers three main areas: organizational input requirements for pricing, including the kickoff meeting and proposal timelines; labor distributions, detailing how man-hours are submitted, converted to dollars, and the dynamics between functional and program managers; and overhead rates, explaining how they are calculated, applied, and how they can impact project cost-effectiveness through examples and detailed elements of overhead expenses.

📝 Lecture Summary

32.1 Organizational Input Requirements:

Once the work breakdown structure and activity schedules are established, the program manager calls a meeting for all organizations required to submit pricing information. It is imperative that all pricing or labor-costing representatives be present for this "kickoff" meeting, where the work breakdown structure is described in depth so each pricing unit manager knows their responsibilities. The kickoff meeting also resolves power struggles between functional managers whose responsibilities may overlap, such as quality control during different program phases. One meeting is not always sufficient, so follow-up status meetings are held with concerned parties. Some companies have all members attend to keep everyone familiar with total effort and problems, while others have only a divisional representative attend to save time, though this can become a bottleneck if communication fails.

Time is extremely important during proposal activities. A Request for Proposal (RFP) often requires bids by a specific date, and the proposal manager's schedule has little flexibility. The RFP indirectly defines how much time pricing units have to identify and justify labor costs. Justification of labor costs may take longer than original estimates, especially without historical standards. Some proposals require comprehensive labor justification immediately, while others permit vendors to submit it later. Ultimately, it is the responsibility of the lowest pricing unit supervisors to maintain adequate standards for an immediate response to pricing requests.

🔑 Definition — Kickoff Meeting: The first meeting where the program manager describes the work breakdown structure to all pricing unit managers so they know their exact responsibilities. 📌 Example: Quality control activities: during Research & Development, research personnel perform their own quality control, but during production, the quality control department has overall responsibility.

32.2 Labor Distributions:

Functional units supply their input to the program office in the form of man-hours for each task, assuming the task is the lowest pricing element, and are time-phased per month. These man-hours are converted to dollars after multiplication by appropriate labor rates. Labor rates are generally known with certainty over twelve months but are estimates thereafter. If a company underestimates salary structures, increased costs and decreased profits occur; if overestimated, the company may not be competitive, or the salary structure becomes an item under contract negotiations for government-funded projects.

The development of labor rates for projection is based on historical costs in business base hours and dollars for the most recent month or quarter. Average hourly rates are determined for each labor unit by direct effort at the department level, including both highest-paid and lowest-paid employees, department manager, and clerical support. These base rates are then escalated as a percentage factor based on past experience, approved budget, local outlook, and similar industries.

Labor hours submitted by functional units are quite often overestimated for fear that management will "massage" and reduce them. Many times management reduces man-hours due to insufficient funding or to remain competitive, causing heated discussions between functional and program managers. The most common solution rests with the program manager: if they select team members knowledgeable in man-hour standards for each department, an atmosphere of trust can develop, allowing man-hours to be reduced in the company's best interests.

The man-hours submitted provide the basis for total program cost analysis and control. 📐 Formula: Labor Cost = Man-hours × Labor Rate 📌 Example 32.1: On May 15, Apex Manufacturing decided to bid for modifying an assembly line. A work breakdown structure was developed. On June 1, each pricing unit was given the WBS and schedule (Figure 32.2). All labor data must be submitted by June 15. During proposal activities, the proposal manager, pricing manager, and program manager must work together, though the program manager has the final say. After planning and pricing charts are approved by program team members and program managers, they are entered into an Electronic Data Processing (EDP) system. The computer prices hours using applicable department rates for preparing the direct budget time plan and estimate-at-completion reports. The direct budget time plan remains the same for the contract's life except for customer-directed changes or management-approved reductions (which cannot be increased without customer approval).

💡 Why this matters: Time plans are monthly mechanical printouts of all planned effort by work package and organizational element, serving as the data bank for status completion reports. Initially, the estimate-at-completion report is identical to the budget report, but changes throughout the program's life to reflect performance degradation or improvement.

32.3 Overhead Rates:

Controlling program costs involves more than tracking labor dollars and hours. Overhead dollars can be a major headache and must be tracked along with labor. Although most programs have an assistant program manager for cost who performs monthly overhead rate analysis, the program manager can increase program success by ensuring each team member understands overhead rates. For example, if overhead rates apply only to the first 40 hours of work, program dollars can be saved by performing work on overtime where the increased salary has a lower burden.

🔑 Definition — Overhead Rate: The indirect costs applied to direct labor, expressed as a percentage of direct labor dollars. 📐 Formula: Total Cost = (Labor Hours × Hourly Rate × Overtime Multiplier) × (100% + Overhead Burden %) 📌 Example 32.2: Apex Manufacturing needs 500 man-hours at $15.00/hour for a report. Regular shift overhead = 75%; overtime overhead = 5%. Overtime is paid at time and a half.

• Regular time: (500 hours × $15.00/hour) × (100% + 75%) = $13,125
• Overtime: (500 hours × $15.00/hour × 1.5) × (100% + 5%) = $11,812.50 The company saves $1,312.50 by performing work on overtime. This difference can be very large in manufacturing divisions with overhead rates between 300-450%.

Regardless of the project, all costs must have associated overhead rates. The preparation and assignment of overheads to each functional division is a science. While the total dollar pool for overhead rates is relatively constant, management decides how to distribute overhead among divisions. A company supporting Research & Development through competitive bidding may keep R&D overhead rates low, but other divisions may absorb additional costs and become uncompetitive.

The development of overhead rates depends on three elements: direct labor rates, direct business base projections, and projection of overhead expenses. Direct business base projection involves determining anticipated direct labor hours and dollars along with direct materials and other direct costs. Factors used include: actual costs to date and estimates to completion, proposal data, marketing intelligence, management goals, and past performance and trends.

Projection of overhead expenses is made by analyzing each element constituting overhead expense. A partial listing includes items from Table 32.1. Projection is based on: historical direct/indirect labor ratios, regression and correlation analysis, manpower requirements and turnover rates, changes in public laws, anticipated changes in company benefits, fixed costs in relation to capital asset requirements, changes in business base, Bid and proposal (B&P) tri-service agreements, and IR&D tri-service agreements. In aerospace and defense, the federal government funds a large percentage of B&P and IR&D activities to stimulate research and competition.

The annual budget is the prime factor in controlling overhead costs. This budget, resulting from CEO-established goals, is reviewed and approved at all management levels. It is established at the department level, and the department manager is responsible for identifying and controlling costs against the approved plan. Departmental budgets are summarized for higher management levels, who are made aware of authorized indirect budgets in their areas of responsibility.

💡 Why this matters: Monthly reports indicate current month and year-to-date budget, actuals, and variances for each management level. Analysis is made by the budget department through coordination with management. Each directorate's total organization is reviewed with the assigned budget analyst, and a joint meeting is held with directors and the vice president/general manager to review overhead performance.

⭐ Key Takeaways

This lecture emphasizes that accurate pricing and estimation require coordinated organizational input from kickoff meetings, careful management of labor distributions with realistic man-hour estimates, and thorough understanding of overhead rates to control total program costs. The critical skills include knowing how to calculate labor costs using appropriate rates, understanding when overtime can be cost-effective due to lower overhead burdens, and recognizing that overhead rate development involves analyzing direct labor rates, business base projections, and overhead expense elements. Students must remember that the program manager's ability to select knowledgeable team members can build trust and improve cost estimation, and that annual budgets and monthly variance reports are essential for overhead cost control.

🧠 Quick Revision Questions

1. What is the purpose of the kickoff meeting in organizational pricing, and what common problem does it resolve?
2. How are man-hours from functional units converted into dollar costs, and what challenge arises when predicting labor rates beyond twelve months?
3. In Example 32.2, why is overtime more cost-effective than regular time for the report, and what overhead rate difference makes this possible?
4. What are the three elements upon which overhead rate development depends, and what factors are used for direct business base projection?
5. How does the direct budget time plan differ from the estimate-at-completion report, and what conditions allow changes to the direct budget time plan?

📘 Lecture 33 — Pricing and Estimation (Contd.)

📖 Overview: This lecture continues the discussion on pricing and estimation in project management, focusing on the detailed processes for determining materials/support costs, pricing out work through a logical sequence, and system pricing approaches. It also covers developing backup costs, the complexities of the low-bidder dilemma, special problems in pricing, and common estimating pitfalls. Understanding these elements is crucial for creating accurate, credible cost proposals that support effective project control and organizational strategy.

🗂️ Topics Covered

This lecture covers materials and support costs, including their determination and flow; a thirteen-step logical sequence for pricing out work; the systems approach to pricing for resource control; development of supporting/backup costs with considerations for different contract types; challenges of the low-bidder dilemma; special problems related to cost billing methods; and a detailed list of estimating pitfalls that can undermine pricing accuracy.

📝 Lecture Summary

33.1 MATERIALS/SUPPORT COSTS

Three of four major pricing input requirements are fulfilled by the salary structure, overhead structure, and labor hours. The fourth major input is the cost for materials and support, which includes six subtopics: materials, purchased parts, subcontracts, freight, travel, and other. For small-dollar-volume programs, travel and freight are estimated directly. For large dollar-volume programs, travel is normally expressed as between 3 and 5 percent of the direct labor costs, and freight as between 3 and 5 percent of all costs for material, purchased parts, and subcontracts. The "other support costs" category may include computer hours or special consultants.

Determination of material costs is very time-consuming, more so than for labor hours. Material costs are submitted via a bill of materials that includes all vendors, projected costs throughout the program, scrap factors, and shelf lifetime for perishable products. Upon release of the work statement, work breakdown structure, and subdivided work description, the end-item bill of materials and manufacturing plans are prepared. End item materials are those identified as an integral part of the production end-item. Support materials are those required by engineering and operations to support the manufacture of end-items, identified on the manufacturing plan.

Furthermore, a procurement plan/purchase requisition is prepared as soon as possible after contract negotiations. This plan is used to monitor material acquisitions, forecast inventory levels, and identify material price variances. Manufacturing plans are used to prepare tool lists for manufacturing, quality assurance, and engineering. From these plans, a special tooling breakdown is prepared by tool engineering, defining tools to be procured and material requirements for in-house fabrication.

The materials/support costs are submitted by month for each program month. If long-lead funding of materials is anticipated, it must be applied to all materials/support costs. Some vendors may provide fixed prices over time periods in excess of twelve months. For example, Vendor Z may quote a firm-fixed price of $130.50 per unit for 650 units delivered over 18 months if the order is placed within 60 days.

🔑 Definition — Bill of Materials: A document that lists all materials, including vendors, projected costs, scrap factors, and shelf life required for a project. 📌 Example: Vendor Z offers a firm-fixed price of $130.50/unit for 650 units over 18 months if the order is placed within 60 days.

33.2 PRICING OUT THE WORK

Logical pricing techniques are available to obtain detailed estimates. The following thirteen steps provide a logical sequence to better control the company's limited resources:

Step 1: Provide a complete definition of the work. Step 2: Establish a logic network with checkpoints. Step 3: Develop the work breakdown structure. Step 4: Price out the work breakdown structure. Step 5: Review WBS costs with each functional manager. Step 6: Decide on the basic course of action. Step 7: Establish reasonable costs for each WBS element. Step 8: Review the base case costs with upper-level management. Step 9: Negotiate with functional managers for qualified personnel. Step 10: Develop the linear responsibility chart. Step 11: Develop the final detailed and PERT/CPM schedules. Step 12: Establish pricing cost summary reports. Step 13: Document the result in a program plan.

Although pricing is an iterative process, the project manager must develop cost summary reports at each iteration to enable key project decisions. Detailed pricing summaries are needed at least twice: in preparation for the pricing review meeting with management and at pricing termination. At other times, "simple cosmetic surgery" on previous cost summaries may suffice, such as adjustments to escalation factors and procurement costs.

Typical pricing reports include:

• A detailed cost breakdown for each WBS element, with cost summary sheets for each task and rollup sheets for each project and the total program.
• A total program manpower curve for each department, showing how each department has contracted to supply resources. "Peaks and valleys" may require schedule alterations for manpower smoothing.
• A monthly equivalent manpower cost summary, showing the fully burdened cost for the average departmental employee over the project period.
• A yearly cost distribution table, broken down by WBS element, showing yearly or quarterly costs; essentially a project cash-flow summary per activity.
• A functional cost and hour summary, providing top management with an overall description of hours and dollars per major functional unit, including indirect costs.
• A monthly labor hour and dollar expenditure forecast, including manpower termination liability information for premature project cancellation.
• A raw material and expenditure forecast, showing cash flow for raw materials based on vendor lead times, payment schedules, commitments, and termination liability.
• A total program termination liability per month table, showing the customer's monthly costs including termination liability for labor and raw materials.

These tables are used by project managers for cost control and by top-level management for selecting, approving, and prioritizing projects.

33.3 SYSTEMS PRICING

The basis of successful program management is establishing an accurate cost package from which all organization members can project and track costs. The cost data must be represented to achieve maximum allocation of corporate resources (people, money, and facilities).

The systems approach to pricing out activity schedules and the work breakdown structure provides unity within the company. The flow of information allows participation of all organization members, even part-time. Functional managers obtain a better understanding of how their labor fits into the total program and how their activities interface with other departments. For the first time, functional managers can accurately foresee how their activity leads to corporate profits.

The project pricing model (sometimes called a strategic project planning model) acts as a management information system, forming the basis for the systems approach to resource control. The summary sheets from the computer output provide management with data to select possible programs for maximum resource utilization. The strategic pricing model also allows management to perform perturbation analysis on base case costs, providing opportunity for design and evaluation of contingency plans.

🔑 Definition — Perturbation Analysis: An analysis performed on base case costs to evaluate the impact of changes and design contingency plans. 💡 Why this matters: Systems pricing ensures all parts of the organization are aligned and resources are allocated optimally.

33.4 DEVELOPING THE SUPPORTING/BACKUP COSTS

Not all cost proposals require backup support. For those that do, backup support should be developed along with pricing. Extreme caution must ensure that itemized prices are compatible with supporting data. Government pricing requirements are a special case.

Most supporting data come from external (subcontractor or outside vendor) quotes. Internal data must be based on historical data, which must be updated continually as each new project is completed. Supporting data should be traceable by itemized charge numbers. Customers may wish to audit the cost proposal, starting with supporting data. On sole-source proposals, it is not uncommon for supporting data to be audited before the final cost proposal is submitted.

The determining factor for requiring supporting data is usually the type of contract. On a fixed-price effort, the customer may not have the right to audit your books. For a cost-reimbursable package, your costs are an open book, and the customer usually compares your exact costs to the backup support.

Companies often have a choice of more than one estimate for backup support. In deciding which estimate to use, consider the possibility of follow-on work:

• If actual costs grossly exceed backup support estimates, you may lose credibility for follow-on work.
• If actual costs are less than backup costs, you must use the new actual costs on follow-on efforts.

The moral is that backup support costs provide future credibility. Well-documented, "livable" cost estimates may be included in the cost proposal even if not required.

Since both direct and indirect costs may be negotiated separately as part of a contract, supporting data (such as in Tables 33.1-33.4 and Figure 33.4) may be necessary to justify costs that differ from company or customer-approved standards. These tables include details on staff turnover data, staff experience profile, and total reimbursable manpower.

33.5 THE LOW-BIDDER DILEMMA

The price tag is critical to the proposal, but the question is what price will win the job. The decision process leading to the final price is highly complex with many uncertainties. While proposal managers may think a very low price helps, winning is only the beginning. Companies have short- and long-range objectives on profit, market penetration, and new product development that may be incompatible with a low-price strategy.

Considerations against a low-price strategy include:

• A suspiciously low price on cost-plus proposals might be perceived as unrealistic, affecting cost credibility or technical ability.
• The bid price may be unnecessarily low, eroding profits.
• The price may be irrelevant to the bid objective, such as entering a new market.
• Low pricing without market information is meaningless; price level is relative to competitive prices, customer budget, and the bidder's cost estimate.
• The bid proposal may cover only part of the total program; winning phase II depends on phase I performance and phase II price.
• Customer financial objectives may include total system life-cycle cost (LCC), design to unit production cost (DTUPC), or specific logistic support items.

Despite customer pressures toward low cost and fixed price, the lowest bidder is not an automatic winner. Both commercial and governmental customers are increasingly concerned about cost realism and the ability to perform under contract. A compliant, sound technical and management proposal based on past experience with realistic, well-documented cost figures is often chosen over the lowest bidder, who may project a risky image.

🔑 Definition — Cost Realism: The credibility and accuracy of a cost proposal, reflecting the bidder's ability to perform the work at the stated price.

33.6 SPECIAL PROBLEMS

Pricing must include an understanding of cost control, specifically how costs are billed back to the project. There are three possible billing situations:

1. Work priced at department average, charged at department average: This is the easiest method but encourages project managers to fight for the highest salary resources, since only average wages are billed.
2. Work priced at department average, billed at actual salary: This can create problems if only the best (highest-paid) employees are used, leading to cost overruns unless they work faster. Some companies are forced to use this by government agencies and may "inflate" direct labor hours to compensate.
3. Work priced at actual salary, billed at actual salary: This is the ideal situation, as long as the people can be identified during pricing.

Some companies use a combination of all three methods. The project office is often priced using the third method (because these people are identified early), while functional employees are priced using the first or second method.

33.7 ESTIMATING PITFALLS

Several pitfalls can impede the pricing function. The most serious is the "buy-in" decision, which is based on the assumption that there will be "bail-out" changes or follow-on contracts later. These may include spares, spare parts, maintenance, manuals, equipment surveillance, optional equipment, optional services, and scrap factors.

Other estimating pitfalls include:

• Misinterpretation of the statement of work
• Omissions or improperly defined scope
• Poorly defined or overly optimistic schedule
• Inaccurate work breakdown structure
• Applying improper skill levels to tasks
• Failure to account for risks
• Failure to understand or account for cost escalation and inflation
• Failure to use the correct estimating technique
• Failure to use forward pricing rates for overhead, general and administrative, and indirect costs

Unfortunately, many of these pitfalls do not become evident until detected by the cost control system, well into the project.

🔑 Definition — Buy-in Decision: A strategy of submitting a low price to win a contract, based on the assumption that future changes or follow-on contracts will cover the losses. 💡 Why this matters: Buy-in promises higher profits later but carries extreme risk if changes or follow-on work do not materialize.

⭐ Key Takeaways

The most critical concepts from this lecture are the structure and determination of materials/support costs, the logical thirteen-step sequence for pricing out work, and the importance of systems pricing for resource control. Students must understand the different billing methods for costs (department average vs. actual salary) and their impact on project budgets. The low-bidder dilemma highlights that credibility and cost realism are often more important than the lowest price. Finally, the extensive list of estimating pitfalls, especially the buy-in strategy, represents serious risks that can compromise project success and must be recognized and avoided.

🧠 Quick Revision Questions

1. What are the four major pricing input requirements, and which is the fourth one discussed in this lecture?
2. List the thirteen steps for logically pricing out the work.
3. What is the project pricing model also called, and what type of analysis does it allow management to perform on base case costs?
4. For what type of contract are costs considered an "open book" and subject to customer audit of backup support?
5. Name at least five of the nine estimating pitfalls that can impede the pricing function.

📘 Lecture 34 — Quality in Project Management

📖 Overview: This lecture introduces the concept of quality as a critical factor in project management and business success. It explores how quality is defined from multiple perspectives, examines its various dimensions, discusses its role in creating competitive advantage, and traces the evolution of quality management philosophies culminating in Total Quality Management (TQM). Understanding quality is essential because high quality reduces costs, increases productivity, generates customer satisfaction, and provides a sustainable competitive edge.

🗂️ Topics Covered

The lecture begins by examining the subjective and multifaceted nature of quality, presenting definitions from a historical business perspective. It then details six distinct perspectives on quality: judgmental, product-based, user-based, value-based, manufacturing-based, and an integrating customer-driven view. Following this, the eight principal quality dimensions are outlined. The concept of competitive advantage is explored through Porter's cost and differentiation frameworks. Finally, the lecture traces the evolution of quality in Japan and explains Total Quality Management (TQM) as a comprehensive management philosophy based on customer focus, participation, and continuous improvement.

📝 Lecture Summary

WHAT IS QUALITY?

Quality is not a new concept; in 1887, William Cooper Procter linked quality to productivity, cost, and profitability. Of these three determinants of profitability, quality is the most significant factor in determining the long-run success or failure of any organization. High quality goods and services provide a competitive edge, reduce costs from returns and rework, increase productivity and profits, and generate satisfied customers who provide continued patronage and word-of-mouth advertising.

Quality is a confusing and subjective concept because people view it from differing criteria based on their roles in the production-marketing value chain. A study of 86 firms produced several dozen different definitions, including perfection, consistency, eliminating waste, speed of delivery, compliance with policies, providing a usable product, doing it right the first time, delighting customers, and total customer satisfaction.

QUALITY FROM DIFFERENT PERSPECTIVES

Judgmental Perspective This view, first defined by Walter Shewhart in 1931, equates quality with superiority or excellence, known as the transcendent definition of quality. Under this view, quality is "both absolute and universally recognizable, a mark of uncompromising standards and high achievement." It cannot be defined precisely—"you just know it when you see it." This perspective is often linked to marketing efforts aimed at developing quality as an image variable.

🔑 Definition — Transcendent Quality: Quality as the "goodness of a product" which is synonymous with superiority or excellence, rising above ordinary limits. 📌 Example: Rolex watches and BMW and Lexus automobiles are attributed with this quality image.

Product-Based Perspective This definition views quality as a function of a specific, measurable variable, where differences in quality reflect differences in the quantity of some product attribute. This assessment implies that higher levels or amounts of product characteristics are equivalent to higher quality.

🔑 Definition — Product-Based Quality: Quality determined by the quantity of a measurable product attribute. 📌 Example: The number of stitches per inch on a shirt or the number of cylinders in an engine are measurable attributes that influence perceived quality.

User-Based Perspective This definition is based on the presumption that quality is determined by what a customer wants. Individuals have different wants and needs, leading to different quality standards.

🔑 Definition — User-Based Quality: Quality defined as fitness for intended use, or how well the product performs its intended function. 📌 Example: A Cadillac sedan and a Jeep Cherokee are both fit for use, but they serve different customer needs—a Cadillac for highway touring with luxury amenities, a Jeep for camping and skiing trips.

Value-Based Perspective This approach defines quality based on the relationship of usefulness or satisfaction to price.

🔑 Definition — Value-Based Quality: A quality product is one that is as useful as competing products and sold at a lower price, or one that offers greater usefulness at a comparable price. 📌 Example: Japanese brands like Toyota and Honda have better reputations for long-term durability than the Big Three (General Motors, Ford, Chrysler), allowing them to offer fewer incentives and rebates, which are essentially payments to compensate for lower quality.

Manufacturing-Based Perspective This view defines quality as the desirable outcome of engineering and manufacturing practice, or conformance to specifications. Specifications are targets and tolerances determined by designers. Targets are the ideal values for which production strives, and tolerances are the allowable variations because it is impossible to meet targets all the time.

🔑 Definition — Manufacturing-Based Quality: Quality as conformance to specifications. 📐 Formula: For a part dimension specified as "0.236 ± 0.003 cm" → the target is 0.236 centimeters, the tolerance is 0.006 centimeters (0.003 above and below), and any dimension in the range of 0.233 to 0.239 centimeters is deemed acceptable and conforms to specifications. 📌 Example: "On-time arrival" for an airplane might be specified as within 15 minutes of the scheduled arrival time. The target is the scheduled time, and the tolerance is 15 minutes.

Integrating Perspectives on Quality How quality is viewed depends on one's position in the value chain (designer, manufacturer, distributor, or customer). The customer is the driving force, and customers generally view quality from the transcendent or product-based perspective. The manufacturer must translate customer requirements into detailed product and process specifications. Product designers must balance performance and cost.

Customer-Driven Quality The American National Standards Institute (ANSI) and the American Society for Quality (ASQ) defined quality as "the totality of features and characteristics of a product or service that bears on its ability to satisfy given needs." By the end of the 1980s, a simpler, more powerful customer-driven definition emerged.

🔑 Definition — Customer-Driven Quality: "Quality is meeting or exceeding customer expectations."

QUALITY DIMENSIONS

The following are the "principal quality dimensions":

• Performance – a product's primary operating characteristics. Example: A car's acceleration, braking distance, steering, and handling.
• Features – the "bells and whistles" of a product. Example: A car may have power options, a tape or CD player, antilock brakes, reclining seats.
• Reliability – the probability of a product's surviving over a specified period of time under stated "conditions of use." Example: A car's ability to start on cold days and frequency of failures.
• Conformance – the degree to which physical and performance characteristics of a product match the pre-established standards. Example: Car's fit/finish and freedom from noises reflect this.
• Durability – the amount of use one gets from a product before it physically deteriorates or until replacement is preferable. Example: Car's corrosion resistance and long wear of upholstery fabric.
• Serviceability – the speed, courtesy, and competence of repair work. Example: Auto owner access to spare parts also comes under serviceability.
• Aesthetics – how a product looks, feels, sounds, tastes, or smells. Example: Car's color, instrument panel design, and "feel of the road" make it aesthetically pleasing.
• Perceived Quality – the "subjective assessment of quality" resulting from image. Example: Advertising, brand names shaped by magazine reviews, and manufacturers' brochures.
• Affordability, Variety, Simplicity etc. are also the principal quality dimensions.

COMPETITIVE ADVANTAGE

When a firm sustains profits that exceed the average for its industry, it possesses a competitive advantage over its rivals. Michael Porter identified two basic types of competitive advantage:

• Cost advantage: delivering the same benefits as competitors but at a lower cost.
• Differentiation advantage: delivering benefits that exceed those of competing products.

A competitive advantage enables the firm to create superior value for its customers and superior profits for itself. Cost and differentiation advantages are known as positional advantages since they describe the firm's position as a leader in either cost or differentiation. A resource-based view emphasizes that a firm utilizes its resources and capabilities to create a competitive advantage that results in superior value creation.

QUALITY EVOLUTION AND QUALITY STAGES IN JAPAN

The lecture includes Figure 34.2, which illustrates the quality evolution and quality stages in Japan, showing the progression of quality thinking from inspection-based approaches to more comprehensive management frameworks.

TOTAL QUALITY MANAGEMENT (TQM) AND ITS PHILOSOPHY

Quality as a Management Framework A 1970s General Electric (GE) task force found that product lines with poor quality reputations deemphasized the customer's viewpoint, regarded quality as synonymous with conformance to specifications, and used formal quality control systems only in manufacturing. In contrast, product lines that received customer praise emphasized satisfying customer expectations, determined needs through market research, and had formalized quality control systems for all business functions. The task force concluded that quality must be viewed as a management discipline, not solely as a technical discipline.

This led to the concept of Total Quality (TQ) . A 1992 definition endorsed by nine major U.S. corporations states:

🔑 Definition — Total Quality (TQ) : A people-focused management system that aims at continual increase in customer satisfaction at continually lower real cost. TQ is a total system approach, an integral part of high-level strategy that works horizontally across functions and departments, involves all employees top to bottom, and extends backward and forward to include the supply chain and customer chain. TQ stresses learning and adaptation to continual change as keys to organizational success.

The foundation of total quality is philosophical: the scientific method. TQ includes systems, methods, and tools. TQ is anchored in values that stress the dignity of the individual and the power of community action. Procter and Gamble's concise definition is: "Total quality is the unyielding and continually improving effort by everyone in an organization to understand, meet, and exceed the expectations of customers."

A. V. Feigenbaum coined the term Total Quality Control in the 1950s, observing that quality is directly influenced by the 9 Ms: markets, money, management, men and women, motivation, materials, machines and mechanization, modern information methods, and mounting product requirements. The Japanese adopted this concept as companywide quality control, with five aspects:

1. Quality emphasis extends through market analysis, design, and customer service.
2. Quality emphasis is directed toward operations in every department.
3. Quality is the responsibility of the individual and the work group, not inspection.
4. The two types of quality characteristics are those that satisfy and those that motivate.
5. The first customer for a part or piece of information is usually the next department.

The term Total Quality Management (TQM) was developed by the Naval Air Systems Command to describe its Japanese-style approach to quality improvement and became popular in the United States during the 1980s.

Principles of Total Quality Total quality is based on three fundamental principles:

1. A focus on customers and stakeholders.
2. Participation and teamwork by everyone in the organization.
3. A process focus supported by continuous improvement and learning.

These principles differ significantly from traditional management practices. With total quality, an organization actively seeks to identify customer needs and expectations, build quality into work processes by tapping workforce knowledge, and continually improve every facet of the organization.

Customer and Stakeholder Focus: The customer is the principal judge of quality. A company's efforts must include designing new products that delight the customer and responding rapidly to changing demands. Internal customers (employees who view themselves as both customers of and suppliers to other employees) are as important as external customers. Employees and society also represent important stakeholders. A TQ organization must demonstrate commitment to employees and view society as a stakeholder through business ethics, public health and safety, the environment, and community support.

Participation and Teamwork: Joseph Juran credited Japanese managers' full use of the knowledge and creativity of the entire workforce as a reason for Japan's rapid quality achievements. When managers give employees tools to make good decisions and the freedom and encouragement to make contributions, better quality products and processes result. Employees allowed to participate—individually and in teams—in decisions affecting their jobs can make substantial contributions to quality. This represents a profound shift from the traditional view that the workforce should be "managed" and leave their brains at the door.

💡 Why this matters: The three principles of TQ represent a complete paradigm shift from traditional command-and-control management. Success depends on management formulating systems and procedures to embed participation into the organizational culture.

⭐ Key Takeaways

Quality is the most significant factor in determining long-term organizational success, reducing costs while increasing customer satisfaction and competitive advantage. Quality must be understood from multiple perspectives (judgmental, product-based, user-based, value-based, and manufacturing-based), but the most powerful modern definition is "meeting or exceeding customer expectations." The eight principal quality dimensions—performance, features, reliability, conformance, durability, serviceability, aesthetics, and perceived quality—provide a framework for evaluating any product or service. Competitive advantage is achieved through either cost leadership or differentiation, both of which quality supports. Total Quality Management (TQM) transformed quality from a technical discipline into a comprehensive management framework based on customer and stakeholder focus, participation and teamwork by everyone, and continuous improvement and learning across all functions of the organization.

🧠 Quick Revision Questions

1. What are the five different perspectives from which quality can be viewed, and how does the customer-driven definition integrate them?
2. List and briefly explain each of the eight principal quality dimensions, providing an example for each.
3. According to Michael Porter, what are the two basic types of competitive advantage, and how does quality contribute to each?
4. What were the key findings of the General Electric task force regarding how successful and unsuccessful product lines approached quality?
5. What are the three fundamental principles of Total Quality (TQ), and how do they differ from traditional management practices?

📘 Lecture 35 — Quality in Project Management (Contd.)

📖 Overview: This lecture continues the discussion of quality in project management by examining the historical evolution of quality from simple inspection to Total Quality Management (TQM). It introduces the key stages of quality development, explains the purpose and components of a quality audit, and presents Deming's influential philosophy on management's role in achieving quality. Understanding this evolution is critical for project managers to implement effective quality systems.

🗂️ Topics Covered

The lecture covers the historical "Quality Movement" from pre-WWI inspection to modern TQM, detailing the "five level model" of quality development stages: Inspection, Quality Control, Quality Assurance, Quality Management, and Total Quality Management. It then defines the "Quality Audit" and its objectives, and concludes with an examination of "Deming's Philosophy," including his "Dreadful Diseases" and the "Deming Cycle for Improvement."

📝 Lecture Summary

35.1 THE QUALITY MOVEMENT:

This section traces the evolution of quality views over the past 100 years. Before World War I, quality was seen as inspection—sorting good items from bad, with an emphasis on problem identification. After WWI and into the early 1950s, this sorting focus remained, but principles of quality control emerged using statistical and mathematical techniques, sampling tables, and process control charts. From the early 1950s to the late 1960s, quality control evolved into quality assurance, shifting the emphasis from problem detection to problem avoidance. New principles like the cost of quality, zero-defect programs, reliability engineering, and total quality control were developed.

35.2 DEVELOPMENT OF QUALITY STAGES:

This section details the "five level model" of quality development, which represents the progression from basic inspection to an organization-wide focus on quality.

1. Inspection: Inspection is defined as an activity of measuring, examining, testing, or gauging characteristics and comparing results with specified requirements to determine conformity.

🔑 Definition — Inspection (ISO 8402): "Activity such as measuring, examining, testing, or gauging one or more characteristics of an entity and comparing the results with specified requirements in order to establish whether conformity is achieved for each characteristic."

2. Quality Control: Quality control is a collective term for activities and techniques within a process that create specific quality characteristics. This includes monitoring processes, identifying and eliminating problem causes, and using statistical process control to reduce variability and increase efficiency. It certifies that quality objectives are being met and is also referred to as the technical aspect of quality management. A good quality control system will select what to control, set standards, establish measurement methods, compare results to standards, act to correct nonconformance, monitor and calibrate measuring devices, and include detailed documentation.

💡 Why this matters: Quality control is the hands-on, technical process that ensures each step of the project produces a quality output.

3. Quality Assurance: Quality assurance is the collective term for formal activities and managerial processes planned to ensure delivered products and services are at the required quality level. It includes efforts to improve internal processes and attempts to integrate project scope, cost, and time functions. The PMBOK refers to quality assurance as the management section of quality management, where the project manager can have the greatest impact. A good quality assurance system will identify objectives and standards, be multifunctional and prevention-oriented, plan for data collection and continuous improvement, establish performance measures, and include quality audits.

💡 Why this matters: This is where the project manager establishes administrative processes to ensure and prove that deliverables meet customer requirements.

4. Quality Management: This section notes that a revolution toward improved quality has occurred, often driven by economic recessions. The push for higher quality is now customer driven, with customers demanding higher performance, faster development, higher technology, and fewer defects. Market expectations are affected by variables including:

• Salability: the balance between quality and cost
• Produceability: the ability to produce the product with available technology and workers at an acceptable cost
• Social acceptability: the degree of conflict between the product and society's values (safety, environment)
• Operability: the degree to which a product can be operated safely
• Availability: the probability the product will perform satisfactorily when used
• Reliability: the probability of the product performing without failure under given conditions for a set time
• Maintainability: the ability of the product to be retained in or restored to a performance level

Customer demands are now handled using Total Quality Management (TQM), which is an ever-improving system for integrating organizational elements to provide cost-effective products fully acceptable to the customer.

5. Total Quality Management (TQM): Total Quality encompasses the quality of work, service, information, process, organization, people, company, and objectives. Because quality is defined by the customer, mature organizations admit they cannot accurately define it. The Kodak definition is products and services that meet or exceed customer needs at a cost representing outstanding value. The ISO 9000 definition is "the totality of feature and characteristics of a product or service that bears on its ability to satisfy stated or implied needs."

Total Quality Management (TQM) is a management strategy aimed at embedding awareness of quality in all organizational processes. It provides an umbrella under which everyone can strive for customer satisfaction at continually lower costs. TQM is the management of total quality, which consists of three qualities:

1. Quality of return to satisfy shareholders
2. Quality of products and services to satisfy the consumer (end user)
3. Quality of life at work and outside work to satisfy the people in the organization

This is achieved with upstream and downstream partners, plus corporate citizenship—the social, technological, economical, political, and ecological (STEPE) responsibility of the enterprise.

📌 Example: In a Supply Chain Management approach, TQM means not just satisfying your immediate customer's needs, but the needs of your customers' customers, all the way to the end consumer.

35.3 QUALITY AUDIT:

A quality audit is an independent evaluation performed by qualified personnel to ensure the project conforms to quality requirements and follows established procedures and policies. A good quality audit will ensure that:

• The planned quality for the project will be met
• The products are safe and fit for use
• All pertinent laws and regulations are followed
• Data collection and distribution systems are accurate and adequate
• Proper corrective action is taken when required
• Improvement opportunities are identified

🔑 Definition — Quality Audit: An independent evaluation performed by qualified personnel that ensures that the project is conforming to the project's quality requirements and is following the established quality procedures and policies.

35.4 DEMING'S PHILOSOPHY:

Deming postulated that 85 percent of all quality problems required management to take the initiative and change the process, while only 15 percent could be controlled by workers. For example, workers were not at fault for poor raw materials resulting from management's decision to seek lowest-cost suppliers; management had to change purchasing policies and develop long-term vendor relationships.

Dr. Deming's Dreadful Diseases:

1. Looking elsewhere for examples, or concluding that "our problems are different"
2. "Creative accounting" rather than "commitment"
3. Purchasing to an "acceptable level of quality"
4. Management's failure to delegate responsibility
5. That employees cause all the problems
6. Quality can be "assured by inspection"
7. False starts: no organization-wide commitment

Deming pioneered the use of statistics and applied Dr. Shewhart's Plan/Do/Check/Act cycle to clerical tasks. He contended that workers must be shown what constitutes acceptable quality and that continuous improvement is possible and necessary. To achieve this, workers need training in statistical process control charts.

🔑 Definition — Deming Cycle (Plan/Do/Check/Act): A continuous improvement cycle where you Plan a change, Do it on a small scale, Check the results, and Act to standardize the improvement or begin the cycle again.

📌 Example: If a project team finds that 85% of defects come from poor raw materials, Deming's philosophy says management must change the purchasing process (e.g., develop long-term relationships with quality vendors), not blame the workers on the floor.

⭐ Key Takeaways

The most critical point is the historical evolution of quality from simple inspection to a comprehensive, organization-wide TQM strategy, culminating in the five-level model. A project manager must understand that quality assurance focuses on prevention through managerial processes, while quality control is the technical, monitoring aspect. Deming's philosophy is foundational: 85% of quality problems are management's fault and require process changes, not worker blame. A quality audit is an independent check for conformance to procedures and requirements. Finally, TQM is a total system covering shareholder returns, customer satisfaction, people's quality of life, and corporate citizenship.

🧠 Quick Revision Questions

1. What is the key difference between Quality Control (QC) and Quality Assurance (QA)?
2. According to Deming, what percentage of quality problems require management to change the process, and what are two of his "Dreadful Diseases"?
3. List the five stages of quality development in order, from least to most comprehensive.
4. What is the primary purpose of a quality audit?
5. According to the lecture, what are the three specific "qualities" that make up "Total Quality" in TQM?

📘 Lecture 36 — Principles of Total Quality

📖 Overview: This lecture defines Total Quality Management (TQM) from multiple expert perspectives and explores the core principles, practices, and scope of TQM. It emphasizes empowerment as a key mechanism for quality improvement, detailing how to implement it in project environments, and concludes with a critical analysis of the Cost of Quality (COQ) and its impact on project success.

🗂️ Topics Covered

The lecture begins with definitions of Total Quality from Crosby, PandG, and Feigenbaum (9Ms), then outlines key Total Quality Practices. The three fundamental Principles of Total Quality—Customer Focus, Participation and Teamwork, Continuous Improvement—are introduced, followed by the three-part Scope of TQM (Infrastructure, Practices, Tools). A detailed examination of Empowerment covers Participative Management, Accountability, key principles, and six specific ways to empower employees for project quality. The lecture concludes with an analysis of the Cost of Quality, including the four sub-categories (Prevention, Appraisal, Internal Failure, External Failure) and how to reduce them.

📝 Lecture Summary

36.1 Definitions of Total Quality

Total quality is defined from several viewpoints. Philip Crosby asserts that quality is not only free, it is a profit maker, with an increase of 5%-10% in profitability by concentrating on quality. Procter & Gamble (P&G) defines Total Quality as the unyielding and continually improving effort by everyone in an organization to understand, meet, and exceed the expectations of customers. A.V. Feigenbaum introduced a comprehensive approach to quality influenced by 9Ms: Market, Money, Material, Management, Machines, Men/Women, Motivation, Mechanizations, Modern Information Methods, and Mounting Products Requirements. Total quality is a people-focused management system aiming at continual increase in customer satisfaction at continually lower real cost. It is an integral part of high-level strategy, works horizontally across functions and departments, involves all employees top to bottom, and extends backward and forward to include the supply chain and customer chain.

36.2 Total Quality Practices

Total Quality practices include a set of behaviors and actions for organizational improvement:

• Encouraging openness
• Creating climates of trust and eliminating fear
• Listening and providing feedback
• Leading and participating in group meetings
• Solving problems with data
• Clarifying goals and resolving conflicts
• Delegating and coaching
• Implementing change
• Making continuous improvement a way of life

36.3 Principles of Total Quality

There are three basic principles of total quality:

1. Customer Focus
2. Participation and Teamwork
3. Continuous Improvement (CI) and Learning

36.4 Scope of Total Quality Management

The scope of TQM is depicted in three tiers:

• Infrastructure: The basic management system necessary to function as a high-performing organization.
• Practices: Activities that occur within a management system to achieve high-performance objectives.
• Tools: A wide variety of graphical and statistical methods to plan work activities, collect data, analyze results, monitor progress, and solve problems.

36.5 Empowerment

Empowerment means managers must relinquish some power, creating a power shift that can cause management fears that workers will abuse this privilege. With empowerment, employees have authority and responsibility to make things happen. Everyone in the organization is “captain of his game,” perceiving their work unit as a key part of the “corporate enterprise.” It builds “confidence in workers” by showing that the company has confidence in them to make decisions on their own. Empowerment is vertical teamwork between managerial and non-managerial personnel. As a whole, participation and empowerment assume that employees are willing to improve their daily work process and relationships. Workers know what goes wrong and where hurdles are in their processes; if given targets and support, they are best to develop creative ideas for positive change. A key problem for many project-based organizations is reducing “bureaucratic red tape” that prevents employees from seizing the initiative.

36.5.1 Participative Management

Participative organizations give information, knowledge, power, and rewards to all employees so that everyone can be involved in the organization’s performance. Participative management is an essential basis for an empowered workforce, putting “everybody's intellect” to work. Different points of view help shape better decisions. It requires that responsibility and accountability be taken to the lowest possible level. Participative management does not imply abrogation by management of its responsibility; it implies workforce involvement in the decision-making process, but the final decision on corporate matters remains the manager's responsibility. When empowered employees become convinced their duty is to their “process” not to their “boss,” teams shoulder responsibility and a cooperative style evolves. Empowerment encourages innovation because employees have authority to try new ideas. Access to information enhances cooperation and empowerment, allowing teams to manage and control opportunity more effectively than under old hierarchical rules.

36.5.2 Accountability

Employees empowered to make decisions are also held accountable for results. Accountability is not to punish a person or to generate immediate, short-term results. The intent is to ensure empowered employees are:

• Giving their best efforts
• Working toward agreed-upon goals
• Behaving responsibly toward each other

36.5.3 Empowerment – Some Key Principles

Key principles of empowerment include:

• People are a valuable resource because they have knowledge and ideas.
• People want to participate.
• When people participate, they feel empowered and think like owners.
• When people participate, they look for ways to improve opportunities.
• When people have importance in corporate and department decisions, better solutions are developed.
• People should be treated fairly and with respect. Organizations should make a long-term commitment to people development.

36.5.4 Six Ways of Empowering Employees for Quality Improvement in Projects

1. Involve employees in developing strategies for continuous improvement.
2. Provide employees with skills required to solve problems and make decisions.
3. Define involvement and empowerment based on the mission of the organization.
4. Establish organizational and individual goals.
5. Establish customer-driven performance measurement at the individual level.
6. Involve and empower everyone to focus on continuous improvement.

Successful empowerment requires providing employees with education, resources, and encouragement; examining policies for needless restrictions; fostering an atmosphere of trust; and sharing information freely rather than guarding it as a source of control.

💡 Why this matters: Empowerment is not just about delegation; it's a strategic shift that unlocks employee potential for innovation and process improvement, directly impacting project quality and organizational agility.

36.6 Cost of Quality

The Cost of Quality (COQ) verifies that a product or service meets customer requirements. It is classified as "the cost of conformance" and "the cost of nonconformance." Conformance costs include training, indoctrination, verification, validation, testing, maintenance, calibration, and audits. Nonconforming costs include scrap, rework, warranty repairs, product recalls, and complaint handling. Trying to save project dollars by reducing conformance costs can be disastrous; e.g., an American supplier who delivered 10,000 parts with only two rejects had the entire batch returned by a Japanese customer.

Feigenbaum divided cost of quality into two categories and four sub-categories:

• Costs of Control:
  • Prevention costs: Up-front costs oriented toward satisfying customer requirements with the first and all succeeding units without defects (e.g., design review, training, quality planning).
  • Appraisal costs: Costs associated with evaluating product or process to ascertain how well customer requirements have been met (e.g., inspection, lab tests, vendor control).
• Costs of Failure of Control:
  • Internal failure costs: Costs associated with failure to make products acceptable before leaving the organization's control (e.g., scrap, rework, repair, downtime).
  • External failure costs: Costs associated with the customer determining their requirements have not been satisfied (e.g., customer returns, complaint evaluation, warranty repairs).

Prevention costs are expected to rise initially as more time is spent on prevention. As processes improve, appraisal costs go down. The biggest savings come from reducing internal failure areas like rework and scrap. External costs also decrease as processes yield first-time quality. Prevention costs can be further decreased by eliminating waste due to rejects, design flaws, improperly instructed manpower, and excessive expenses.

🔑 Definition — Prevention Costs: Up-front costs oriented toward the satisfaction of customer's requirements with the first and all succeeding units of product produced without defects.

📐 Formula: COQ = Costs of Control (Prevention + Appraisal) + Costs of Failure of Control (Internal Failure + External Failure)

📌 Example: The American supplier scenario. An American company supplied 10,000 parts to a Japanese customer. Only 2 rejects were found during inspection. The nonconformance cost (the entire batch returned, losing the order and reputation) was an order of magnitude greater than the conformance cost (more thorough internal testing/inspection). This shows that reducing prevention/appraisal costs can lead to massive external failure costs.

⭐ Key Takeaways Total Quality is a strategic, people-focused system integrating customer focus, teamwork, and continuous improvement. Empowerment is a critical principle where managers share power, giving employees authority and accountability to improve their processes, which fosters innovation. The Cost of Quality is not just about spending less; it's a strategic trade-off where investing in prevention and appraisal costs significantly reduces the far more damaging internal and external failure costs. Finally, successful TQM implementation requires a shift from bureaucratic control to a culture of trust, participation, and long-term commitment to employee development.

🧠 Quick Revision Questions

1. What are the three basic principles of Total Quality as defined in this lecture?
2. Explain the difference between empowerment and participative management.
3. What are the four sub-categories of the Cost of Quality, and give one example of each.
4. List two of the six ways to empower employees for quality improvement in projects.
5. Why is reducing “bureaucratic red tape” considered important for empowerment in project-based organizations?

📘 Lecture 37 — Customer Focused Project Management

📖 Overview: This lecture explores the critical importance of placing customers at the center of project management. It defines who customers are, categorizes customer types, and introduces frameworks like the Kano Model to understand customer satisfaction. The lecture provides practical methods for measuring satisfaction, managing customer relationships, and delivering quality service to ensure long-term business success.

🗂️ Topics Covered

The lecture covers the definition of a customer in project contexts, key business goals, types of customers (primary, secondary, indirect, external, consumer, intermediary, false, internal), customer-driven project organizations, customer identification methods, the Kano Model for classifying product attributes, customer satisfaction measurement techniques, Customer Relationship Management (CRM), gathering customer information, and a four-step process for quality customer service including handling difficult customers.

📝 Lecture Summary

37.1 Who is a customer in any project?

World class projects and organizations are obsessed with meeting and exceeding customer expectations. Firms should learn to have "customer focused projects", often in response to competitive crises. Customers in any project refer to:

1. Any individual or group that receives and must be satisfied with the work product or output of a process.
2. Individual or group whose request a process is intended to fulfill.
3. Anyone who is impacted by the product or process.

Looking at your project organization from your customers’ point of view and “improving processes” to enable you to meet and exceed your customers’ expectations is the only way to achieve quality. It is important to meet customer expectations as it is the prime responsibility of every organization to meet the needs of its customers. Understanding of one’s customers leads to customer satisfaction. Japanese relate quality to customer satisfaction.

37.2 Key goals for businesses:

Following are the four key goals for any business:

1. Satisfy customers
2. Achieve higher customer satisfaction than competitors
3. Retain customers in long run
4. Gain market share

To achieve aims and goals, a business must deliver ever-improving value to its customers. Value refers to “quality related to price”. It is important as consumers no longer buy solely on the basis of price.

37.3 Types of Customers:

• Primary: “Direct receiver of output of the process” (bank loan seeker, lab test report receiver). It is the source of product and process requirement.
• Secondary: Secondary customers are from “outside of process” boundaries, who also receive any process output, but not reason for “process’ existence” (bank’s head office receiver secondary output).
• Indirect: When original boundaries do not receive process output directly but are affected if process output is incorrect or late (logistic department).
• External Customers: Those who are located outside the organizational boundaries, receive end product or service but is not the actual user. (Power supplier for computers manufacturing, distributors).
• Consumer End User: This refers to the final user of the product. Sometimes the external customers and consumers are the same.
• Intermediary: In between producer and end user (Transporter).
• False: When a process that performs activities that do not add value to product or service. Inspectors doing 100% inspection. It needs to be eliminated.
• Internal: Next person to whom product passed on for further processing. His requests must be met, but not at cost of external customers.

37.4 Customer-Driven Project Organizations:

If competitors offer better choices for similar price, consumers naturally select package with highest “perceived quality”.

37.5 Customer Identification:

37.5.1 Fundamental Questions in Identifying Customers:

Identifying customers begins with asking some fundamental questions:

• What products/services are produced?
• Who uses products/services?
• Do employees call/write to/answer questions for?
• Supplies inputs

37.5.2 Importance of Identifying Customer Types:

Every customer type, source of product, product requirements must be identified and process effectiveness must be measured. Information on what satisfies customer, and what improvements are necessary, comes from lost, prospective, and competitors’ customers, who provide useful insights.

37.6 Kano Model:

The Kano Model of Customer (Consumer) Satisfaction classifies product attributes based on how they are perceived by customers and their effect on customer satisfaction. These classifications are useful for guiding design decisions in that they indicate when good is good enough, and when more is better.

Project activities in which the Kano Model is useful:

1. Identifying customer needs
2. Determining functional requirements
3. Concept development
4. Analysing competitive products

Other tools that are useful in conjunction with the Kano Model:

1. Eliciting Customer Input
2. Prioritisation Matrices
3. Quality Function Deployment
4. Value Analysis

Introduction: The Kano Model of Customer satisfaction divides product attributes into three categories: threshold, performance, and excitement. A competitive product meets basic attributes, maximises performances attributes, and includes as many “excitement” attributes as possible at a cost the market can bear.

Threshold Attributes: Threshold (or basic) attributes are the expected attributes or “musts” of a product, and do not provide an opportunity for product differentiation. Increasing the performance of these attributes provides diminishing returns in terms of customer satisfaction; however the absence or poor performance of these attributes results in extreme customer dissatisfaction. An example of a threshold attribute would be brakes on a car.

🔑 Definition — Threshold Attributes: Expected attributes or "musts" of a product whose absence causes extreme dissatisfaction but whose presence does not increase satisfaction beyond a neutral point.

Performance Attributes: Performance attributes are those for which more is generally better, and will improve customer satisfaction. Conversely, an absent or weak performance attribute reduces customer satisfaction. Of the needs customers verbalise, most will fall into the category of performance attributes. These attributes will form the weighted needs against which product concepts will be evaluated. The price for which customer is willing to pay for a product is closely tied to performance attributes. For example, customers would be willing to pay more for a car that provides them with better fuel economy.

🔑 Definition — Performance Attributes: Attributes where "more is better" — higher performance directly increases customer satisfaction, and lower performance decreases it.

Excitement Attributes: Excitement attributes are unspoken and unexpected by customers but can result in high levels of customer satisfaction, however their absence does not lead to dissatisfaction. Excitement attributes often satisfy latent needs – real needs of which customers are currently unaware. In a competitive marketplace where manufacturers’ products provide similar performance, providing excitement attributes that address “unknown needs” can provide a competitive advantage. Although they have followed the typical evolution to a performance then a threshold attribute, cup holders were initially excitement attributes.

🔑 Definition — Excitement Attributes: Unspoken, unexpected product features that delight customers when present but do not cause dissatisfaction when absent.

Other Attributes: Products often have attributes that cannot be classified according to the Kano Model. These attributes are often of little or no consequence to the customer, and do not factor into consumer decisions. An example of this type of attribute is a plate listing part numbers found under the hood on many vehicles for use by repairpersons.

Application of the Kano Model Analysis: A relatively simple approach to applying the Kano Model Analysis is to ask customers two simple questions for each attribute:

1. Rate your satisfaction if the product has this attribute?
2. Rate your satisfaction if the product did not have this attribute?

Customers should be asked to answer with one of the following responses:

• A) Satisfied
• B) Neutral (It's normally that way)
• C) Dissatisfied
• D) Don’t care.

Basic attributes generally receive the “Neutral” response to Question 1 and the “Dissatisfied” response to Question 2. Exclusion of these attributes in the product has the potential to severely impact the success of the product in the marketplace.

💡 Why this matters: The Kano Model helps project managers prioritize features. Basic attributes must be included; performance attributes should be optimized; excitement attributes provide competitive advantage. Asking "How much extra would you pay?" aids trade-off decisions for performance attributes. Attributes receiving "Don't care" can be dismissed unless critical for product functionality.

37.7 CUSTOMER SATISFACTION MEASUREMENT:

37.7.1 Methods of Customer Retention:

Following are the methods for retaining customers:

• Establish honest relationship and empathize
• Reward loyalty (airline’s frequent flyer)
• Reward usage (Coupons, credit points, preferential treatment)
• Provide unpaid service (free product targets, after sales service)

37.7.2 Seven Steps to Customer Satisfaction System:

• Step 1: Total management commitment
• Step 2: Get to know your customers
• Step 3: Develop “performance and process standards” of service quality
• Step 4: Hire, train, and compensate good staff
• Step 5: Reward service accomplishments
• Step 6: Stay close to your customers
• Step 7: Work towards continuous improvement in “service quality performance”

37.7.3 Customer Defections:

1. Leading practices for profitability and market share must understand linkages between voice of customer and design, production, and delivery processes.
2. Ensures that no critical requirements fall through cracks and minimizes potential gaps between expected quality and actual quality.
3. Make commitment to customer that promotes trust and confidence in products and services.
4. Must have effective Customer Relationship Management (CRM) processes by which customer can easily seek assistance, comment, complain and receive prompt resolution of their concerns.

37.7.4 Must measure Customer Satisfaction:

1. Compare results relative to competitors
2. Use information to evaluate
3. Improve internal processes

37.7.5 Methods of Measuring Customer Satisfaction:

There are two methods of measuring customer satisfaction:

1. Quality Dimension Development
2. Generate Critical Incidents

37.7.5.1 Quality Dimensions Development Method:

Step 1: Creating list of quality dimensions: a) Read professional literature and enlist quality dimensions b) Generate list from personal experience

Step 2: Write definitions of each dimension: a) Definition can be in general terms

Step 3: Develop specific examples for each quality dimension: a) Examples: Specific-reflecting service or product b) Examples: Specific behaviors of providers c) Declarative statements

37.7.5.2 Five Key Dimensions of Service Quality:

1. Reliability: Ability to provide what was promised, dependably and accurately. Includes customer service representatives responding in promised time, following customer instructions, providing error free invoices, making repairs correctly first time.
2. Assurance: Knowledge and courtesy of employees. Their ability to convey “trust and confidence”. Includes ability to answer questions, having capabilities to do necessary work, monitoring credit card transactions to avoid fraud, being polite during customer transactions.
3. Tangibles: Physical facilities, equipment and appearance of persons including attractive facilities, appropriately dressed employees, well designed forms that are easy to read and interpret.
4. Empathy: Degree of caring and attention provided to customer. Includes explaining “Tech Jargon” in layman’s language, recognizing regular customers by name.
5. Responsiveness: Willingness to help customer and provide prompt service. For example: acting quickly to resolve problems, promptly crediting returned merchandise, rapidly replacing defective products.

Additional dimensions include Timeliness of Support (completing job when expected, meeting deadlines, finishing within stated time frame) and Responsiveness of Support (quick to respond, immediately helped when needed, short wait time).

37.8 Customer Relationship Management (CRM):

Customer Relationship Management (CRM) includes attention to:

• Target and developing customer contact employees
• Empowering them to do whatever is necessary to satisfy customers

37.9 Gathering Customer Information:

Customer requirements are called “voice of customer”. There are a variety of methods to “listen” to the Voice of Customer. To do it effectively, information needs to be collected about the customer like: a) Needs and expectations b) Importance c) Satisfaction with company's performance

37.10 Four Steps to Quality Customer Service:

Step 1: Send positive attitude:

• Product Knowledge / command
• Appearance (dress, quality, cleanliness, orderliness)
• Body language (head, arms, facial, smile, body movement, eye contact)
• Sound of your voice (tone and how you say it) — face to face and on telephone
• Staying energized
• Empathize (concern for customer’s benefits)

Step 2: Identify needs of your customers, guests, clients a) Human Needs: welcomed, respected, comfortable, orderly, understood, helped, important, appreciated, recognized b) Timing Needs: hold time on telephone, waiting in office, letter response, return calls, appropriate time to meet c) Location Needs d) Product Needs: stated, unstated, basic, delighter e) Create an environment to listen f) Careful Listening and Understanding g) Feedback / Evaluation

Step 3: Provide for needs of your customers, guests, clients

• Are you ready to fulfill the human, timing, location, and product needs of the customer?
• Are you capable to fulfill the human, timing, location, and product needs of the customer?
• Do you have the required product/service to meet the needs of the customer?
• Have you actually fulfilled the human, timing, location, and product needs of the customer?

Step 4: Make sure your customers, clients, guests return to you

• Make sure you delivered both the procedures and the personal
• Be sensitive to check your performance by the outcomes before, during and after the service delivery
• Handling complaints for cases of gaps: Listen to stated and non-stated complaints carefully; Empathize; Repeat and confirm understanding; Apologize genuinely; Acknowledge sympathy; Correct the situation; Identify root-causes and prevent recurrence
• Types of difficult customers: Angry, Nasty or Obnoxious, Demanding, Constant Critic, Non-Stop Talker, Indecisive, Intoxicated, Argumentative
• They are usually difficult for their own reasons - not because of you
• Reasons Why Customers are Difficult: Negative experience, Frustrated, Confused, Satisfy their ego or self-esteem, Ignored, Treated poorly, In bad mood
• Get Difficult Customers on Your Side: Do not take it personally; Remain calm; listen carefully; Do not just protect yourself or your company; Focus on the problem, not the person; Turn the difficult one into a satisfied customer
• Take an extra step - surprise the customer (e.g., ticket agent offering to select seat for return flight, salesperson delivering personally, waiter offering extra glass of coffee)

To re-engineer your Customer Satisfaction into Quality Customer Satisfaction:

• Customer Satisfaction Vision and Policy
• Customer Satisfaction Training
• Customer Satisfaction Personality Grooming and Development
• Customer Satisfaction Systems and Procedures
• Customer Satisfaction Consistency
• Customer Satisfaction Measurement (e.g. customer retention rate)
• Develop and regularize Customer Satisfaction Delighters

Determine Questions: Be Concise, Precise, Direct, Unambiguous Response Format: Checklist Format (yes/no) or Likert-type scale (1-5 scale) Sampling techniques: Census (all customers), Judgmental Sampling (based on judgment), Statistical Sampling (based on statistical probability)

🔑 Definition — Likert Scale: A psychometric scale commonly used in questionnaires where respondents specify their level of agreement or disagreement with a statement, typically on a 1-5 scale.

📌 Example (Questionnaire Introduction): "To better serve you, we would like to know your opinion of the quality of our service at XYZ Company. You recently received service from our company. Please indicate the extent to which you agree or disagree with the following statements about the service you received from the staff. Circle the appropriate number using the scale below: 1, 2, 3, 4, 5."

⭐ Key Takeaways

Customer-focused project management is essential for long-term business success, with the key goals being to satisfy customers, outperform competitors, retain customers, and gain market share. The Kano Model provides a powerful framework for classifying product attributes into threshold (must-haves), performance (more-is-better), and excitement (delighters) categories, guiding design and prioritization decisions. Measuring customer satisfaction through quality dimensions (reliability, assurance, tangibles, empathy, responsiveness) and using structured methods like Likert-scale questionnaires are critical for continuous improvement. The four-step process to quality customer service—sending a positive attitude, identifying needs, providing solutions, and ensuring customer return—provides a practical roadmap, with special attention required for handling difficult customers and complaints effectively. Finally, Customer Relationship Management (CRM) systems and gathering the "voice of customer" are foundational for aligning project outputs with customer expectations.

🧠 Quick Revision Questions

1. What are the three categories of product attributes in the Kano Model, and how does each affect customer satisfaction when present or absent?
2. List the five key dimensions of service quality and provide one example for each.
3. What are the four key goals for any business according to this lecture?
4. Describe the four steps to quality customer service.
5. How does the Kano Model analysis use two questions to classify product attributes, and what do the responses "Neutral" and "Dissatisfied" to these two questions indicate?

📘 Lecture 38 — Quality Improvement Tools

📖 Overview: This lecture introduces the seven basic tools of Statistical Process Control (SPC) used for quality improvement in project management. It explains how these tools help collect data, identify patterns, measure variability, and make objective decisions based on quantifiable facts rather than subjective judgment.

🗂️ Topics Covered

The lecture covers the seven basic tools of Statistical Process Control: Data Tables, Cause-and-Effect Analysis (Fishbone), Histograms, Pareto Analysis, Scatter Diagrams, Trend Analysis, and Process Control Charts. It explains each tool's purpose, construction, and application, along with concepts like common vs. special cause variation, control chart interpretation, and the normal distribution's role in quality control.

📝 Lecture Summary

Seven Basic Tools of Statistical Process Control (SPC):

Statistical methods have become prevalent throughout business, industry, and science, playing a major role in decision-making. The statistical point of view takes decision making out of the subjective autocratic decision-making arena by providing the basis for objective decisions based on quantifiable facts. This change provides benefits: improved process information, better communication, discussion based on facts, consensus for action, and information for process changes.

Statistical Process Control (SPC) takes advantage of the natural characteristics of any process. All business activities can be described as specific processes with known tolerances and measurable variances. The measurement of these variances provides the basis for continuous process improvement. The seven basic tools are: Data Tables, Pareto Analysis, Cause-and-Effect Analysis, Trend Analysis, Histograms, Scatter Diagrams, and Process Control Charts.

38.1.1 Data Tables:

Data tables or data arrays provide a systematic method for collecting and displaying data. They are forms designed for collecting specific data, providing a consistent, effective, and economical approach to gathering data, organizing them for analysis, and displaying them for preliminary review. Data tables sometimes take the form of manual check sheets where automated data are not necessary or available. Simple-to-understand, straightforward tables are key to successful data gathering.

🔑 Definition — Data Table: A systematic method for collecting and displaying data, often in the form of check sheets designed to minimize complicated entries.

📌 Example: An attribute (pass/fail) data figure for "Material Receipt and Inspection" shows defect categories: incorrect invoices (invoice doesn't match purchase order), incorrect inventory (inventory doesn't match invoice), damaged material, and incorrect test documentation (required supplier test certificate not received). From this check sheet, the total number of defects is 34, the highest number of defects is from supplier A, and the most frequent defect is incorrect test documentation.

38.1.2 Cause-and-Effect Analysis (C and EA) "Fishbone":

After identifying a problem, it is necessary to determine its cause. Cause-and-effect analysis uses diagramming techniques to identify the relationship between an effect and its causes. Cause-and-effect diagrams are also known as fishbone diagrams. Six steps are used to perform a cause-and-effect analysis:

🔑 Definition — Cause-and-Effect Diagram (Fishbone Diagram): A diagramming technique used to identify the relationship between an effect and its causes, named for its fishbone-like appearance.

Step 1 – Identify the problem: This often involves other SPC tools like Pareto analysis, histograms, and control charts, as well as brainstorming. The result is a clear, concise problem statement.

Step 2 – Select interdisciplinary brainstorming team: Select a team based on the technical, analytical, and management knowledge required to determine the causes.

Step 3 – Draw problem box and prime arrow: The problem box contains the problem statement. The prime arrow functions as the foundation for the major categories.

Step 4 – Specify major categories: The six basic categories for primary causes are most frequently: personnel, method, materials, machinery, measurements, and environment. Other categories may be specified based on needs.

Step 5 – Identify defect causes: Three approaches exist: the random method (list all six major causes at the same time and identify causes for each category), the systematic method (focus on one major category at a time in descending order of importance), and the process analysis method (identify each sequential step and perform cause-and-effect analysis for each step).

Step 6 – Identify corrective action: Based on the cause-and-effect analysis and determination of causes, identify corrective action. The cause-and-effect diagram is reversed so the problem box becomes the corrective action box.

💡 Why this matters: The fishbone diagram helps distinguish between symptoms and root causes, preventing teams from treating only surface-level issues while the underlying problem persists.

38.1.3 Histogram (HG):

A histogram is a graphical representation of data as a frequency distribution. This tool is valuable in evaluating both attribute (pass/fail) and variable (measurement) data. Histograms offer a quick look at data at a single point in time; they do not display variance or trends over time. A histogram displays how cumulative data looks today, useful for understanding the relative frequencies (percentages) or frequency (numbers) of data and how that data are distributed.

🔑 Definition — Histogram: A graphical representation of data as a frequency distribution that shows how data are distributed at a single point in time.

📌 Example: Figure 38.8 illustrates a histogram of the frequency of defects in a manufacturing process, showing the distribution of different defect types.

38.1.4 Pareto Analysis (PA):

A Pareto diagram is a special type of histogram that helps identify and prioritize problem areas. It directs attention to the most frequently occurring element based on the Pareto principle (80/20 rule). There are three types:

1. Basic Pareto analysis: Identifies the vital few contributors that account for most quality problems.
2. Comparative Pareto analysis: Focuses on any number of program options or actions.
3. Weighted Pareto analysis: Gives a measure of significance to factors like cost, time, and criticality that may not appear significant at first.

🔑 Definition — Pareto Analysis: A technique using a special histogram to identify and prioritize the most significant problem areas by quantifying frequency of occurrence.

📌 Example: From the material receipt and inspection process, the basic Pareto analysis shows supplier A experiencing the most rejections with 37 percent of all failures. Comparative Pareto analysis (Figure 38.11) displays the use of this method to assess the difference in defects after corrective action.

38.1.5 Scatter Diagrams:

A scatter diagram or scatter plot organizes data using two variables: an independent variable and a dependent variable. These data are recorded on a simple graph with X and Y coordinates showing the relationship between the variables. Relationships fall into several categories: no correlation (data points widely scattered with no pattern), curvilinear correlation (U-shaped), negative correlation (downward slope), and positive correlation (upward slope).

🔑 Definition — Scatter Diagram: A pictorial representation of process control data using two variables (independent and dependent) to show the relationship between them.

📌 Example: From solder certification test scores, the independent variable (experience in months) is on the X-axis, and the dependent variable (score) is on the Y-axis. The scatter plot shows a curvilinear relationship: the least and most experienced employees scored highest, while those with intermediate experience did relatively poorly.

38.1.6 Trend Analysis (T/A):

Trend analysis is a statistical method for determining the equation that best fits the data in a scatter plot. It quantifies relationships, determines the equation, and measures the fit. This method is also known as curve fitting or least squares. Trend analysis can determine optimal operating conditions by providing an equation describing the relationship between the dependent (output) and independent (input) variables. One of the most important contributions is forecasting, which enables prediction of what is likely to occur in the future based on the regression line.

🔑 Definition — Trend Analysis: A statistical method for determining the equation that best fits scatter plot data, also known as curve fitting or least squares.

📌 Example: The equation of the regression line (trend line) from the solder certification test data provides a measure of change in output variable caused by every incremental change in the input variable, allowing prediction of future outcomes as the independent variable attains values beyond existing data.

38.1.7 Process Control Charts (C/C):

The use of control charts focuses on the prevention of defects rather than their detection and rejection. It costs much more to produce unsatisfactory products or services than satisfactory ones due to costs in labor, materials, facilities, and loss of customers.

🔑 Definition — Control Chart: A statistical tool used to monitor process stability, distinguish between common cause and special cause variation, and focus on defect prevention.

Control Charts and the Normal Distribution: The construction, use, and interpretation of control charts is based on the normal statistical distribution. The centerline represents the average or mean of the data (X̄). The upper control limit (UCL) and lower control limit (LCL) represent the mean plus and minus three standard deviations (σ). The normal distribution is a bell-shaped curve (Gaussian distribution) symmetrical about the mean, where 99.73 percent of all measurements lie within ±3σ, which is why limits on control charts are called three-sigma limits.

📌 Key Fact: Companies like Motorola have embarked upon a six-sigma limit rather than three-sigma, allowing only two defects per billion units produced. However, maintaining six-sigma can be extremely expensive unless costs are spread over very large production volumes.

Common cause variability (or variation) is always present in any process—it is the part of variability inherent in the process itself and can be corrected only by a management decision to change the basic process. Special cause variability (or variation) can be controlled at the local or operational level, indicated by a point beyond the control limit or a persistent trend approaching the control limit.

Control Chart Types: There are two types of control charts: variable charts for continuous data and attribute charts for discrete data. X̄ and R charts measure control processes with continuous variables (weight, length, time, volume). p and NP charts measure attribute characteristics in a sample—p charts when failures are expressed as a fraction, NP charts when failures are expressed as a number. c and u charts measure number or portion of defects in a single item—c charts when sample size is fixed, u charts when sample size is not fixed.

Control Chart Components: Each control chart has a centerline (X̄ bar line), statistical control limits (UCL and LCL), and calculated attribute or control data. Some contain specification limits, which differ from statistical control limits in that they are prescribed for a process rather than resulting from measurement of the process.

Control Chart Interpretation: A properly interpreted control chart can tell much more than whether the process is in or out of control. Key patterns include:

• Runs: Several successive points on one side of the central line. A run with a length of seven points indicates an abnormality.
• Trends: A continued rise or fall in a series of points. Seven consecutive points rising or falling indicates an abnormality.
• Periodicity: Points showing the same pattern of change (rise or fall) over equal intervals.
• Hugging: Points close to the centerline or control limit. Abnormality exists if 2 out of 3, 3 out of 7, or 4 out of 10 points lie within the outer one-third zone.
• Out of control: Data points exceed either the UCL or LCL.
• In control: No obvious abnormalities appear.

⭐ Key Takeaways

The seven basic tools of SPC—Data Tables, Fishbone Diagrams, Histograms, Pareto Analysis, Scatter Diagrams, Trend Analysis, and Control Charts—form a complete toolkit for data-driven quality improvement. Control charts are the most powerful tool, distinguishing between common cause variation (requiring management-level changes) and special cause variation (addressable at the operational level). Understanding the normal distribution and the concept of three-sigma limits (containing 99.73% of data) is fundamental to interpreting control charts. The Pareto principle helps focus improvement efforts on the vital few causes that account for most problems, while cause-and-effect analysis systematically traces problems to their root causes.

🧠 Quick Revision Questions

1. What are the seven basic tools of Statistical Process Control, and what is the primary purpose of each?
2. Explain the difference between common cause variation and special cause variation in process control.
3. What does a "run" of seven consecutive points on one side of the centerline indicate on a control chart?
4. How does a Pareto analysis differ from a basic histogram, and what are its three types?
5. What percentage of measurements lie within three-sigma limits in a normal distribution, and why is this significant for control chart interpretation?

📘 Lecture 39 — Project Effectiveness Through Enhanced Productivity

📖 Overview: This lecture examines the critical relationship between competitiveness and productivity in project management. It defines productivity, distinguishes it from production, explores different professional perspectives, and identifies barriers to productivity. The lecture also provides comprehensive strategies for productivity improvement through both hard and soft factors, including human resource management techniques.

🗂️ Topics Covered

The lecture covers competitiveness and its indicators, definitions of productivity in project management context, differences between production and productivity, various professional perspectives on productivity, definitions of effectiveness and efficiency, types of productivity including partial and total factor productivity, white-collar productivity challenges, critical barriers to productivity, causes of productivity decline, productivity improvement strategies, categories of productivity factors (external and internal), and soft factors including motivation, incentives, job design, worker participation, training, time management, and quality of work life.

📝 Lecture Summary

39.1 Competitiveness

Competitiveness emerged strongly in the new era of globalization and describes the "economic strength" of any organization or position of a company with respect to its competitors in the marketplace. Competitiveness is the process by which one entity strives to outperform another. In organizations, competitiveness is the ability to get customers to choose your product or service over competing alternatives on a sustainable basis. Competitiveness is continually "sustained incorporated in productivity," resulting in high wages and living standards. It is demonstrated by the "ability to meet the rest of free international markets" while "expanding real income."

39.1.1 Indicators of Competitiveness

Macro-level competitiveness of nations reflects the standard of living of their citizens. National competitiveness is a consolidation of micro-level performances of companies and individuals, who are the true "Agents of Economic Growth." The Competitiveness Pyramid shows that company and industry competitiveness at the micro level feeds into national competitiveness at the macro level.

Competitiveness depends on productivity: "Standard of living is determined by productivity of a nation's economy which is measured by the value of goods and services (products) produced per unit of the nation's human, capital and natural resources."

Indicators of competitiveness include Productivity: the efficiency with which goods and services are produced and provided, determined by previous investments, quality and performance of workforce, technology innovation, quality of plant and equipment, and the efficiency with which these factors of production are utilized.

Productivity of "local" industries is of fundamental importance to competitiveness. It depends on:

1. Sophistication with which companies compete
2. Quality of the microeconomic business environment

When productivity and quality are considered together, competitiveness can be enhanced. The definition of productivity in a successful project management organization is to create surplus through productive output. Productivity = Outputs (Time/Quality) Inputs.

🔑 Definition — Competitiveness: The ability of an entity to outperform another and get customers to choose your product or service over competing alternatives on a sustainable basis.

🔑 Definition — Productivity (in PM context): Outputs divided by Inputs, with consideration of both quality and time.

📐 Formula: Productivity = Outputs / Inputs → The ratio of goods/services produced to resources used, considering time and quality factors.

39.2 Productivity in the Context of Project Management

39.2.1 Definition of Productivity

1. Ratio of output to input by a large number of professionals.
2. ILO Definition: "Ratio between output of wealth produced and input resources used up in process of production."
3. Comparative tool for managers, industrial engineers, economists, and politicians.

The Project Management System diagram (Figure 39.2) shows inputs (men, machines, materials, money, methods, management) being transformed through a conversion process into outputs.

39.2.2 Difference between Production and Productivity

Production: Concerned with the activity of "producing goods and/or services." Productivity: "Efficient utilization of resources (input) in producing goods/services (output)."

The basic differences:

• Production is the quantity of output produced.
• Productivity is the "ratio of output produced to input(s) used."
• Higher productivity means accomplishing more with the same "amount of resources" or achieving higher output in terms of volume/quality for the same input.

39.2.3 Messages of Productivity

Taylor's Message of Productivity:

• Various pay plans based on output for surplus increase: labor productivity is not possible without work order that: a. Provided ample reward b. Adequate targets c. Managerial help
• Careful advance planning by manager
• Managers to design work system for workers to do their best.

Frederick concluded: Low productivity is a matter of ignorance on the part of labor and management ignorance. "Fair day's work" and "fair day's pay" — productivity enhancement is the answer to high wages/profits.

Peter Drucker says: The problem faced in developing countries is not a problem of "underdevelopment but rather of under management." Actually, productivity is the most serious challenge confronting management.

39.2.4 Perspectives on Productivity

Productivity – Manager's Perspective: Use "accounting ratios" for management. Usually interested in productivity measures that enable easy assessment of the present profitability of the company.

Productivity – Engineer's Perspective: Seek measures of physical assets and other resources. Examples: Production/hour, Man hours/unit, Material required/unit, material consumption, utilization, Space utilization. May fail to relate to overall productivity.

Productivity – Behaviorist's Perspective: View productivity of people in organization in terms of time they spend at work versus total time available — a misleading measure.

Productivity – Accountant's Perspective: "Costing and budgeting" approach to productivity. When budget figures, rather than optimum achievable values, are used as standards, this can create a false impression of high productivity.

Productivity – Economist's Perspective: Partial measures, such as "labor productivity," are employed by economists, along with total factor and total productivity, but again definitions do not agree.

39.3 Definition of Effectiveness and Efficiency

Productivity implies both effectiveness and efficiency in individual and organization performance.

• Effectiveness is the "achievement of objectives." It entails promptly achieving stated objectives.
• Efficiency is the "achievement of ends with the least amount of resources." Resources used to achieve objectives are weighted against what is actually accomplished.

🔑 Definition — Effectiveness: The achievement of stated objectives promptly.

🔑 Definition — Efficiency: The achievement of ends with the least amount of resources.

39.3 Types of Productivity

1. Partial Productivity
2. Total Factor Productivity
3. Total Productivity

Total-Factor Productivity: Ratio of "net output to sum of associated labor and capital (factor) inputs." Net output equals total output minus intermediate goods and services purchased.

Findings of Survey in Different Industries:

• Average: only 4.4 hours per day used productively
• 1.2 hours lost due to personal and other unavoidable delays
• Hours are simply wasted because of management's inability to effectively "plan and control" the worker's tasks.

Productivity Loss:

• Percent due to poor: "Planning and scheduling" of work.
• 25% due to: "Unclear and untimely instructions."
• Percent due to: "Inability to adjust staff size" and duties during "peak and valley workload periods."
• 25% due to: "Poor co-ordination" of material flow, unavailability of needed tools, excess travel time.

💡 Why this matters: Understanding the types of productivity and sources of productivity loss helps project managers identify specific areas for improvement and allocate resources effectively.

39.5 White-Collar Productivity

Productivity of white-collar workers is no less important than that of direct labor or manufacturing employees. It is usually the least known, least analyzed, and least managed of all factors of productivity. White-collar employees are productive only 50% of the time. The remainder is non-productive time and can be traced to personal delays (15%) and improper management (35%).

Examples of White Collar Waste:

• Poor staffing
• Inadequate communication
• Unproductive meetings and telephone conversations
• Poor scheduling
• Slack start and quiet times
• Lack of communication between functions
• Information overload

39.6 Critical Barriers/Problems to Productivity

• Family-controlled industry
• Earning easy money
• Monopolistic market, in some segments, some highly competitive
• Erratic inflow of orders
• Lack of productivity and quality culture
• Shortage of funds, low level of codification
• Automation not encouraged
• Low priority of market and commercial activities
• Poor after-service
• Complicated government policy, rules and regulations
• Poor infrastructure support/road transport
• Energy shortage
• Poor working conditions: light, ventilation, safety, housekeeping
• Non-availability of basic material components (to be imported)
• Unreliable suppliers

39.7 Causes of Productivity Decline in Organizations

• Inability to measure, evaluate, and manage productivity of white-collar employees — causes shocking waste of resources.
• Rewards and benefits given without requiring equivalent in productivity and accountability.
• Diffused authority and inefficiency in complex organizations, thereby causing delays and time lags.
• Organization expansion lowers productivity growth, resulting in soaring costs.
• Low motivation among rising numbers of affluent workers with new attitudes.
• Late deliveries caused by schedules disrupted by limited materials.
• Unresolved human conflicts and difficulties in teamwork, resulting in project inefficiencies.
• Legislative intrusions and antiquated laws, resulting in constrained "management options and prerogatives."
• Specialization in work processes resulting in monotony and boredom.
• Rapid technology changes and high costs, resulting in decline in new opportunities and innovation.
• Demand for leisure time causing disruption in operations.
• Project manager's inability to keep pace with the latest information and knowledge.

39.8 Productivity Improvement (PI)

How can projects improve their productivity?

Productivity is composed of:

• People
• Operations variables

To improve productivity, management needs to focus on two points:

1. Productivity does not just happen by "trying harder." It must be planned.
2. How do you plan for productivity, and what factors are involved?

Improvement means "increase the ratio of output of goods and services produced divided by input used to produce." The ratio can be increased by either increasing output, reducing input, or both.

Financial and social benefits of a "productivity improvement strategy" in a project should be greater than the "implementation cost" in the long run.

The task of the project manager is to evaluate those factors that have a bearing on productivity and take appropriate measures to use them effectively. To raise productivity and reduce cost, we must eliminate bad features in design and specifications that cause excessive work content.

39.8.1 Productivity Improvement Factors

Productivity improvement (PI) is not just "doing things better," but more importantly, it is "doing the right things better." Inter-relationships between labor, capital, and socio-organizational environment are important in a way that they are balanced and coordinated into an integrated whole.

Three Main Productivity Factor Groups:

• Job-related
• Resource-related
• Environment-related

39.9 Categories of Productivity Factors

There are two major categories of productivity factors:

• External (not controllable): Beyond the control of individual enterprise. Understanding of them can motivate certain actions that may change the enterprise's or project's behavior and its productivity in the long run.
• Internal (controllable): Within its control. The first step towards productivity improvement is to identify problem areas within these factor groups.

The Integrated Model of Project Productivity Factors (Figure 39.4) shows external factors (technology, economy, demographics, government/legal, social, ecological, customer/client, supplier/contractor) influencing internal factors (human resources, materials/equipment, systems/procedures, work methods/technology), which together affect project outputs.

39.10 Soft Factors

People: The principal resource and central factor in productivity improvement. All people in the organization have a role to play as workers, engineers, managers, entrepreneurs, and trade union members.

Each role has two aspects:

• Application
• Effectiveness

Application: The degree to which people apply themselves to their work. People differ not only in their ability but also in their will to work.

Law of Behavior: Motivation decreases if it is either satisfied or blocked from satisfaction. Workers may do their jobs working hard (no motivation), but even if they work to their full capacity, they would not be satisfied (motivation is blocked from satisfaction).

Motivation is basic to all human behavior and to efforts in productivity improvement. Material needs are predominant, but this does not mean that non-financial incentives are not effective or have no place.

The project manager should see what stimulates and maintains motivation to bring about changes in the attitude of managers, engineers, and workers, and develop a set of values conducive to higher productivity.

Workers' success in increasing productivity through:

• Rewards
• Improving recognition
• Involvement
• Learning opportunities
• Elimination of negative rewards

Execute effective incentive schemes for significant improvement in productivity. Wage incentives are related to the amount of change accomplished.

The project manager should work to encourage workers to apply their creative talents by taking special interest in their problems and promoting a favorable social climate.

2. Effectiveness: Effectiveness is the extent to which application of human effort brings desired results in output and quality. It is the ability to do a productive job, improved through:

• Training and development
• Job rotation and placements, systematic job progression (promotion)
• Career planning

Key approaches, methods and techniques to improve labor productivity:

• Wages and salaries
• Training and education
• Social security – pensions and health plans
• Rewards
• Incentive plans
• Participation or co-determination
• Contract negotiations
• Attitudes to work, to supervision and to change
• Motivation to higher productivity
• Co-operation
• Organization development
• Improved communications
• Suggestion systems
• Career planning
• Attendance
• Turnover
• Job security

Financial Incentives (Individual and Group): Individual plan is made to give financial incentives on the basis of individual performance.

Types of Individual Plan:

• Piece work plan
• Standard hour plan
• Measured day work plan
• Emerson plan

Group plan is made to give financial incentives on the basis of group performance.

Types of Group Plan:

• Scanlon plan
• Ruker plan
• Kaiser plan
• Tonnage plan
• Dollar sales plan
• Profit sharing
• Improshare

Fringe Benefits: Some intangible means of rewarding and encouraging management employees. These are referred to as "fringes" and include:

• Free Medical
• Insurance
• Free Air
• Fares
• Entertainment
• Company Car
• Telephone
• Subsidized education, etc.

Employee Promotion: Both financial and non-financial form of motivation. Upgradation of employee status is a natural way to recognize skill, knowledge, proficiency, and effort on the job.

Maslow's Hierarchy of Needs: Only dissatisfied needs can motivate workers to high productivity — physiological, safety/security, belongingness, self-esteem, self-actualization (realization of one's potential).

• Japanese: promotion based on seniority
• USA: promotion based on extraordinary performance
• Debatable issue

Job Enrichment: A non-financial motivation technique that provides:

• Variety in assigned tasks
• Employee autonomy and discretion in performing tasks
• Feedback on performance
• Herzberg's two-factor theory applied

Two Factors Theory: "Motivators" — factors leading to job satisfaction: achievement, recognition, nature of work, responsibility, growth, etc. Factors leading to dissatisfaction/avoidance are "Hygiene" factors: company policy, administration, supervision, pay, status.

Job Enlargement: Enlargement of responsibilities associated with the job. Enhanced scope and responsibility. Proponents say jobs get boring and monotonous, causing high absenteeism, high turnover, and low morale, with consequent low productivity. Example: Volvo Sweden — worker could stamp name on engine.

Job Rotation: Involves rotation of workers in different jobs for short periods of time to provide an "all-rounder" in the company's operations for which they were not originally hired:

• Relieves boredom through flexibility in job assignments.
• Not retraining conscious — an ongoing basis effort to provide opportunity to exercise freedom in staying on a job for a fixed period.

Workers Participation and Empowerment: Overcoming resistance to change through employee involvement in planning and implementing change. Mental and emotional involvement in groups encourages workers to contribute to group goals and share responsibility.

Workers Participation Approaches:

• Quality control circles
• Productivity quality teams
• Productivity action teams
• Productivity circles
• Productivity maintenance group
• Employee participation group

Skill Enhancement: Formalized techniques to increase skills needed to perform the job. Skill training is needed for employees when the employee's attitude is positive but abilities are low.

• In the information age, there is a great need for skill at all levels.

Management by Objectives (MBO): A managerial motivation technique that aids motivation through participation by having superior and subordinate managers jointly identify common goals, carefully define them, and together monitor progress towards achieving results for both employer and employee.

• In setting up goals, care must be taken:
  • Set simplistic goals
  • Set goals without adequate resources
  • Not set harsh goals that cause resentment
  • If properly administered, MBO can create joint goals and help in team building
  • MBO goals provide fairness to both employee and employer

Working Condition Improvement – Quality of Work Life (QWL): An often-emphasized but rarely applied technique that involves a detailed audit of working conditions, designing improved conditions of working, installing and maintaining improvements in working conditions.

Designing Improved Factors include:

• Temperature, light and humidity
• Noise
• Colors of surroundings
• Extent of handling hazardous material, parts or product
• Extent of manual handling of heavy items

Training: Seeks to achieve improved human productivity by increasing ability levels of the workforce. Seeks to meet demands of growth and change. Training may actually decrease total productivity initially.

Types of training:

• On-the-job training
• Apprenticeship
• Internship
• Outside courses
• Visitation training

Role Perception: Refers to the manner in which an individual defines his or her job. The type of effort an employee believes is essential for effective job performance. If workers see high or low productivity as a path to attainment of one or more of their personal goals in work situations, they will tend to be high or low producers.

Quality of Supervision: Concerned with the work of creating and maintaining environments in which people can accomplish goals efficiently and effectively. To improve supervision quality, supervisors must be trained in:

• Interpersonal skills
• Human management
• Group dynamics
• Other behavioral tools

Recognition: Management shows acknowledgment of an employee's outstanding performance in terms of improved productivity, ideas, or any act of good workmanship. They include:

• Pay raise
• Bonus
• Awards
• Certificate of appreciation
• Special highlights in company newsletter
• Special parking provision
• Engraving on plaque in cafeteria

Punishment: Punishment contingency attempts to decrease the likelihood of a particular behavior occurring by making punishment contingent on that behavior. Common punishment contingencies used in work organizations include:

• Disciplinary layoffs
• Transfer to undesirable jobs
• Withholding salary increases

Quality Circles: A group of employees who voluntarily cooperate to solve problems related to production, quality, work environment, maintenance scheduling, or anything that affects these areas.

Productivity and Quality Teams: Small groups of people doing similar tasks meet regularly to select, investigate, and solve problems related to workplace, products, and services. An effective means of improving employee morale, quality, and productivity in organizations. Team spirit, positive thinking, and philosophy of achieving excellence are three important characteristics of productivity and quality teams.

Zero Defects: Zero defects program attempts to improve quality by changing workers' attitudes. Their theme, "do it right first time," stresses error-free performance. It relies on workers to identify error-prone situations with the assumption that the people best prepared to eliminate errors are those who create them.

Time Management: A powerful technique, particularly for white-collar, supervisory, and management personnel. Time management involves minimization of wasteful elements of a person's administrative work, including:

• Interruptions by drop-in visitors (without appointment)
• Attending lengthy and unnecessary meetings that accomplish very little
• Inability to say "no" for some tasks
• Procrastination and lack of decisiveness
• Inability to delegate work
• Taking on much more than can be handled
• Lack of responsibility and authority to do certain jobs
• Delayed, inaccurate or inadequate information
• Taking orders from too many people
• Handling too many "crisis" situations
• Lack of organization of tasks by priority or target dates
• Lack of determination to complete tasks assigned
• Lack of organization on and around desk
• Unnecessary socialization
• Poor filing system
• Making unnecessary trips to people, departments, copy machines, etc.
• Excessive conversation time
• Too many rescheduling of meetings, personal engagements, etc.

To minimize these "time-wasters," time management applies simple, common-sensical but very effective programming rules to every item of work, one of which is: "never handle the same paper twice." Time management always improves human productivity. It is too often ignored, particularly by management people who preach productivity to their subordinates.

Flex Time: Employees are given freedom in determining their hours of work.

• Core time (hours when all employees must be at work)
• Flexible time (hours when employees can vary their time of arrival and departure)

Compressed Work Week: Working for the same number of hours but for fewer days per week (e.g., 8 hours for 5 days vs. 10 hours for 4 days).

Harmonization: Integration of the interests of stockholders, the board of directors, management at all levels, and all employees in a consistent manner both within and outside the physical boundaries of the organization.

🔑 Definition — Motivation: The basic force behind all human behavior and efforts in productivity improvement; it decreases if either satisfied or blocked from satisfaction.

🔑 Definition — Job Enrichment: A non-financial motivation technique that provides variety, autonomy, discretion, and feedback in assigned tasks.

🔑 Definition — Management by Objectives (MBO): A managerial motivation technique where superior and subordinate managers jointly identify, define, and monitor progress towards common goals.

🔑 Definition — Zero Defects: A program that attempts to improve quality by changing workers' attitudes, with the theme "do it right first time."

⭐ Key Takeaways

Competitiveness depends fundamentally on productivity, which is defined as the ratio of outputs to inputs with consideration of both quality and time. Productivity must be distinguished from production — production is the quantity of output, while productivity measures efficient resource utilization. There are three types of productivity: partial, total factor, and total productivity, and different professionals (managers, engineers, behaviorists, accountants, economists) view productivity from different perspectives. White-collar productivity is often the least managed factor, with employees being productive only 50% of the time. Productivity improvement requires planned intervention through both external (uncontrollable) and internal (controllable) factors, with people being the central resource. Key soft factors for improvement include motivation, financial and non-financial incentives, job enrichment, workers' participation, training, quality of work life, time management, and MBO. The project manager's task is to evaluate these factors and take appropriate measures for productivity enhancement.

🧠 Quick Revision Questions

1. What is the difference between production and productivity, and why is this distinction important in project management?
2. What are the three types of productivity, and how is total-factor productivity calculated?
3. What are the main causes of white-collar productivity loss, and what percentage of time do white-collar workers spend productively?
4. What are the two major categories of productivity factors, and how do they differ in terms of managerial control?
5. According to Herzberg's two-factor theory, what are "motivators" and "hygiene factors," and how do they relate to job enrichment and productivity improvement?

📘 Lecture 40 — Cost Management and Control in Projects

📖 Overview: This lecture explores the critical processes of cost management and cost control in project management. It introduces the Management Cost and Control System (MCCS) as a comprehensive framework encompassing both a planning cycle and an operating cycle. The lecture explains how to control costs through work authorization, cost account codes, budgets, and variance analysis, emphasizing the need to integrate time, cost, and performance.

🗂️ Topics Covered

The lecture covers cost management and cost control, the Management Cost and Control System (MCCS) as a two-cycle process (planning and operating), understanding control as verification and decision-making, the four phases of the operating cycle, the structure and function of cost account codes and work authorization forms, and the creation and management of budgets including management reserve and variance analysis using BCWS, BCWP, and ACWP.

📝 Lecture Summary

40.1 Cost Management

Cost management is the process whereby companies use cost accounting to report or control various costs of doing business. It describes the approach and activities of managers in short-range and long-range planning and cost decisions that incorporate value for the customer and lower costs of products and services. Managers make decisions on the amount and kind of material used, changes of plant processes, and changes in product designs, with information from the accounting system helping them make such decisions. In the context of a project, cost management involves the overall planning, co-ordination, control, and reporting of all cost-related aspects from “project initiation” to “operation and maintenance”. It is a process of identifying all costs associated with an investment, making informed choices about options that will deliver the best “value for money”, and managing those costs throughout the life of the project. Techniques like value management help improve value and reduce costs.

40.2 Cost Control

Cost control is equally important to all companies, regardless of size. Small companies generally have tighter monetary controls, mainly because of the risk with the failure of as little as one project, but with less sophisticated control techniques. Large companies may have the luxury to spread project losses over several projects, whereas the small company may have few projects. Cost control is not only the "monitoring" of costs and recording massive quantities of data, but also analyzing the data in order to take corrective action before it is too late. Cost control should be performed by all personnel who incur costs, not merely the project office. Cost control implies good cost management, which must include: cost estimating, cost accounting, project cash flow, company cash flow, direct labor costing, overhead rate costing, and others such as incentives, penalties, and profit-sharing.

40.3 Management Cost and Control System (MCCS)

Cost control is actually a subsystem of the Management Cost and Control System (MCCS) rather than a complete system per se. The MCCS is represented as a two-cycle process: a planning cycle and an operating cycle. The operating cycle is what is commonly referred to as the cost control system. Any cost control system is only as good as the original plan against which performance will be measured. It is more common for the plan to be at fault than the control system. The purpose of any MCCS is to establish policies, procedures, and techniques that can be used in the day-to-day management and control of projects and programs. The planning and control system must provide information that: gives a picture of true work progress; relates cost and schedule performance; identifies potential problems with respect to their sources; provides information to project managers with a practical level of summarization; and demonstrates that the milestones are valid, timely, and auditable.

As a tool for planning, the system must be able to: plan and schedule work; identify those indicators that will be used for measurement; establish direct labor budgets; establish overhead budgets; and identify management reserve. The project budget must be reasonable, attainable, and based on contractually negotiated costs and the statement of work. There are two categories of standards: Performance results standards are quantitative measurements (quality, quantity, cost, time-to-complete); Process standards are qualitative (personnel, functional, and physical factors relationships).

Management Cost and Control System (MCCS) planning activities include: contract receipt, work authorization for project planning, work breakdown structure (WBS), subdivided work description, schedules, planning charts, and budgets. MCCS planning is accomplished in one of these ways: one level below the lowest level of the WBS; at the lowest management level; or by cost element or cost account. A well-disciplined MCCS will produce results like: policies and procedures that minimize the ability to distort reporting; strong management emphasis on meeting commitments; and weekly team meetings with a formalized agenda. For MCCS to be effective, both the scheduling and budgeting systems must be disciplined and formal to prevent inadvertent or arbitrary budget or schedule changes. This does not mean the baseline budget and schedule are static, but that changes must be controlled and result only from deliberate management actions. Two new programs used with MCCS are zero-base budgeting (for better estimating) and design-to-cost (for a decision-making framework).

40.4 Understanding Control

Effective management during the operating cycle requires a well-organized cost and control system for immediate feedback. The requirements for an effective control system (for both cost and schedule/performance) include: thorough planning of the work; good estimating; clear communication; a disciplined budget and authorization; timely accounting; periodic re-estimation; and frequent comparison of actual progress to schedules and budgets. It is essential that management must compare the time, cost, and performance of the program to the budgeted time, cost, and performance, not independently but in an integrated manner. Being within one's budget serves no purpose if performance is only 75 percent. All three resource parameters must be analyzed as a group.

The first purpose of control is a verification process accomplished by comparing actual performance to date with predetermined plans and standards. This verifies that objectives have been translated into standards, standards are reliable, and meaningful budgets have been established. The second purpose of control is decision making. Three useful reports required by management are: the project plan, schedule, and budget; a detailed comparison between resources expended and those predetermined (including an estimate of work remaining); and a projection of resources to be expended through program completion.

🔑 Definition — Variance: Any schedule, technical performance, or cost deviation from a specific plan.

💡 Why this matters: The "iceberg syndrome" shows that problems become evident too late in the project to be solved easily, resulting in a very high cost to correct them. Possible cost reductions are usually available more readily in the early project phases but are reduced as we go further into the project life-cycle. Downstream, the cost for changes could easily exceed the original cost of the project.

40.5 Operating Cycle

The operating cycle of the MCCS is composed of four phases:

• Work authorization and release (phase II)
• Cost data collection and reporting (phase III)
• Cost analysis (phase IV)
• Reporting: customer and management (phase V)

These four phases, when combined with the planning cycle (phase I), constitute a closed system network. Phase II is considered as work release. Work is authorized via a work description or project work authorization form, which is a contract containing the narrative description, organization, and time frame for each WBS level. This multipurpose form releases the contract, authorizes planning, records detail description of the work, and releases work to the functional departments. Program management may issue a subdivided work description form to the functional units, which generally is not used for efforts longer than ninety days and must be "tracked" as if a project in itself. The work control center assigns a work order number to the subdivided work description form. A work order number is required for all in-house direct and indirect charging and serves as a cross-reference number for automatic assignment of the indentured work breakdown structure number.

40.6 Cost Account Codes

Since project managers control resources through line managers rather than directly, they control direct labor costs by opening and closing work orders. Work orders define the charge numbers for each cost account.

🔑 Definition — Cost Account: An identified level at a natural intersection point of the work breakdown structure and the Organizational Breakdown Structure (OBS) at which functional responsibility for the work is assigned, and actual direct labor, material, and other direct costs are compared with actual work performed for management control purposes.

Cost accounts are the focal point of the MCCS and may comprise several work packages, which are detailed short-span jobs or material items. The work authorization form specifically identifies the cost centers that are "open" for the charge number, the man-hours available for each cost center, and the operational time period. If a charge number is opened up at the department level, then the department manager has the right to subdivide the assigned man-hours among sections. If a cost center needs additional time or man-hours, a cost account change notice form must be initiated.

Cost data collection and reporting (phase III) accumulates actual cost for work performed (ACWP) and budgeted cost for work performed (BCWP) for each contract in detailed cost accounts. These are usually printed out monthly for all levels of the WBS. Weekly supplemental direct labor reports can also be printed. The weekly labor report lists all cost centers authorized to charge to the WBS element. Four categories of cost data are normally accumulated: labor, material, other direct charges, and overhead. Project managers can maintain reasonable control over labor, material, and other direct charges, while overhead costs are calculated yearly or monthly and applied retroactively.

40.7 Budgets

The project budget must be reasonable, attainable, and based on contractually negotiated costs and the statement of work. The basis for the budget is historical cost, best estimates, or industrial engineering standards. The budget must identify planned manpower requirements, contract allocated funds, and management reserve.

🔑 Definition — Management Reserve: The dollar amount established by the project office to budget for all categories of unforeseen problems and contingencies resulting in out-of-scope work to the performers.

Management reserve should not be used to cover up bad planning estimates or budget overruns. An undistributed budget is associated with contract changes where time constraints prevent necessary planning. An unallocated budget represents contract tasks not yet identified or authorized.

To calculate variances, three basic variables are defined: 📐 Formula:

• BCWS (Budgeted Cost for Work Scheduled): Budgeted amount for work scheduled to be accomplished in a given time period.
• BCWP (Budgeted Cost for Work Performed): Budgeted amount for completed work within a given time period (also called "earned value").
• ACWP (Actual Cost for Work Performed): Amount actually expended in completing the work accomplished within a given time period.

There are two primary methods of measurement:

• Measurable efforts: Discrete increments of work with a definable schedule for accomplishment, whose completion produces tangible results.
• Level of effort: Work that does not lend itself to subdivision into discrete scheduled increments, such as project support and project control.

Variances are used on both types of measurement. The cost variance compares deviations from the budget, while the scheduling variance provides a comparison between planned and actual performance. All budgets must be traceable through the budget "log," which includes: distributed budget, management reserve, undistributed budget, and contract changes.

⭐ Key Takeaways

Cost management and control are not just about monitoring expenses but involve analyzing data for timely corrective action. The Management Cost and Control System (MCCS) is a comprehensive framework that integrates a planning cycle with an operating cycle, where cost control is a subsystem. Effective control requires the integrated analysis of time, cost, and performance, not in isolation. Cost accounts are the focal point of MCCS, using work orders and cost account codes to track resources at the intersection of WBS and OBS. Finally, variances between BCWS, BCWP, and ACWP are essential for verifying budgets and schedules, with management reserve designated for unforeseen problems, not to cover poor planning.

🧠 Quick Revision Questions

1. What is the primary difference between cost management and cost control in a project context?
2. What are the two main cycles of the Management Cost and Control System (MCCS), and what is the primary purpose of each?
3. Why is it important to analyze time, cost, and performance together rather than independently?
4. What is a cost account, and what two organizational structures define its intersection point?
5. Define BCWS, BCWP, and ACWP. What is the purpose of comparing these three variables?

📘 Lecture 41 — Cost Management and Control in Projects

📖 Overview: This lecture focuses on project cost management and control, covering budgets, variances, and performance metrics. It explains how to track project financial health using earned value management, cost and schedule performance indices, and variance analysis, along with depreciation methods and ethical considerations.

🗂️ Topics Covered

The lecture covers budgets including management reserve and undistributed budget; variances and earned value concepts including BCWS, BCWP, and ACWP; cost and schedule variance calculations; cost performance index (CPI) and schedule performance index (SPI); variance analysis with the 50/50 rule; depreciation methods; parametric modeling estimation; analogous estimating; and ethics in project management.

📝 Lecture Summary

41.1 Budgets

The project budget, the final result of the planning cycle, must be reasonable, attainable, and based on contractually negotiated costs and the statement of work. The basis for the budget includes historical cost, best estimates, or industrial engineering standards. The budget must identify planned manpower requirements, contract allocated funds, and management reserve.

All budgets must be traceable through the budget "log," which includes distributed budget, management reserve, undistributed budget, and contract changes. Management reserve is the dollar amount established by the project office to budget for all categories of unforeseen problems and contingencies resulting in out-of-scope work. It should be used for tasks or dollars such as rate changes, not to cover up bad planning or budget overruns. There also exists the Undistributed budget, associated with contract changes where time constraints prevent incorporating the change into the performance budget, and the Unallocated budget, representing a logical grouping of contract tasks not yet identified.

💡 Why this matters: Understanding the different types of budgets ensures proper allocation of funds and prevents misuse of contingency funds.

41.2 Variance

Variance is defined as any schedule, technical performance, or cost deviation from a specific plan. Variances are used by all levels of management to verify the budgeting system and scheduling system. The budgeting and scheduling system variance must be compared together because cost variance compares deviations only from the budget and does not provide a measure of comparison between work scheduled and work accomplished. The scheduling variance provides a comparison between planned and actual performance but does not include costs.

There are two primary methods of measurement: Measurable efforts (discrete increments of work with a definable schedule producing tangible results) and Level of effort (work not lending itself to subdivision, such as project support and control).

41.2.1 Variances

To calculate variances, three basic variables are defined by Archibald:

• Budgeted cost for work scheduled (BCWS): The budgeted amount of cost for work scheduled to be accomplished plus the amount or level of effort scheduled in a given time period.
• Budget cost for work performed (BCWP): The budgeted amount of cost for completed work, plus budgeted for level of effort or apportioned effort activity completed within a given time period. This is sometimes referred to as "earned value."
• Actual cost for work performed (ACWP): The amount reported as actually expended in completing the work accomplished within a given time period.

🔑 Definition — Planned Value (PV): What the plan should be worth at this point in the schedule. Also BCWS.

🔑 Definition — Earned Value (EV): Physical work completed to date and within authorized budget for that.

The budget at completion (BAC) is the sum of all budgets (BCWS) allocated to the project, synonymous with the project baseline. The estimate at completion (EAC) identifies a realistic appraisal of the work when performed (EAC = cumulative actuals + estimate-to-complete).

📐 Formula: Variance at Completion (VAC) = BAC – EAC

📐 Formula: Cost Variance (CV) = BCWP – ACWP → A negative variance indicates a cost-overrun condition.

📐 Formula: Schedule Variance (SV) = BCWP – BCWS → A negative variance indicates a behind-schedule condition.

📐 Formula: Cost Variance Percentage = (CV / BCWP) × 100

📐 Formula: Schedule Variance Percentage = (SV / BCWS) × 100

📌 Example: Consider a project scheduled to spend $100K for each of the first four weeks. Actual expenditures at the end of week four are $325K. BCWS = $400K and ACWP = $325K. If BCWP is $300K, then the project is behind schedule (SV = $300K - $400K = -$100K) and overrunning costs (CV = $300K - $325K = -$25K).

Critical variances are established for each level of the organization. Permitted variances may depend on factors such as life-cycle phase, length of life-cycle phase, length of project, type of estimate, and accuracy of estimate.

COST PERFORMANCE INDEX (CPI)

41.2.2 Performance efficiency is calculated as a percentage of BCWP:

📐 Formula: Cost Performance Index (CPI) = BCWP / ACWP → If CPI = 1.0, perfect performance; if CPI > 1.0, exceptional performance; if CPI < 1.0, poor performance.

📐 Formula: Schedule Performance Index (SPI) = BCWP / BCWS → Same interpretation as CPI.

Variance Analysis

41.2.3 The cost and schedule performance index is used for trend analysis (three-month, four-month, or six-month moving averages) to predict trends and take corrective action. The goal of the cost account manager is to take action that will correct the problem within the original budget or justify a new estimation.

Five Questions must be addressed during variance analysis:

1. What is the problem causing the variance?
2. What is the impact on time, cost, and performance?
3. What is the impact on other efforts, if any?
4. What corrective action is planned or under way?
5. What are the expected results of the corrective action?

The "earned value" concept (same as BCWP) is a forecasting variable used to predict whether the project will finish over or under budget.

📌 Example: On June 1, the budget showed 800 hours should have been expended for a task, but only 600 hours appeared. Performance = (800/600) × 100 = 133 percent, indicating under-run. If actual hours were 1,000, performance = 80 percent, indicating overrun.

The 50/50 rule records half of the budget for each element at the time work is scheduled to begin, and the other half at the time work is scheduled to be completed. This eliminates the necessity for continuous determination of percent complete.

41.3 Depreciation

41.3.1 Depreciation is the technique used to compute the "estimated value" of any object after few years. Types include:

1. Straight line depreciation: Same amount depreciated (reduced) from cost each year.
2. Double-declining balance: First year - high deduction in value, twice the amount of straight line. Each year after that, deduction is 40% less than previous year.
3. Sum of year depreciation: If life is 5 years, total of 1-5 is 15. First year deduct 5/15 from cost, second year deduct 4/15, and so on.

41.3.2 Parametric Modeling Estimation

This is the use of mathematical models to make estimation. Two types:

• Regression Analysis: Mathematical model based upon historical information.
• Learning Curve: Model based upon the principle that cost/unit decreases as more work gets completed.

🔑 Definition — Parametric Modeling Estimation: Using mathematical models based on historical data to estimate project costs.

41.3.3 Analogous Estimating

An estimation technique with characteristics: estimation based on past project (historical information), less accurate compared to bottom-up estimation, top-down approach, takes less time compared to bottom-up estimation, and is a form of expert judgment.

41.3.4 Ethics

Ethics are standards of right and wrong that influence behavior. Right behavior is considered ethical and wrong behavior is considered unethical. Ethics are a major concern to both managers and employees. Ethics are a set of beliefs about right and wrong principles of conduct governing an individual or a group behavior that is fair and just, over and above obedience to laws and regulations. Ethics guide people in dealings with stakeholders and others to determine appropriate actions. A project manager often must choose between the conflicting interests of stakeholders.

⭐ Key Takeaways

The project budget must be traceable through a log, with management reserve for contingencies and undistributed budget for contract changes. Variances are measured using BCWS (planned), BCWP/earned value (performed), and ACWP (actual), with cost variance (CV = BCWP – ACWP) and schedule variance (SV = BCWP – BCWS) indicating overruns or delays. CPI and SPI measure performance efficiency, with values above 1.0 indicating exceptional performance. Variance analysis requires answering five key questions and can use the 50/50 rule to estimate percent complete. Depreciation methods include straight line, double-declining balance, and sum of years, while parametric modeling and analogous estimating are cost estimation techniques guided by ethical principles.

🧠 Quick Revision Questions

1. What is the difference between management reserve and undistributed budget?
2. How do you calculate cost variance and schedule variance, and what do negative values indicate?
3. What does a CPI of 0.85 indicate about project performance?
4. What are the five questions that must be addressed during variance analysis?
5. How does the 50/50 rule help in calculating earned value?

📘 Lecture 42 — Project Management Through Leadership

📖 Overview: This lecture examines leadership as a critical component of project management, distinguishing it from management. It explores how leaders get things done through people, the characteristics of effective leaders, and models like transformational leadership, vision creation, and the Leadership Grid. Understanding these concepts is essential for project managers who must inspire teams and navigate complex organizational dynamics.

🗂️ Topics Covered

The lecture covers four main areas: Leadership as a process of getting things done through people, including its tasks, effects, characteristics, and comparison to management; Transformational Leadership, including its evolution, goals, strategies, and results; Vision, including its purposes and characteristics of effective vision statements; and the Leadership Grid & Managerial Grid, which models leadership styles based on concern for production and people.

📝 Lecture Summary

42.1 Leadership

Leadership is a process of getting things done through people. Leaders work through others—like a quarterback moving a team toward a touchdown or a mayor getting citizens to support new policies—to reach specific goals. Leadership is not a science but an adventure, as success is never guaranteed. Leadership always means responsibility; the leader is the person others look to get the job done. Wearing a badge of office does not automatically make one a good leader, but it identifies you as someone others want to follow. No one is a finished leader; all leaders are explorers of the human mind, searching for the secrets of how to get things done through people.

The Tasks of Leadership Several common statements about leadership are examined:

• "The only people who lead have some kind of leadership job" – False. People without formal titles can also lead, and people with titles may not lead. You are a leader only when you are getting things done through other people.
• "Leadership is a gift. If you are born with it, you can lead. If you are not, you can't" – False. Leadership takes skill, and most people can learn these skills.
• "Leader is another word for boss" – Partly True. If "boss" means someone who pushes and orders others around, this is false. A leader is a boss in the sense of working with others to get the job done.
• "Being a leader in a Scout troop is like being a leader anywhere else" – True. The skills needed are very much the same.

What does a leader deal with? Every leader deals with just two things: the job and the group. The job is what needs to be done (not necessarily work; it could be a game or an idea). The group (e.g., a patrol) is the people who do the job. If there is no job, there is no need for a leader. If there is no group, there is no leadership.

The Job of a Leader A leader succeeds when two conditions are met:

1. The job gets done.
2. The group holds together.

Almost anybody with a whip and a mean temper can get a job done, but they usually destroy the group in the process. That is not leadership. Conversely, having fun without accomplishing the job is also not leadership. A leader must both get the job done and keep the group going.

What affects leadership? Leadership differs with:

• The leader: No leader can take over another's job and do it the same way.
• The group: A great football coach might struggle to lead an orchestra.
• The situation: A leader must change style depending on conditions (e.g., a group discussion vs. a fire emergency).

An effective leader must be alert to the reactions of group members, the conditions they are in, and their own abilities and reactions.

Leadership Develops Everyone is somewhere on a scale between having no leadership skills and having a complete set of them. Leadership can be developed over time.

Ten Characteristics of a Leader

1. Listening: Deep commitment to listening intently to others, including what is said and unsaid, and getting in touch with one's own inner voice.
2. Empathy: Striving to understand and empathize with others, assuming good intentions, and not rejecting people even when refusing certain behaviors.
3. Healing: The potential for healing one's self and relationships with others is a powerful force for transformation.
4. Awareness: General awareness and self-awareness strengthen the leader, helping understand ethics, power, and values.
5. Persuasion: Relying on persuasion rather than positional authority to make decisions, building consensus rather than coercing compliance.
6. Conceptualization: The ability to dream great dreams and think beyond day-to-day realities, balancing conceptual thinking with operational approaches.
7. Foresight: The ability to foresee likely outcomes by understanding lessons from the past, realities of the present, and consequences for the future.
8. Stewardship: Holding something in trust for another, with a commitment to serving the needs of others and using openness and persuasion rather than control.
9. Commitment to the growth of people: Believing people have intrinsic value beyond their tangible contributions, nurturing personal and professional growth.
10. Building community: Seeking to create community among those who work within a given institution.

These characteristics are natural in many individuals and can be enhanced through learning and practice.

Leadership vs. Management

The most dramatic differences are at the extremes: poor leaders are despots, while poor managers are bureaucrats. A good manager does things right; a leader does the right thing. Both are necessary and important. All first-class managers turn out to have quite a lot of leadership ability.

Top Ten Characteristics of a Great Manager

1. Time Management: Handling tasks and assignments in a timely manner; time must be budgeted wisely.
2. Communication Skills: Communicating clearly with fellow managers, employees, businesses, and customers.
3. Conflict Resolution: Listening, identifying issues, discussing solutions, agreeing on solutions, and following up.
4. Personal Traits: Being creative, adaptable, charismatic, understanding, confident, mentally stable, and a great listener.
5. Experience: Knowledge of job title, years in the field, and performance appraisals.
6. Goal Setting: Managing time wisely and focusing on specific goals, assigning tasks to employees.
7. Responsibility: Ensuring assignments, tasks, and deadlines are met, hiring appropriate people.
8. Organization: Keeping a clean and well-organized office, organizing projects and documents.
9. Leadership Skills: Being able to handle a group of people and lead them in the right direction.
10. Objective Views: Remaining non-judgmental, giving everyone a chance, avoiding favoritism.

Seven Personal Qualities Found in a Good Leader

1. Exemplary character: Trustworthy, honest, and of integrity; "walks the talk."
2. Enthusiasm: Passionate about work and role as leader, a source of inspiration and motivation.
3. Confidence: Appears confident to inspire confidence in others and draw out their best efforts.
4. Tolerance of ambiguity: Remains calm, composed, and steadfast to main purpose during uncertainties.
5. Analytical thinking: Views situations as a whole but can break them down into manageable steps.
6. Commitment to excellence: Maintains high standards and proactively raises the bar.

These seven characteristics are foundational to good leadership and can be developed and strengthened.

42.2 Transformational Leadership

Views of leadership are changing. Instead of thinking of leadership as aggressive action, it is now seen more as a way of thinking. Instructional leadership is "out" and transformational leadership is "in."

Evolution of Transformational Leadership The idea was first developed by James McGregor Burns in 1978 and later extended by Bernard Bass and others. It was based on studies of political leaders, Army officers, and business executives. There has been a shift in businesses from Type A to Type Z organizations, which reduce status differences, emphasize participative decision-making, and use "consensual" or "facilitative" power manifested through other people instead of over them.

Difference from Other Leadership Styles

Goals of Transformational Leadership

1. Helping staff develop and maintain a collaborative, professional school culture: Staff talk, observe, critique, and plan together; norms of collective responsibility and continuous improvement encourage teaching each other.
2. Fostering teacher development: Teachers' motivation for development is enhanced when they internalize goals for professional growth.
3. Helping teachers solve problems more effectively: Stimulates teachers to engage in new activities and put forth "extra effort"; helps staff work smarter, not harder.

Strategies of Transformational Leaders

• Visit classrooms daily; encourage teachers to visit each other.
• Involve staff in deliberating on school goals, beliefs, and visions.
• Help teachers work smarter by seeking different interpretations and placing individual problems in larger perspective.
• Use action research or school improvement teams to share power.
• Publicly recognize good work; write private notes of appreciation.
• Survey staff about wants and needs; use active listening.
• Let teachers experiment with new ideas; share research.
• Bring workshops to school; get teachers to share talents.
• Hire staff with commitment to collaboration; give option to transfer if not committed.
• Have high expectations for teachers and students.
• Use bureaucratic mechanisms to support teachers (funding, planning time, protection from excessive demands).
• Remind teachers they are responsible for all students.

Results of Transformational Leadership

• Transformational leadership has a sizable influence on teacher collaboration.
• Significant relationships exist between aspects of transformational leadership and teachers' attitudes and instructional behavior.
• Student achievement can be "remarkably improved."
• It should be part of a balanced approach, with "finding the right balance" being the challenge.

42.3 Vision

A good Vision serves three important purposes:

1. Clarifying "General direction for Change"
2. Motivates People to take action in the right direction, even if steps are painful.
3. Helps coordinate action of different people in a remarkably fast and efficient way.

Characteristics of Effective Vision

• Imaginable: Conveys a picture of what the future could look like; ambitious enough to force people out of comfort zones.
• Desirable: Appeals to long-term interests of most stakeholders; ignores or exploits no groups.
• Realistic: Not "pie-in-the-sky"; faith-filled yet realistic; linked to core competencies of organization.
• Focused: Clear enough to motivate action; not vague or ambiguous.
• Flexible: Allows initiative and modification; as change proceeds, the vision itself often changes.
• Communicable: Can be explained successfully within five minutes; articulates what is important, unique, and exciting.

Vision Statement A Vision Statement encompasses the desired future for your company. It provides a basis on which you and your team members can focus and work towards. Some look ahead a year or two, others ten years. A good vision draws up a "picture" of what an individual or group has in mind and causes those who read it to "see" the intended outcome.

42.4 The Leadership Grid & the Managerial Grid

Developed by Robert R. Blake and Jane S. Mouton, this leadership model focuses on task (production) and employee (people) orientations. The grid consists of two behavioral dimensions:

• Concern for production
• Concern for people

The Seven Managerial Grid Styles:

Grid Leadership Styles (Blake and Mouton's original five):

Grid Relationship Skills Grid theory translates into practice through seven relationship skills:

• Critique: Learning from experience by examining how behavior affects results
• Initiative: Taking action to exercise shared effort and support
• Inquiry: Questioning, seeking information, testing for understanding
• Advocacy: Expressing attitudes, opinions, ideas, and convictions
• Decision-Making: Evaluating resources, criteria, and consequences
• Conflict Resolution: Confronting and working through disagreements
• Resilience: Reacting to problems, setbacks, and failure

Grid theory makes behaviors tangible and objective, allowing teams to examine how behaviors help or hurt them and improve decision-making and conflict resolution skills.

💡 Why this matters: This lecture bridges the conceptual gap between managing tasks and leading people. For a project manager, understanding that leadership requires balancing concern for the project (task) with concern for the team (people) is essential for delivering successful projects while maintaining a cohesive, motivated team.

⭐ Key Takeaways

Leadership is fundamentally about getting things done through people while keeping the group intact—the job must be done, and the group must hold together. Leaders and managers differ in critical ways: managers have subordinates and focus on efficiency and control, while leaders have followers who choose to follow and focus on effectiveness, vision, and inspiration. Transformational leadership, which emphasizes collaboration, teacher development, and shared problem-solving, has been shown to improve outcomes by helping people work smarter, not harder. An effective vision must be imaginable, desirable, realistic, focused, flexible, and communicable to guide action and motivate people. The Leadership Grid reveals that the most effective leadership style (9,9 Team management) combines high concern for both production and people, demonstrating that task focus and people focus are not mutually exclusive but mutually reinforcing.

🧠 Quick Revision Questions

1. What are the two things every leader must achieve for successful leadership?
2. List four key differences between managers and leaders.
3. What are the three fundamental goals of transformational leadership?
4. What are the six characteristics of an effective vision?
5. In the Leadership Grid, what is the style characterized by high concern for both production and people called?

📘 Lecture 43 — Communication in the Project Management

📖 Overview: This lecture explores the critical role of communication in project management, emphasizing that 70-90% of a project manager's time is spent communicating. It covers the fundamentals of interpersonal communication, common barriers, and practical skills including writing, active listening, presentations, and conducting effective project meetings. Mastering these skills is essential for project success and career advancement.

🗂️ Topics Covered

The lecture covers communication fundamentals in project management, including the communication management plan and channels formula. It then examines interpersonal communication types (oral, written, nonverbal) and barriers such as emotions, filtering, and cultural differences. The communication process model is detailed, followed by writing skills and letter writing techniques. Active listening strategies, presentation planning, and running effective project meetings with proper time management are also addressed.

📝 Lecture Summary

43.1 Communication

The purpose of communication is to get your message across to others clearly and unambiguously. This involves effort from both the sender and receiver. Communication is only successful when both parties understand the same information as a result of the exchange. When unsuccessful, it causes breakdowns that hinder personal and professional goals. A University of Pittsburgh survey found that communication skills were the single most important factor in choosing managers, including written and oral presentations and ability to work with others.

In project management, Project Communication Management provides a critical link between "people, ideas, & information" at all stages in the Project Life Cycle. It aids in "decision making" and helps achieve project success. Approximately 70-90% of a typical Project Manager's time is spent in communication: ~45% listening, ~30% talking, and ~50% in meetings.

The Communication Management Plan defines how and when various stakeholders receive information and communicate with each other. Memos, emails etc. are non-formal communication types. The total number of communication channels between stakeholders is given by the relationship: N(N - 1)/2 (where N is the number of stakeholders). This means if there are 10 stakeholders, that project will have 45 channels of communication.

One page business letter that took 10 min to dictate cost between $13.60 and $20.52 in 1996. Poor writing costs even more since it wastes time, effort and jeopardizes goodwill.

Characteristics of Effective Communication include: Fostering an "Open Communication Climate", Committing to "Ethical Communication", Understanding "Dynamics of Intercultural Communication", Becoming Proficient in Communication Technology, Using an "Audience Centered Approach", and Creating & Processing Messages Efficiently.

In series of transmission from one person to next, message becomes less and less accurate. Poor retention of information is another serious problem, necessitating repeating the message and using several channels.

Techniques to Improve Organization Communication include: Emphasis on Teamwork, Improve Reporting System, Focus on Employees Participation & Involvement, Improve Management System, Change Organizational Culture, Flatter Hierarchy, Cross Functional Teams, and Fewer Control.

The function of communication is to provide form in which ideas and purposes can be expressed as Message. Vocabulary, language, & knowledge play an important role in sender's ability to encode.

🔑 Definition — Communication: The process of getting your message across to others clearly and unambiguously, requiring effort from both sender and receiver. 📐 Formula: N(N - 1)/2 → Total number of communication channels between stakeholders, where N is the number of stakeholders. 📌 Example: With 10 stakeholders, the project will have 10(10-1)/2 = 45 communication channels.

💡 Why this matters: Understanding communication channels helps project managers recognize the complexity of information flow and the need for structured communication plans.

43.2 Interpersonal Communication

Interpersonal communication is the process of sending and receiving information between two or more people. Communication is interpersonal when the people involved are contacting each other as persons, on a personal level.

Effective Communication requires face-to-face contact in an environment of "Openness & Trust". Several aspects include Talking, Listening, Reading, Writing and more formalized aspects such as conducting meetings, interviews etc.

Elements of Good Talking: Voice Quality, Talking Style, Word Choice and Vocabulary.

Three Broad Types of Interpersonal Communication: Oral, Written, and Nonverbal.

Oral Communication consists of all forms of spoken Information and is the most preferred type of Communication used by Managers. Managers prefer face-to-face & telecommunication to written communication because it permits immediate feedback.

Written Communication includes Letters, memos, policy manuals, reports, forms, & other documents used to share Information in Organization.

Types of Nonverbal Communication: Body Language, Space, Time, Para language, Color, and Layout and Design.

🔑 Definition — Interpersonal Communication: The process of sending and receiving information between two or more people on a personal level.

43.3 Barriers against Effective Interpersonal Communication

Emotions: Sometimes when people communicate, the receiver can feel how the sender perceives the subject matter. Extreme emotions hinder effective communication because the message may be misinterpreted. It's best to avoid responding when upset or angry.

Filtering: The sender manipulates the information to appear favorable to the receiver. This may mislead the receiver.

Overloaded with Information: Too much information about the same subject matter may be confusing. The human brain can only process so much information; overloading exceeds our processing capacity.

Defensiveness: Humans tend to refuse mutual understanding when they feel threatened or disadvantaged. Defensiveness involves attacking what the sender tells you, sarcastic remarks, questioning motives, or being overly judgmental.

Cultural Difference: Culture may be a huge hindrance for effective interpersonal communication. When two people with different cultures communicate, they may misunderstand each other's true meaning.

Jargon: Not everyone understands each other's jargon words. Jargon should be avoided when talking to someone unfamiliar with you or your organization.

43.3.1 The importance of removing barriers

Problems with communication can pop-up at every stage of the communication process (sender, encoding, channel, decoding, receiver, feedback, context) and create misunderstanding.

SOURCE: As the source, you need to be clear about why you're communicating and what you want to communicate. The information should be useful and accurate.

MESSAGE: The information that you want to communicate.

ENCODING: Transferring information into a form that can be sent and correctly decoded. Success depends on conveying information clearly and anticipating sources of confusion (cultural issues, mistaken assumptions, missing information). Knowing your audience is critical.

CHANNEL: Messages are conveyed through channels—verbal (face-to-face, telephone, videoconferencing) and written (letters, emails, memos, reports). Different channels have different strengths and weaknesses.

DECODING: Successful decoding involves taking time to read carefully or listen actively. Errors in encoding and decoding can cause confusion.

RECEIVER: Each individual enters the communication process with ideas and feelings that influence their understanding. Consider these before delivering your message.

FEEDBACK: Verbal and nonverbal reactions to your message. Pay close attention as it allows you to be confident your audience understood.

CONTEXT: The situation in which your message is delivered, including surrounding environment or broader culture (corporate culture, international cultures).

43.4 WRITING SKILLS

Many people are intimidated by writing. Once something is in written form, it cannot be taken back. Written communication is more concrete than verbal, with less room for error. This presents challenges including spelling, grammar, punctuation, writing style, and wording.

The Importance of "Style": Basic tips include avoiding slang words, avoiding abbreviations (unless defined), steering away from symbols (such as ampersands), avoiding clichés, using brackets to play down words and dashes for emphasis, spelling names correctly, expressing numbers less than 10 as words and 10 or greater as figures, using quotation marks for direct speech and publication titles, and keeping sentences short.

"The Elements of Style" by Strunk and White is recommended as a clear, concise guide for writing improvement.

43.5 Letter Writing

Address the letter to an individual. Begin with a personal name and end with an appropriate closing like 'Sincerely yours'. If no individual name is available, use a more generic closing like 'With kindest regards'.

The first paragraph should provide an overall summary showing why the letter is relevant. The body explains the reason for correspondence with relevant background and current information, flowing logically.

The closing is the final impression. End with an action point such as 'I will call you later this week to discuss this further'.

The Importance of Careful Proofing: Check the letter thoroughly when completed. Use grammar and spell check, but don't place total faith on the computer. Have a dictionary and thesaurus to double-check. Ensure the document is clear, concise, well-organized, and contains necessary information using facts. Outline the course of action expected and close appropriately with contact information.

43.6 Active Listening

Poor interpersonal communication skills (including active listening) reduce productivity because you lack tools to influence, persuade, and negotiate. Lines of communication must be open between people who rely on each other.

1. Start by Understanding Your Own Communication Style: Good communication requires self-awareness. Understanding your personal style helps create good impressions. By becoming more aware of how others perceive you, you can adapt more readily.

2. Be an Active Listener: People speak at 100 to 175 words per minute (WPM), but can listen intelligently at up to 300 WPM. Since only part of our mind pays attention, mind drift occurs. Active listening involves listening with a purpose—to gain information, obtain directions, understand others, solve problems, share interest, see how another feels, show support. Try repeating words mentally to reinforce the message.

3. Use Nonverbal Communication: Use nonverbal behaviors (facial expressions, smiles, gestures, eye contact, posture) to raise the channel of interpersonal communication. This shows you are listening actively.

4. Give Feedback: What someone says and what we hear can be amazingly different. Personal filters, assumptions, judgments, and beliefs can distort what we hear. Repeat back or summarize to ensure understanding. Restate what you think you heard and ask, "Have I understood you correctly?" If responding emotionally, say so and ask for more information.

43.7 Presentation Planning Checklist

Presentation: Does your introduction grab attention and explain objectives? Are main points in logical sequence and flowing well? Do main points need visual aids? Does closing summarize clearly and concisely? Is the conclusion strong and tied to the introduction?

Delivery: Are you knowledgeable about the topic? Are notes in order? Where and how will you present? Have you visited the site? Have you checked visual aids?

Appearance: Dress and groom appropriately for audience expectations. Practice paying attention to body language and posture.

Visual Aids: Are they easy to read and understand? Are they tied to the points? Can they be seen from all areas?

43.8 Running Effective Project Meetings

Meetings are wonderful tools for generating ideas and managing group activity, but can fail without adequate preparation and leadership.

The Importance of Preparation: Designate a meeting time allowing all participants to prepare adequately. Make yourself available for questions. As meeting leader, make a meeting agenda with detailed notes.

Managing a Meeting: Choose the right participants—those who can contribute, are good decision-makers and problem-solvers. Keep participants to a maximum of 12. Invite people with necessary information. When an item is resolved, make clear who is responsible. Summarize action to be taken and include in meeting minutes.

Time Keeping: Start on time. Don't recap for latecomers. State a finish time and don't over-run. Arrange agenda in order of importance so important items aren't omitted. Finish early if everything is achieved.

Issuing Minutes: Minutes record decisions and actions agreed. They provide a record and a review document for next meeting to measure progress. This makes them a useful disciplining technique as individual performance gets high visibility.

⭐ Key Takeaways

Communication is the most critical skill for project managers, consuming 70-90% of their time, with the formula N(N-1)/2 calculating communication channels between stakeholders. Effective communication requires overcoming barriers like emotions, filtering, information overload, defensiveness, cultural differences, and jargon through the communication process model. Written communication demands careful proofing and style awareness, while active listening—listening at up to 300 wpm with purpose—prevents costly misunderstandings. Finally, effective project meetings require preparation, proper participant selection, strict time management, and documented minutes for accountability.

🧠 Quick Revision Questions

1. What percentage of a project manager's time is typically spent on communication, and how is this time distributed across listening, talking, and meetings?
2. What is the formula for calculating the number of communication channels, and how many channels exist for a project with 10 stakeholders?
3. List six types of barriers to effective interpersonal communication discussed in the lecture.
4. What are the key elements of the communication process model, and what role does feedback play in ensuring successful communication?
5. What are the three broad types of interpersonal communication, and why do managers prefer oral communication over written communication?

📘 Lecture 44 — Project Risk Management

📖 Overview: This lecture introduces the fundamental concepts of project risk management, including definitions, components, and the systematic process for dealing with uncertainty in projects. It emphasizes the importance of proactive risk management to anticipate and mitigate potential issues before they adversely impact project goals.

🗂️ Topics Covered

The lecture covers what risk is and its primary components, including probability and impact, as well as tolerance of risk profiles. It then explores risk management processes, categories of risk, risk planning, risk identification, risk assessment, and risk handling methods. The discussion also includes decision-making under certainty, risk, and uncertainty, along with the risk management process cycle.

📝 Lecture Summary

44.1 What are the Risks?

Risk is a measure of the probability and consequence of not achieving a defined project goal. It involves the notion of uncertainty; for example, "Can the computer be produced within budgeted cost?" A probability measure can be used, such as a 0.15 probability of not meeting a launch date. However, the consequences or damage associated with occurrence must also be considered. A goal with a probability of occurrence of only 0.05 may present a much more serious risky situation than a goal with a probability of 0.20, if the consequences of not meeting the first goal are more than four times more severe. Risk is not always easy to assess since probability and consequence are usually not directly measurable and must be estimated by statistical or other procedures. 💡 Why this matters: Understanding that risk is a combination of both probability and impact allows project managers to prioritize risks that have low probability but catastrophic consequences over high-probability, low-impact risks.

🔑 Definition — Risk: A measure of the probability and consequence of not achieving a defined project goal.

44.2 Components of Risk

Risk has two primary components for a given event:

• Probability of occurrence of that event
• Impact of the event occurring (amount at stake)

Conceptually, risk for each event can be defined as a function of likelihood and impact: Risk = f(likelihood, impact). As either the likelihood or impact increases, so does the risk.

Another element is the cause of risk — the hazard. Risk can also be represented as: Risk = f(hazard, safeguard). Risk increases with hazard but decreases with safeguard. The implication is that good project management should be structured to identify hazards and allow the development of safeguards to overcome them.

44.3 Tolerance of Risk

The three commonly used classifications of tolerance for risk are: the risk averter (or avoider), the neutral risk taker, and the risk seeker (or lover). Utility is the amount of satisfaction or pleasure an individual receives from a payoff.

With the risk averter, utility rises at a decreasing rate, meaning when more money is at stake, satisfaction or tolerance diminishes. A risk averter prefers a more certain outcome and will demand a premium to accept risk.

With the risk lover, satisfaction increases when more money is at stake (increasing slope). A risk lover prefers the more uncertain outcome and may be willing to pay a penalty to take a risk.

📌 Example: A risk averter would prefer a guaranteed $50,000 profit over a 50% chance of earning $100,000. A risk lover would choose the 50% chance.

44.4 Risk Management

Risk management is the act or practice of dealing with risk. It includes planning for risk, assessing (identifying and analyzing) risk issues, developing risk handling options, and monitoring risks to determine how they have changed. Proper risk management is proactive rather than reactive.

📌 Example: An activity in a network requires new technology development. The schedule indicates six months, but engineers think nine months. A proactive manager develops a Risk Handling Plan now. A reactive manager does nothing until the problem occurs, losing valuable time.

44.5 Categories of Risk

The Project Management Institute categorizes risks as follows:

• External–unpredictable: Government regulations, natural hazards, acts of God (outside PM's control)
• External–predictable: Cost of money, borrowing rates, raw material availability (outside PM's control)
• Internal (nontechnical): Labor stoppages, cash flow problems, safety issues (may be within PM's control)
• Technical: Changes in technology, design issues, operations/maintenance issues (relates to utilization of technology)
• Legal: Licenses, patent rights, lawsuits, subcontractor performance, contractual failure

Decision-making falls into three categories:

• Decision-Making under Certainty: All necessary information is available, and outcomes can be predicted with high confidence. A payoff matrix will have one dominant strategy with no probabilities assigned.
• Decision-Making under Risk: No single dominant strategy exists; probabilities must be assigned to each state of nature. Outcomes can be described within established confidence limits from well-defined experimental distributions.
• Decision-Making under Uncertainty: Meaningful assignments of probabilities are not possible. The decision-maker has four basic criteria from which to make a management decision, depending on the project type and the PM's risk tolerance.

The Risk Management Process includes several related actions:

• Risk planning: Developing and documenting an organized, comprehensive strategy for identifying and tracking risk issues, developing handling plans, and assigning adequate resources.
• Risk assessment: Identifying and analyzing program areas and critical technical process risks to increase the likelihood of meeting cost, performance, and schedule objectives. Risk identification examines program areas to identify documented risk; risk analysis examines each identified issue to refine the description, isolate the cause, and determine effects.
• Risk handling: Identifies, evaluates, selects, and implements options to set risk at acceptable levels. Options include assumption, avoidance, control (mitigation), and transfer.
• Risk monitoring: Systematically tracks and evaluates the performance of risk handling actions against established metrics and provides inputs for updating strategies.

🔑 Definition — Risk management: The act or practice of dealing with risk, including planning, assessment, handling, and monitoring.

44.6 Risk Planning

Risk planning is the detailed formulation of a program of action for the management of risk. It is the process to:

• Develop and document an organized, comprehensive, and interactive risk management strategy
• Determine methods to execute the program's risk management strategy
• Plan for adequate resources

The result is often the Risk Management Plan (RMP). The RMP is the roadmap that tells the project team how to get from where the program is today to where the program manager wants it to be. The key to writing a good RMP is to provide necessary information so the program team knows the objectives, goals, and risk management process.

44.7 Risk Assessment

Risk assessment is the problem definition stage of risk management that identifies, analyzes, and quantifies program issues in terms of probability and consequences. The components—identification and analysis—are performed sequentially with identification being the first step.

Risk identification begins by compiling the program's risk issues. Risk analysis is a technical and systematic process to examine identified risks, isolate causes, determine relationships to other risks, and express the impact in terms of probability and consequence.

44.8 Risk Identification

The second step in risk management is to identify all potential risk issues. Methods for identifying risk are numerous. Most sources are either objective or subjective.

• Objective sources: Recorded experience (lessons learned files, program documentation evaluations, current performance data)
• Subjective sources: Experiences based upon knowledgeable experts (interviews, subject matter experts)

Expert judgment techniques include:

• Delphi method: A panel of experts is selected without face-to-face interaction. Each expert makes anonymous predictions, receives composite feedback, and then makes new predictions. The process repeats as necessary.
• Nominal group technique: Allows face-to-face contact. A panel generates ideas in writing, lists them, discusses each, and then prioritizes them mathematically.

Risks can also be classified as:

• Business risk: Provides opportunities of profit and loss (competitor activities, inflation, customer response)
• Insurable risk: Provides only a chance for loss (direct property damage, indirect consequential loss, legal liability, personnel)

44.9 Risk Handling

Risk handling includes specific methods and techniques to deal with known risks, identifies who is responsible, and provides cost and schedule estimates for reducing the risk. Options fall into four categories:

• Risk assumption (retention): "I know the risk exists and am aware of the possible consequences. I accept the risk and its impact should it occur."
• Risk avoidance: "I will not accept this option because of potentially unfavorable results."
• Risk control (mitigation): "I will take necessary measures to control this risk by continuously reevaluating it and developing contingency plans."
• Risk transfer: "I will share this risk with others through insurance or warranty, or transfer the entire risk to them."

⭐ Key Takeaways

Risk is a function of both the probability of an event occurring and its impact, and it decreases as safeguards are implemented against identified hazards. Project managers have different tolerances for risk (averse, neutral, or seeking), which influences their decision-making. The risk management process is a continuous, proactive cycle of planning, assessment, identification, analysis, handling, and monitoring, not a reactive problem-solving activity. Risks can be categorized by source (external, internal, technical, legal) and by decision-making environment (certainty, risk, or uncertainty), which determines the analytical approach. Expert judgment techniques like the Delphi method and nominal group technique are valuable but require awareness of potential biases.

🧠 Quick Revision Questions

1. What are the two primary components of risk for a given event, and how do they relate conceptually to the overall risk?
2. What are the three classifications of tolerance for risk, and how does utility change with money at stake for a risk averter versus a risk lover?
3. What are the four main options for handling risk, and what does each option represent from the project manager's perspective?
4. What is the difference between decision-making under risk and decision-making under uncertainty?
5. What are the key differences between the Delphi method and the nominal group technique for expert judgment in risk identification?

📘 Lecture 45 — Project Procurement, Contract Management, and Ethics in Project Management

📖 Overview: This lecture explores the strategic and operational aspects of project procurement, including procurement cycles, contract types, and contract administration. It also addresses the critical role of ethics in project management, providing a framework for ethical decision-making and professional conduct. Understanding these concepts is essential for managing project resources, mitigating risks, and ensuring project success.

🗂️ Topics Covered

This lecture is organized into four main sections: Procurement, which defines procurement and outlines its strategies and environments; Procurement Cycles, which details the requirement, requisition, solicitation, and award cycles; Types of Contracts, which explains various contract types like Fixed-Price, Cost-Plus, and Incentive contracts; and Ethics in Project Management, which discusses ethical origins, a code of ethics for project managers, and ways to improve ethical performance.

📝 Lecture Summary

45.1. Procurement

Procurement is defined as the acquisition of goods or services. It is a process involving two parties with different objectives interacting in a given market segment. Good procurement practices increase corporate profitability by leveraging quantity discounts, minimizing cash flow problems, and seeking quality suppliers. Procurement is often centralized to standardize practices and lower paperwork costs.

There are two basic procurement strategies: a corporate procurement strategy, which relates specific procurement actions to the corporate strategy, and a project procurement strategy, which relates actions to the project's operating environment. Project strategies can differ from corporate strategies due to constraints, resource availability, or customer requirements. For example, corporate strategies might favor multiple vendors, while project strategies may dictate sole-source procurement.

Procurement planning involves selecting one of four primary objectives: procure all goods/services from a single source, procure from multiple sources, procure only a small portion, or procure none.

A critical factor is the procurement environment. The macro environment includes general external variables like recessions, inflation, and unemployment that influence how and when procurement occurs. For example, a foreign corporation in a country with high unemployment might use only domestic suppliers.

The microenvironment is the internal environment of the firm, including policies and procedures that govern procurement. This environment involves a procurement/contracting system with five cycles:

• Requirement cycle: definition of the project's boundaries.
• Requisition cycle: analysis of sources.
• Solicitation cycle: the bidding process.
• Award cycle: contractor selection and contract award.
• Contract administration cycle: managing the subcontractor until completion.

These cycles can be conducted in parallel, especially requisition and solicitation.

45.2. Procurement Cycles

The first step, the requirement cycle, includes defining the project need, developing the Statement of Work (SOW), specifications, and Work Breakdown Structure (WBS), performing a make or buy analysis, laying out milestones and schedule, cost estimating including life-cycle costing, and obtaining authorization to proceed.

The SOW is a narrative description of the work to be accomplished and/or the resources to be supplied. To prevent companies from subcontracting almost all work, SOWs now often require identification of the talented internal resources committed to the project.

Specifications are written, pictorial, or graphic information that describe, define, or specify the services or items to be procured. There are three types:

• Design specifications: Detail what is to be done in terms of physical characteristics. The risk of performance is on the buyer.
• Performance specifications: Specify measurable capabilities the end product must achieve. The risk of performance is on the contractor.
• Functional specifications: The seller describes the end use of the item to stimulate competition among commercial items at a lower cost. This is a subset of performance specifications, and the risk is on the contractor.

Feasible procurement alternatives include make or buy, lease or buy, buy or rent, and lease or rent.

🔑 Definition — Make or buy analysis: A decision-making process that compares the costs and benefits of producing an item internally versus purchasing it from an external supplier.

Factors for a make decision include: less costly (but not always), easy integration of operations, utilize idle capacity, maintain direct control, maintain design/production secrecy, avoid unreliable suppliers, and stabilize the workforce. Factors for a buy decision include: less costly (but not always), utilize skills of suppliers, small volume requirements, limited capacity or capability, augment the labor force, maintain multiple sources, and indirect control.

📐 Formula: Breakeven Point for Lease vs. Rent → The point in time where the total cost of leasing equals the total cost of renting. Lease Cost = Fixed Cost + (Variable Cost per Day * Days) Rent Cost = Variable Cost per Day * Days Breakeven Point = Fixed Cost / (Rent Cost per Day - Lease Variable Cost per Day)

📌 Example: A company can rent equipment for $100 per day or lease it for $60 per day plus a one-time cost of $5000. The breakeven point in days is: $5000 / ($100 - $60) = $5000 / $40 = 125 days. If the firm needs the equipment for more than 125 days, leasing is more cost-effective.

Requisition Cycle: Once requirements are identified, a requisition form is sent to procurement. This cycle includes evaluating/confirming specifications, confirming sources, reviewing past performance of sources, and producing a solicitation package.

The solicitation package is prepared in the requisition cycle but used in the solicitation cycle. It should be identical for all suppliers to ensure a level playing field. A typical package includes: bid documents, a listing of qualified vendors, proposal evaluation criteria, bidder conferences, and change request management.

Solicitation Cycle: The critical element is selecting the acquisition method. The three common methods are:

• Advertising: Sealed bids are used with no negotiations; the award goes to the lowest bidder.
• Negotiation: Price is determined through bargaining. This can involve a Request for Information (RFI), Request for Quotation (RFQ), or Request for Proposal (RFP). The RFP is the most costly for the vendor. The process can be competitive or noncompetitive (sole-source procurement).
• Small purchases: For items like office supplies.

The three major factors of negotiations are: compromise ability, adaptability, and good faith. Negotiations should be planned for, including developing objectives (min-max positions), evaluating your opponent, defining strategy and tactics, gathering facts, performing a price/cost analysis, and arranging "hygiene" factors (e.g., location, timing).

There should be a postnegotiation critique, both internally and with losing bidders, to explain why they did not win. This can help prevent bid protests, which are most common on government contracts.

Award Cycle: This cycle results in a signed contract. Basic elements of most contracts include:

• Mutual agreement: There must be an offer and acceptance.
• Consideration: There must be a down payment.
• Contract capability: The contract is binding only if the contractor has the capability to perform.
• Legal purpose: The contract must be for a legal purpose.
• Form provided by law: The contract must reflect the contractor's legal obligation.

The objective of the award cycle is to negotiate a contract type and price that results in reasonable contractor risk and provides the greatest incentive for efficient performance.

The two most common contract forms are:

• Completion contract: The contractor must deliver a definitive end product. The contract is complete upon delivery and acceptance.
• Term contract: The contractor must deliver a specific "level of effort" (e.g., man-days) over a specific period. The contractor is under no further obligation once the effort is performed, irrespective of technical accomplishments.

A definitive contract follows normal contracting procedures. However, if work must begin immediately, a letter contract (or letter of intent) can be used. This is a preliminary written instrument authorizing the contractor to begin work, with a "not to exceed" face value.

45.3. Types of Contracts

Before analyzing contract types, key terminology must be understood:

• Target cost or estimated cost: The cost level the contractor will most likely obtain under normal conditions.
• Target or expected profit: The profit value negotiated and set forth in the contract.
• Profit ceiling and profit floor: The maximum and minimum values of total profit.
• Price ceiling or ceiling price: The amount of money for which the customer is responsible, usually greater than the target cost.
• Sharing arrangement or formula: The cost responsibility split between customer and contractor for each dollar spent, typically applying to overruns or under-runs.
• Point of total assumption: The point where the contractor assumes all liability for additional costs.

Contracts range from cost-plus types, where the contractor's profit is fixed and risk is minimal, to lump sum or turnkey types, where the contractor assumes full responsibility for all costs and profits.

There are five general types of contracts to consider:

1. Fixed-Price (FP) or Lump-Sum:

• The contractor must carefully estimate the target cost and perform the work for the negotiated value.
• Risk: High for the contractor. If costs are underestimated, profit is reduced or eliminated.
• Advantage: Maximum protection for the owner on ultimate cost.
• Disadvantage: Requires a long period for bid preparation. Owner must know exact requirements at the time of bidding.

2. Cost-Plus-Fixed-Fee (CPFF) or Cost-Plus-Percentage-Fee (CPPF):

• The cost may vary but the fee (profit) is fixed (CPFF) or a percentage of cost (CPPF).
• Risk: Low for the contractor, who only agrees to use "best efforts". Good and poor performance are rewarded equally.
• Advantage: Quick preparation of bids, encourages quick completion. Provides maximum flexibility for the owner.
• Disadvantage: No financial assurance of ultimate cost; higher costs may result due to lack of financial incentive.

3. Guaranteed Maximum-Shared Savings (GMSS):

• The contractor is paid a fixed fee and reimbursed for actual costs, but only up to a ceiling figure (the "guaranteed maximum"). Savings below the ceiling are shared between owner and contractor.
• Risk: Shared between owner and contractor.
• Advantage: Combines the advantages of lump sum and cost-plus contracts. Establishes a maximum price early and protects the owner from being overcharged. Both parties have a real incentive to complete the project at the lowest possible cost.

4. Fixed-Price-Incentive-Fee (FPIF):

• A fixed-price contract with a provision for adjusting total profit by a formula, agreed upon in advance, that depends on the final total cost.
• Risk: Shared between owner and contractor. Provides an incentive for the contractor to reduce costs and increase profit.
• Use: When project requirements are firmly established.

5. Cost-Plus-Incentive-Fee (CPIF):

• A cost-plus contract with a provision for adjusting the fee by a formula that compares total project costs to the target cost.
• Risk: More risk is placed on the contractor compared to CPFF, forcing them to plan ahead and keep costs down.
• Use: For long-duration or R&D type projects.

💡 Why this matters: The choice of contract type is a critical strategic decision that allocates risk between the buyer and seller. It directly impacts the contractor's behavior, incentive for cost control, and the final project cost.

45.4. Ethics

Ethical Origins: Ethics in project management has several origins.

• Societal Ethics: Standards of behavior based on a society's values, legal rules, norms, and mores. These vary from one society to another.
• Professional Ethics: Values and standards used by a group of managers in the workplace, applied when decisions are not clear-cut ethically (e.g., practices of physicians or lawyers).
• Individual Ethics: The values of an individual, resulting from their family and upbringing. Values are basic convictions of what is "right and wrong."

Ethics codes and policies reflect top management's desires in a project-based organizational culture. Project managers should behave ethically to avoid harming others. Managers are responsible for "protecting and nurturing resources" in their charge. Leadership, culture, and incentive compensation plans help shape individual ethical behavior. There is strong evidence that ethical managers benefit in the longer run.

Ethical decisions involve a normative judgment, implying something is "good or bad, right or wrong." For example, should you buy goods from overseas firms that hire children?

Code of Ethics for Project Managers: The Project Management Institute has developed a code of ethics. Its key articles state that Project Managers shall:

Article I (Personal Conduct):

• Maintain high standards of personal and professional conduct.
• Accept responsibility for their actions.
• Undertake projects only if qualified by training or experience.
• Maintain professional skills at the state-of-the-art.
• Advance the integrity of the profession.
• Support the code and professional society.

Article II (In Their Work):

• Provide project leadership to maximize productivity and minimize costs.
• Apply state-of-the-art management tools.
• Treat all team members fairly.
• Protect project team members from harm.
• Provide suitable working conditions.

Article III (Relations with Employers and Clients):

• Act as faithful agents or trustees.
• Keep confidential information.
• Disclose any circumstances that could lead to a conflict of interest.
• Not give or accept gifts of more than nominal value.
• Be honest and realistic in reporting project cost, schedule, and performance.

Article IV (Responsibilities to the Community):

• Protect the safety, health, and welfare of the public.
• Seek to extend public knowledge of the project management profession.

How Firms Can Improve Their Social Responsiveness (Ethical Performance):

• Establish and publish their own Code of Ethics.
• Appoint Ombudsmen to review corporate past behavior.
• Protect whistle-blowing (when an employee discloses an illegal, immoral, or unethical action).
• Implement training programs for ethical sensitivity.
• Control compliance through a corporate social audit.
• Demonstrate commitment through leadership.
• Involve personnel at all levels.

⭐ Key Takeaways

The most critical lessons from this lecture are that project procurement is a strategic process involving five cycles, and the selection of a contract type is the primary mechanism for allocating risk between the buyer and the seller. Understanding the differences between Fixed-Price, Cost-Plus, and Incentive contracts is essential, as each type creates different incentives for the contractor regarding cost control and performance. Furthermore, a project manager must adhere to a strict code of ethics, which governs their conduct with team members, clients, and the public. Finally, factors like make-or-buy analysis, the use of different specification types, and the negotiation process are all integral to successful procurement management.

🧠 Quick Revision Questions

1. What are the five cycles of the procurement/contracting system, and what is the primary activity of each?
2. What is the formula for calculating the breakeven point between leasing and renting equipment, and why is it important?
3. A project requires a new software module. The buyer is unsure of the exact technical specifications but knows the operational results needed. What type of specification should be used, and who bears the performance risk?
4. What are the five main types of contracts, and how does the allocation of risk differ between a Fixed-Price contract and a Cost-Plus-Fixed-Fee contract?
5. According to the Code of Ethics for Project Managers, what are a project manager's primary ethical responsibilities regarding information from an employer or client?