Study guide: Project Management Foundations

📋 Course Outline

1. Project Foundations and Organization
2. Project Management Process Groups
3. Roles in Project Management
4. Scope Management Fundamentals
5. Requirements Collection and Prioritization
6. Scope Definition and Control
7. Activity Scheduling and Estimation
8. Activity Duration Estimation
9. Schedule Development and Control
10. Project Cost Management
11. Quality Management Foundations
12. Planning and Controlling Project Quality
13. Project Human Resource Management
14. Stakeholder Communication Management
15. Project Risk Management
16. Procurement Management
17. Procurement Planning and Contract Types
18. Procurement Administration and Closure

📖 1. Project Foundations and Organization

🔑 Key Concepts & Definitions

• Project: A temporary effort to create a unique product, service, or result, with a definite start and end.
• Stakeholder: An individual, group, or organization positively or negatively affected by a project or its product.

• Program: A group of related projects managed together because managing them independently can be challenging.

• Portfolio: A group of programs and individual projects implemented to achieve a specific strategic business goal.
• Project management office: A centralized department that supports and manages projects by providing policies, methodologies, templates, training, tools, resources, and project managers.
• Business value: The total sum of tangible and intangible elements of a business, including assets, equity, utility, goodwill, reputation, brand recognition, public benefit, and trademarks.

★ Must-know

📌 Operational work is ongoing, whereas project work has a definite end.

• Project management comprises the process groups initiating, planning, executing, monitoring and controlling, and closing, as well as the knowledge areas integration, scope, time, cost, quality, human resources, communication, risk, procurement, and stakeholder management.

📌 Project objectives are defined in the project charter, and a project is considered complete when its objectives are met; it is terminated if they are not met.

Further detail

• Management by objectives (MBO) establishes clear, concise, well-articulated, realistic objectives, reviews them periodically, and implements corrective actions when deviations occur.

• Project constraints can involve:

  • time
  • cost
  • risk
  • scope
  • quality
  • resources
  • customer satisfaction

📌 A change to one project constraint can affect other constraints, so the project manager evaluates change impacts through integrated change control.

💡 Memory Hook

Ongoing operations continue; projects have a definite end.

📖 2. Project Management Process Groups

🔑 Key Concepts & Definitions

• Progressive elaboration: The continual refinement of estimates and scope.

★ Must-know

• The Initiating Process Group formally authorizes a project and may start project selection; its outputs include the project charter, identified stakeholders, and a stakeholder management strategy.

• The Planning Process Group develops the project management plan and project documents, assesses the knowledge areas, and provides a roadmap for accomplishing the project.

• The Executing Process Group completes the work in the latest revision of the project management plan, focusing on managing people, following processes, and distributing information.

• Monitoring and Controlling measures project performance against the project management plan and handles change requests, corrective actions, preventive actions, and defect repair.

📌 A project is closed only after closure activities are completed and formal sign-off confirms that the product is acceptable; the project manager can then release resources involved in closing it.

Further detail

• 🔄 The process sequence is:

  1. Start by initiating the project.
  2. Plan the project.
  3. Act by executing the project.
  4. Check and act by monitoring and controlling the project.
  5. End by closing the project.

• The project manager is assigned during the Initiating phase, and high-level planning at this stage can include a high-level WBS, order-of-magnitude estimates, and high-level risk identification.

• Project planning is iterative, and the plan should accommodate changes while its level of detail and planning effort remain appropriate to the project’s needs.

💡 Memory Hook

Start → Plan → Act → Check and Act → End.

📖 3. Roles in Project Management

★ Must-know

• The project manager is accountable for project success or failure and integrates project components into a cohesive whole that meets customer needs.

• The program manager manages related projects together to achieve results not obtainable by managing each project separately and ensures selected projects support organizational strategic goals.

• The sponsor advocates for the project, secures support and funding, provides the project statement of work and initial-scope information, and grants the project manager authority as outlined in the project charter.

📌 In a matrix organization, the functional manager shares direction of individuals’ work with the project manager; in a project-centric organization the project manager directs the work, while in a functional organization the functional manager directs it.

