π 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:
- 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.
- Project Charter: Authorizes the existence of the project and outlines the project objectives.
- Preliminary Project Scope Statement: Provides a description of the major project deliverables, project objectives, project assumptions, project constraints, and a statement of work.
- Project Scope Management Plan: Provides a description of how the stated project objectives will be developed within the detailed Project Scope Statement.
- 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.
-
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.
-
Requested Changes: Changes to the project management plan processed through Integrated Change Control.
-
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
-
What is the difference between scope, objectives, and goals, and why is it important to explicitly identify items "out of scope"?
-
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)?
-
What are the five processes of project scope management, and what is the primary purpose of each process?
-
What are the five inputs required for defining project scope, and what are the three key outputs produced from this process?
-
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:
- 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.
- 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.
- 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.
- 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.
- 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
- What is the key difference between product scope and project scope?
- List the five main processes that comprise project scope management.
- What is a Work Breakdown Structure (WBS), and what are its components called at the lowest level?
- What is the primary goal of the scope verification process?
- 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
- What are the three types of time estimates used in PERT, and how do they differ from the single estimate used in CPM?
- Define the critical path and explain why it is crucial for project control according to the two key points mentioned in the lecture.
- What is slack time, and how can project managers use it to optimize resource allocation?
- What is the purpose of a dummy activity in network scheduling, and what does its representation look like?
- How does GERT differ from PERT in terms of handling project uncertainties and branching?