Further detail

• The project manager is assigned no later than project initiation, helps write the project charter, and is in charge of the project but not necessarily its resources.

• The portfolio manager governs the projects or programs in a portfolio at the executive level, selecting and managing them for organizational value and return on invested resources.

• During project closing, the sponsor provides formal acceptance of deliverables and supports collection of historical project records.

• The project team can help identify stakeholders, requirements, constraints, assumptions, WBS elements, activity dependencies, estimates, and risks, and execute the project management plan.

📖 4. Scope Management Fundamentals

🔑 Key Concepts & Definitions

• Scope management: Defines the work required for a project and ensures that all of that work—and only that work—is done.
• Product scope: What the customer wants from the product.
• Project scope: The work, including planning, coordination, and management activities, performed to deliver the product scope.

★ Must-know

• The scope management plan covers scope planning, execution, and control and is created as part of project management planning, not as a separate scope management process.

Further detail

• The scope management plan should define in advance how scope will be determined, managed, and controlled, and the project manager should seek formal approval for a clearly defined scope.

• Scope requirements should be gathered from all stakeholders, because relying on only a few stakeholders or only the sponsor can lead to an incorrect scope definition.

• Gold plating, or adding extras beyond the agreed project scope, is not allowed.

• Scope changes require integrated change management that considers effects on time, cost, risk, quality, resources, and customer satisfaction; the change originator updates a change request form and the change is tracked in a change control register.

• For a software project, product scope can be a new workflow application that fulfills internal and external customer requirements, assessed by comparing the resulting application with its documented requirements and project scope statement.

• At the end of a project or phase, completed work is compared with the scope baseline in the project management plan to assess whether scope has been completed successfully.

• A scope management plan answers how scope will be achieved, which tools and organizational resources are needed, and how scope will be managed and controlled throughout the project.

• The scope management plan may be iterated during planning: the project manager first decides how to define scope, then uses more complete project information to plan execution and control, with later planning such as human resources planning potentially prompting revisions.

💡 Memory Hook

Do all the work in scope—and only that work.

📖 5. Requirements Collection and Prioritization

🔑 Key Concepts & Definitions

• Requirements Traceability Matrix: Links requirements to project objectives and other requirements, helping assess proposed scope changes and ensure strategic goals are met.

★ Must-know

• Collect Requirements begins with identifying stakeholders, records them in a stakeholder register, and then gathers and documents their detailed requirements using methods suited to the project and stakeholders.

• Requirements can be gathered through interviews, focus groups, facilitated workshops, brainstorming, nominal group technique, Delphi technique, mind maps, affinity diagrams, questionnaires and surveys, observation, and prototypes.

• Balancing stakeholder requirements involves prioritizing requirements, resolving conflicts, and adjusting competing demands of scope, time, cost, quality, resources, risk, and customer satisfaction to meet project objectives.

Further detail

• Requirements may concern product or process needs, including quality, business processes, regulatory requirements, compliance, and project management, and should support stated objectives rather than be included merely because someone wants them.

• Historical records and lessons learned from similar projects help identify relevant requirements, team expectations, and scope-definition mistakes to avoid.

📌 In the Delphi technique, experts provide anonymous responses that are compiled and recirculated for review until consensus, whereas nominal group technique ranks ideas during a meeting following brainstorming.

📌 Group decisions may use unanimity, dictatorship, majority support from more than half the members, plurality by the largest number of supporters when no majority exists, or consensus acceptable to the group.

• Requirements documentation should be clear and unambiguous, and stakeholders should confirm that collected requirements meet the stated objectives.

📖 6. Scope Definition and Control

🔑 Key Concepts & Definitions

• Project scope statement: An output of Define Scope that can include product scope, project scope, deliverables, product acceptance criteria, out-of-scope activities, constraints, and assumptions.
• Scope baseline: The approved project scope statement, WBS, and WBS dictionary; deviations require a change request and approved changes update these components.

• Work Breakdown Structure: A hierarchical decomposition of the complete project scope and its deliverables into manageable work packages.
• WBS dictionary: A description of the work for each work package that can specify its start, schedule milestones, acceptance criteria, and other information.

★ Must-know

• Define Scope uses the requirements documentation, project charter, and information about risks, assumptions, and constraints to determine what is and is not included in the project and its deliverables.

📌 Verify Scope obtains customer acceptance of completed deliverables, including interim deliverables, whereas Close Project or Phase obtains final acceptance of the project or phase as a whole.

• Control Scope compares completed work with the scope baseline, identifies deviations, recommends corrective or preventive action, and initiates change requests for changes that must pass Integrated Change Control.

Further detail

• Product analysis examines the product objectives and description supplied by the customer and sponsor to identify tangible deliverables.

📌 A WBS is created top-down with team involvement; each level is a smaller piece of the level above, the first level is completed before further decomposition, and it includes no deliverables outside the project.

• A deliverable can be treated as a work package when it can be estimated realistically and confidently, completed quickly and without interruption or further information, and potentially outsourced or contracted.

📖 7. Activity Scheduling and Estimation

🔑 Key Concepts & Definitions

• Rolling wave planning: Details activities only when needed to manage the work in an approaching project life-cycle phase, rather than planning every detail at the start.

★ Must-know

• Define Activities breaks WBS work packages into activities that can be estimated, scheduled, monitored, and managed, using the scope baseline and an available project team.

• PDM relationship types are:

  • Finish-to-Start
  • Start-to-Start
  • Finish-to-Finish
  • Start-to-Finish

• Padding estimates is unacceptable; estimates should be reviewed periodically for achievability, padding, and risks, and the project manager is responsible for providing accurate and feasible estimates.

Further detail

• A schedule management plan establishes who participates in scheduling, the planning approach and tools, measurement units, baseline and variance responses, change control, and reporting requirements.

📌 A milestone is an interim deliverable or schedule point, not the duration or timeline of an activity.

• Network diagram methods include:
  • Precedence Diagramming Method (PDM)
  • Arrow Diagramming Method (ADM)
  • Graphical Evaluation and Review Technique (GERT)

📌 Mandatory dependencies follow the natural flow of work or may be contractually required, discretionary dependencies are selected by the project manager and team and can be changed, and external dependencies depend on parties outside the project.

📌 A lead allows a successor activity to start before its predecessor is complete, whereas a lag is waiting time inserted between activities.

• Activity estimates are more accurate when based on the WBS, prepared by the people doing the work, and informed by historical information.

• Estimate to Complete should be recalculated periodically to ensure adequate time, funds, and resources remain available for the project.

📖 8. Activity Duration Estimation

★ Must-know

• Activity duration estimates are made after activities have been defined and sequenced and their resource types and quantities identified.

📌 Padding is an arbitrary extra time or cost added because an estimator lacks information, whereas reserves are calculated to address identified risks and unknowns through risk management.

• One-point estimating assigns a single estimate to an activity and may rely on expert judgment, historical information, or a guess; it can hide risks, encourage padding, reduce buy-in, and undermine trust.

📌 Analogous estimating uses expert judgment and historical information from similar projects or activities, whereas parametric estimating uses relationships between variables and activity outcomes derived from historical or other data.

• Three-point estimating uses optimistic, pessimistic, and most likely estimates to produce a risk-based expected duration using an average or weighted average such as PERT.

Further detail

• Estimators should ideally be the people doing the work, although project team members familiar with the work often estimate durations.

• Padding is less likely when:

  • estimators have a WBS
  • estimators have a WBS dictionary
  • time and cost reserves are calculated
  • risks and unknowns are identified

💡 Memory Hook

Padding hides uncertainty; reserves address identified risk.

📖 9. Schedule Development and Control

🔑 Key Concepts & Definitions

• Critical Path: The longest path in a project network diagram.

★ Must-know

📌 Total float is delay possible without delaying the project end date; free float is delay possible without delaying a successor’s early start; project float is delay possible without delaying an externally imposed completion date.

• Monte Carlo analysis simulates project outcomes using a network diagram and optimistic, pessimistic, and most likely activity estimates to estimate completion-date and cost probabilities, critical-path likelihood, and overall project risk.

Further detail

📌 A near-critical path has a duration close to the critical path, and the closer their durations are, the greater the project risk.

📐 Formula - Float can be calculated as $\text{Float} = LS - ES$ or $\text{Float} = LF - EF$, and both formulas give the same result.

• Critical-path activities have zero float, while delayed projects or projects with imposed dates can have negative float.

• Fast tracking performs critical-path activities in parallel that were planned in series and can cause rework, increase risk, and require more communication.

• Crashing compresses a schedule through cost and schedule trade-offs while maintaining project scope, and it always increases cost.

• Resource leveling produces a resource-limited schedule and can lengthen the schedule and increase cost and other constraints.

📖 10. Project Cost Management

🔑 Key Concepts & Definitions

• Life Cycle Costing: Considers the whole life of a product rather than only the project cost.
• Value Analysis: Systematically identifies functions, assigns values to them, and seeks less costly resources and activities without reducing performance or scope.

★ Must-know

📌 Variable costs change with the amount of work, whereas fixed costs do not vary with the amount of work.

📌 Direct costs can be attributed to project work, whereas indirect costs are overheads that cannot be apportioned to a specific project or activity and may serve multiple projects.

• Bottom-up estimating estimates costs for individual activities or work packages, rolls them up into control units, and then combines them into the overall project estimate.

📌 Contingency reserves address known risks remaining after risk responses, whereas management reserves address unknown risks.

• The cost budget equals the cost baseline plus management reserves.

Further detail

• A rough order of magnitude estimate is generally made during project initiation and typically ranges from -50% to +50%, while a budget estimate is made during planning and ranges from -10% to +25%.

• A definitive estimate is a refined project cost estimate for which some project managers use a range of ±10% and others use -5% to +10% from actual.

• 🔄 Cost aggregation rolls costs up through these levels:

  1. activity costs into work package costs
  2. work package costs into control account costs
  3. control account costs into project costs

📌 The 50/50 rule credits an activity as 50% complete when it begins and the remaining 50% when it finishes; the 20/80 rule assigns 20% at the start and 80% at completion, while the 0/100 rule assigns no credit until completion.

💡 Memory Hook

Activity costs roll up to work packages, control accounts, then the project.

📖 11. Quality Management Foundations

🔑 Key Concepts & Definitions

• Quality: The degree to which a project fulfills its requirements.
• Quality Management: Creates and follows policies and procedures to ensure that a project meets the defined customer needs it was intended to meet.
• Continuous Improvement: Continuous improvement, or Kaizen, is the ongoing search for small improvements in a process; “Kai” means “change” and “Zen” means “for the better.”
• Total Quality Management: Total Quality Management (TQM) encourages companies and employees at every organizational level to continuously improve product quality and business practices.
• Marginal Analysis: Identifies the point where the benefits from improving quality equal the incremental cost of achieving that quality.
• Just in Time: Just in Time (JIT) has suppliers deliver raw materials when they are needed, reducing inventory to nearly zero and avoiding unnecessary high inventory costs.

★ Must-know

• The project manager holds ultimate responsibility for product or project quality, while the entire organization also has quality responsibilities.

Further detail

📌 Philip Crosby described quality as “conformance to requirements” and popularized prevention over inspection and “zero defects”; Joseph Juran defined quality as “fitness for use” and advocated top-management involvement in quality issues.

• W. Edwards Deming is associated with the 14 points of quality management and the Plan-Do-Check-Act cycle.

• Gold plating adds value or scope beyond what the customer requested based on the team’s impression of what the customer values, and it is not recommended because it can create a gap in customer expectations.

• Poor quality leads to:

  • increased costs
  • low morale
  • low customer satisfaction
  • increased risk
  • rework
  • schedule delays

💡 Memory Hook

Crosby’s conformance to requirements contrasts with Juran’s fitness for use.

📖 12. Planning and Controlling Project Quality

★ Must-know

📌 Plan Quality defines project quality and how to achieve it; Perform Quality Assurance checks whether planned processes are followed; Perform Quality Control examines actual deliverables against planned quality.

• Plan Quality identifies relevant organizational and industry practices, standards, and quality requirements for the project, product, and project management work, and produces a Quality Management Plan.

📌 Control limits are set from organizational quality standards and calculated at plus or minus three standard deviations; specification limits express customer expectations or contractual requirements and are stated by customers.

📌 A process is out of statistical control if a data point falls outside control limits or if a non-random pattern occurs, such as seven non-random points on one side of the mean, even within the limits.

Further detail

• Plan Quality uses these inputs:

  • organizational process assets
  • enterprise environmental factors
  • stakeholder register
  • scope baseline
  • schedule baseline
  • cost baseline
  • risk register

• The cited standards and their purposes are: ISO 9000 supports organizational quality procedures and their use, OSHA sets worker-safety standards in plants, the CISG governs international sales transactions

📌 Additional project-specific standards and procedures must not violate other relevant standards, and quality effort should be appropriate to project needs and balanced against other project constraints.

• The seven basic quality tools are:

  • cause-and-effect diagrams
  • flowcharts
  • histograms
  • Pareto charts
  • run charts
  • scatter diagrams
  • control charts

• A Pareto chart orders results from most frequent to least frequent and applies the 80/20 rule: 80% of problems are attributed to 20% of causes.

💡 Memory Hook

Control limits describe process variation; specification limits describe customer requirements.

📖 13. Project Human Resource Management

★ Must-know

• Team development stages are:

  • forming
  • storming
  • norming
  • performing
  • adjourning

• A Human Resource Plan covers:

  • roles and responsibilities
  • project organization charts
  • staffing management plan

• The conflict sources in descending frequency are:

  • schedule
  • project priorities
  • resources
  • technical opinions
  • administrative procedures
  • cost
  • personality

📌 Confronting solves the underlying problem in a win-win way, compromising gives each party partial satisfaction in a lose-lose outcome, withdrawal postpones or avoids a decision, smoothing emphasizes agreement, collaborating incorporates multiple viewpoints, and forcing imposes one viewpoint at another's expense.

Further detail

• The staffing management plan includes:
  • staff acquisition
  • resource calendars
  • staff release
  • staff training needs
  • rewards and recognition
  • compliance
  • safety

📌 A responsibility assignment matrix cross-references team members with activities or work packages, while a RACI chart clarifies assignments as Responsible, Accountable, Consult, or Inform.

• A project sponsor provides financial resources and may be a customer, senior manager, or another party.

• Project manager power types and their bases are:

  • formal: position
  • reward: giving rewards
  • penalty: imposing penalties
  • expert: technical or project-management expertise
  • referent: charisma, fame, respect, or being liked

💡 Memory Hook

Forming → Storming → Norming → Performing → Adjourning.

📖 14. Stakeholder Communication Management

🔑 Key Concepts & Definitions

• Stakeholder Register: An output of Identify Stakeholders that compiles information about stakeholders.

★ Must-know

• The project manager spends 85%–90% of their time communicating, and communication-related issues are among the most frequent problems faced by project managers.

• 🔄 Stakeholder management proceeds by:

  1. identifying all stakeholders
  2. determining their requirements
  3. determining their expectations
  4. determining their interests
  5. determining their level of influence
  6. planning how to communicate with them
  7. executing communication
  8. managing their expectations and influence

• Stakeholder analysis identifies stakeholders and assesses their impact or influence using the project charter, past-project records, brainstorming, interviews, and names suggested by existing stakeholders.

• The Communications Management Plan is a component of the Project Management Plan and documents how communication will be managed and controlled.

📌 Interactive communication involves two or more people exchanging information and responding, push communication sends information without expecting feedback, and pull communication places information centrally for recipients to retrieve.

📐 Formula - The number of communication channels among $N$ people is $\frac{N(N-1)}{2}$.

Further detail

• Power/interest grids and salience models classify stakeholders by factors such as authority, impact, influence, or requirements to guide what, how, and when to communicate.

• The stakeholder management strategy, an output of Identify Stakeholders, determines whether stakeholders are managed individually or in groups and accounts for both positive and negative involvement.

• About 55% of communication is nonverbal, and pitch and tone of voice also help convey a message.

• The project manager spends about 85–90% of their time communicating.

• Performance reports include: status reports on current performance against the baseline, progress reports on work accomplished, trend reports, forecasts, variance reports, earned value reports, lessons-learned documentation

💡 Memory Hook

Identify stakeholders → determine needs and influence → plan communication → communicate → manage expectations.

📖 15. Project Risk Management

🔑 Key Concepts & Definitions

• Risk: An uncertain event or condition that can affect project objectives positively or negatively.
• Risk Register: A living project document updated throughout the project lifecycle that records risks, potential responses, root causes, and updated risk categories.

★ Must-know

📌 Risk tolerance is the degree or level of risk considered acceptable, whereas a risk threshold is the specific point at which risk becomes unacceptable.

• The six risk management processes are:
  • Plan Risk Management
  • Identify Risks
  • Perform Qualitative Risk Analysis
  • Perform Quantitative Risk Analysis
  • Plan Risk Responses
  • Monitor and Control Risks

📌 Threat response strategies are avoid, mitigate, and transfer; opportunity strategies are exploit, enhance, and share; acceptance can apply to both threats and opportunities.

Further detail

• Risk categories include external risks such as government, regulatory, environmental, and market risks; internal risks such as service, customer satisfaction, cost, and quality risks; technical risks from technology changes; and unforeseeable risks, estimated at about 9–10%.

• Business risk can result in either gain or loss, whereas pure (insurable) risk results only in loss.

• Risk identification techniques include:

  • document reviews
  • brainstorming
  • the Delphi technique
  • interviewing
  • root cause analysis
  • SWOT analysis
  • checklist analysis
  • assumption analysis
  • diagramming techniques

• Quantitative risk analysis can use expected monetary value analysis, Monte Carlo analysis, and decision trees to assess risk exposure and support estimates of reserves, costs, schedules, and the likelihood of meeting project objectives.

• Risk response planning documents residual and secondary risks, contingency and fallback plans, response owners, risk triggers, contracts, and contingency reserves.

• Monitoring and controlling risks includes tracking triggers and residual risks, evaluating responses, identifying further responses, recommending corrective actions, reassessing risks, conducting risk audits, analyzing reserves, and updating project records.

💡 Memory Hook

Plan, identify, analyze, respond, then monitor risks.

📖 16. Procurement Management

★ Must-know

• The four procurement processes are:

  • Plan Procurements
  • Conduct Procurements
  • Administer Procurements
  • Close Procurements

• Procurement contracts must be formal, and a change management procedure is the means of adding an activity that is not already included in the contract.

• Planning procurements involves: performing a make-or-buy analysis, creating the procurement management plan, creating a statement of work for each procurement, selecting contract types, preparing procurement documents, determining source-selection criteria

• Making is favored when: the organization has an idle plant or workforce, the work involves proprietary information or procedures, the organization wants to retain control

Further detail

• In centralized contracting, one procurement department and manager handle procurements for multiple projects; in decentralized contracting, a procurement manager is assigned full-time to one project and reports to its project manager.

• Procurement documents may include:

  • a Request for Proposal (RFP)
  • an Invitation for Bid (IFB)
  • a Request for Quotation (RFQ)

• A procurement process can take one to three months because sellers need time to review project needs and respond.

💡 Memory Hook

Buy to reduce constraints; make when idle capacity, proprietary work, or control favors in-house delivery.

📖 17. Procurement Planning and Contract Types

🔑 Key Concepts & Definitions

• Procurement statement of work: Describes all work and activities the seller must complete, including meetings, reports, and communications, and should be clear, complete, and concise.
• Procurement management plan: Describes the planning, execution, and control of procurement after the organization decides to obtain products or services from outside sources.

★ Must-know

📌 A procurement statement of work describes what the final product should accomplish, a functional statement of work emphasizes the end purpose or results rather than specific procedures, and a design statement of work specifies precisely what work is to be done.

• The three broad contract categories are:
  • fixed price
  • time and material
  • cost reimbursable

📌 Fixed-price contracts suit well-defined requirements and sufficient competition to establish a fair price, whereas cost-reimbursable contracts suit uncertain scopes whose costs cannot be estimated accurately enough for fixed pricing.

• Under a fixed-price contract, the seller bears additional costs above the agreed price, so the buyer has the least cost risk.

Further detail

• Design statements of work are most commonly used in construction and equipment purchasing, while performance and functional statements of work are used for work not done before, such as information systems, information technology, and research and development.

• A time-and-material contract pays the seller per hour or per item and is often used for services whose level of effort cannot be determined when the contract is awarded.

• A purchase order is a simple fixed-price contract signed by one party, making it unilateral rather than bilateral.

📌 A cost-plus-fixed-fee contract pays actual costs plus a negotiated fee fixed before work begins, whereas a cost-plus-incentive-fee contract adjusts the fee according to whether specified performance objectives are met.

📌 A cost contract pays the seller no fee, whereas a cost-plus-percentage-of-cost contract pays all costs plus a percentage of costs as a fee.

• A fixed-price incentive-fee contract adjusts seller profit as performance targets are met, while a fixed-price award-fee contract adds a performance-based award whose total possible amount is determined in advance.

• A sharing ratio describes how cost savings or overruns are shared between buyer and seller, and the point of total assumption in a fixed-price incentive-fee contract marks the point above which the seller bears all cost-overrun loss.

📖 18. Procurement Administration and Closure

🔑 Key Concepts & Definitions

• Contract: The legally binding agreement between buyer and seller that defines roles and responsibilities, mitigates risks, and may include payment, reporting, marketing, proposal, and statement-of-work terms.
• Claim: An assertion that the buyer harmed the seller and that the seller is entitled to compensation; claims are best settled through negotiation or the contract's dispute-resolution process.

★ Must-know

📌 An RFP requests a detailed proposal describing how and by whom work will be done, an IFB usually requests the total price for all work, and an RFQ requests a price per item, hour, meter, or other unit.

• Negotiations aim to obtain a fair and reasonable price and develop a good relationship with the seller, with scope, schedule, and price as the main items to negotiate.

• Procurement closure occurs when a contract is completed or terminated early, and every procurement must be closed out regardless of how it ends.

• Procurement closure includes:

  • product verification
  • negotiated settlement of claims and invoices
  • financial closure
  • procurement audit
  • record updates
  • final contract performance reporting
  • lessons learned
  • a procurement file

Further detail

• Procurement documents should include: seller background information and response instructions, source-selection criteria, pricing forms, the procurement statement of work, proposed contract terms and conditions

• Source-selection criteria include:

  • years in business
  • financial stability
  • understanding of need
  • price or life-cycle cost
  • technical ability
  • past performance quality
  • on-time completion ability
  • project-management ability

📌 A single-source procurement selects a preferred seller directly, whereas a sole-source procurement has only one available source.

• Evaluation methods include:

  • a weighting system
  • independent estimates
  • screening systems
  • past-performance history
  • presentations

• A legal contract requires:

  • an offer
  • acceptance
  • consideration
  • legal capacity
  • legal purpose

• The procurement manager or contract administrator has authority to change a contract; the project manager may request a change but needs the procurement manager's approval.

• Termination may be for cause or for convenience, and the contract should contain termination provisions.

• A procurement is closed after the seller receives the buyer's formal sign-off that the procured products are acceptable.

💡 Memory Hook

Administer performance and changes, settle claims, then verify, settle, pay, audit, and close.

📊 Synthesis Tables

Organizational Structure and Project Authority