Project, Agile, and Portfolio Management

Introduction and Context

Mechatronics projects integrate mechanical structures, electronics, sensors, actuators, embedded software, control algorithms, communications, manufacturing processes, and user requirements. Their management is therefore more complex than managing a single-discipline engineering project. A small change in a sensor, for example, may require redesign of the control software, modification of the electrical interface, new safety testing, and changes to the production schedule.

Technology management provides the structures and decisions needed to convert an engineering opportunity into a controlled, valuable, and deliverable initiative. Project management focuses on delivering a defined result within agreed constraints. Agile management emphasizes short feedback cycles and adaptation. Portfolio management selects and governs groups of initiatives so that organizational resources support strategic objectives rather than isolated technical interests.

This chapter examines scope, schedule, cost, quality, resources, earned-value analysis, Agile and hybrid methods, portfolio prioritization, and benefits realization. The emphasis is application: students should be able to select an appropriate management approach, interpret project-control information, and make defensible decisions in a mechatronics context.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Define a mechatronics project in terms of scope, deliverables, assumptions, constraints, and acceptance criteria.
2. Develop and interpret schedules, budgets, risk responses, quality plans, and resource plans.
3. Apply earned-value management to assess cost and schedule performance.
4. Compare predictive, Agile, and hybrid project approaches.
5. Prioritize projects within a technology portfolio using strategic, economic, risk, and capability criteria.
6. Establish governance and benefits-realization mechanisms.
7. Evaluate ethical, safety, cybersecurity, and regulatory responsibilities in technology initiatives.

1. Projects as Temporary Systems of Value Creation

A project is a temporary endeavor undertaken to create a unique product, service, or result. A mechatronics project may produce an automated inspection cell, a collaborative robot application, a medical device prototype, a smart production line, or an autonomous mobile platform.

Projects differ from operations. Operations are continuous and repetitive; projects have a beginning, an end, and a transition to operation or disposal. However, a technology project must be designed with operations in mind. Maintainability, training, spare parts, software updates, cybersecurity monitoring, and total cost of ownership are not merely post-project concerns.

The traditional project constraint model identifies scope, time, and cost as interdependent constraints, with quality and risk affecting all three. A reduction in schedule may require additional resources or reduced scope. Increasing scope without changing time, cost, or resources usually increases technical and delivery risk. A more useful modern view adds value, safety, sustainability, and stakeholder acceptance.

Important terminology includes:

• Sponsor: person or group accountable for supporting the project and obtaining organizational commitment.
• Project manager: person responsible for coordinating planning, execution, monitoring, and closure.
• Stakeholder: anyone who can affect, be affected by, or perceive themselves to be affected by the project.
• Deliverable: a verifiable product, component, document, or result.
• Milestone: a significant control point with zero duration in a schedule.
• Baseline: an approved reference plan used for comparison with actual performance.
• Change control: the structured process for evaluating and approving modifications.
• Work package: a manageable component of the work breakdown structure.

2. Initiating and Defining Scope

2.1 From opportunity to project charter

A project begins with a problem or opportunity, not with a preferred technology. A project charter should state the business or operational need, intended outcome, high-level scope, sponsor, major assumptions, constraints, preliminary risks, budget authority, and success criteria. For example, “install a robot” is a solution statement; “reduce manual loading time by 30% while maintaining operator safety and product traceability” is an outcome-oriented need.

A strong charter distinguishes outputs from outcomes. An output is what the project produces, such as a robotic cell. An outcome is the operational effect, such as reduced cycle time. Benefits are measurable improvements resulting from outcomes, such as increased throughput or reduced injury exposure.

2.2 Requirements and scope boundaries

Requirements should be traceable from stakeholder need to verification evidence. A requirement for an automated inspection system might specify measurement accuracy, maximum cycle time, environmental conditions, communication protocols, data retention, and safety performance. Ambiguous words such as “fast,” “intelligent,” or “user-friendly” should be converted into measurable acceptance criteria.

A requirements traceability matrix links each requirement to its design element, test method, and acceptance result. This reduces the risk that an apparently complete system contains unverified requirements.

The work breakdown structure (WBS) decomposes the total project scope into progressively smaller components. A typical WBS for a robotic inspection cell may include:

1. Project management and governance
2. Requirements and concept design
3. Mechanical design and tooling
4. Electrical and control-panel design
5. Robot and motion programming
6. Vision and inspection software
7. Safety design and validation
8. Procurement and fabrication
9. Integration and testing
10. Operator training and handover

The WBS should describe deliverables and work, not organizational departments alone. It becomes the foundation for estimating, scheduling, assigning responsibility, and controlling scope.

2.3 Scope creep and change control

Scope creep is uncontrolled expansion of project work. It commonly occurs when stakeholders request “small” additions that individually appear harmless but collectively consume contingency and delay integration. Every proposed change should be assessed for effects on requirements, interfaces, safety, cybersecurity, cost, schedule, quality, and benefits.

A change-control board or equivalent authority may classify changes as approved, rejected, deferred, or requiring re-baselining. Agile projects do not eliminate change control; they change its timing and mechanism. In Agile work, the product backlog is continuously reordered, but capacity, product goals, definition of done, and release commitments still require governance.

3. Scheduling and Resource Planning

3.1 Network logic

A schedule represents logical relationships among activities. Common relationships include finish-to-start, start-to-start, finish-to-finish, and start-to-finish, although finish-to-start should be used whenever it adequately represents the work because excessive leads and lags can conceal risk.

The critical path is the longest-duration path through a network. It determines the shortest possible project duration under the stated logic and estimates. Activities on the critical path have approximately zero total float. A delay to a critical activity can delay the project unless corrective action is taken.

For activity i, total float can be expressed as:

where TF is total float, ES is earliest start, EF is earliest finish, LS is latest start, and LF is latest finish. These values are obtained through forward and backward passes. The relationship assumes a consistent activity network and a defined project completion milestone.

3.2 Three-point estimation

When activity duration is uncertain, three-point estimation can be used. In the Program Evaluation and Review Technique (PERT) approximation, the expected duration is:

where t_o is the optimistic duration, t_m is the most likely duration, and t_p is the pessimistic duration. The formula assumes a beta-like distribution and is an approximation, not a guarantee. It should not be treated as statistically precise when estimates are speculative or when activity dependencies dominate uncertainty.

For an activity estimated as 4 days optimistic, 6 days most likely, and 10 days pessimistic:

The estimate is useful for planning but should be revisited as knowledge improves.

3.3 Resources and capacity

Resource planning identifies people, equipment, facilities, materials, software tools, and external suppliers. Mechatronics projects often compete for scarce specialists such as safety engineers, controls programmers, machine-vision experts, and commissioning technicians. A schedule that ignores these constraints is not feasible.

Resource leveling adjusts activity timing to resolve over-allocation. Resource smoothing attempts to use available float without changing the critical completion date. If neither is sufficient, the project manager must negotiate scope, acquire resources, change sequence, or revise the completion target.

A resource plan should also consider learning curves, shift patterns, fatigue, access to production equipment, supplier lead times, and the distinction between calendar time and productive engineering time.

4. Cost, Quality, and Risk Control

4.1 Cost planning

A project budget normally includes direct labor, purchased equipment, materials, subcontractors, facilities, testing, training, and applicable overhead. Estimates should identify assumptions and uncertainty. A contingency reserve addresses known-unknown risks within the project manager’s authority; management reserve is generally controlled at a higher level for unforeseen work. These reserves should not be used to conceal poor estimating or unauthorized scope.

A basic cost estimate may be constructed as:

All terms must use a common currency and time basis. If labor is estimated from hours and an hourly rate, C_labor = h × r, where h is labor hours and r is cost per hour. The estimate is valid only if the rate includes or clearly excludes benefits, overhead, and escalation.

4.2 Quality management

Quality means conformance to requirements and fitness for intended use. Project quality management includes:

• Quality planning: defining standards, metrics, inspection points, and acceptance methods.
• Quality assurance: evaluating whether processes are capable and appropriately followed.
• Quality control: inspecting and testing outputs against requirements.

Verification asks, “Was the product built according to specification?” Validation asks, “Does the product satisfy the real operational need?” A robotic system can pass component tests yet fail validation because operators cannot safely access tooling or because maintenance interrupts production excessively.

Quality should be built into design through reviews, interface control, configuration management, automated testing, supplier qualification, fault analysis, and staged integration. End-of-project inspection alone is expensive and cannot repair all design defects.

4.3 Risk management

A risk is an uncertain event or condition that may have a positive or negative effect on objectives. A risk register records the cause, event, consequence, probability, impact, owner, response, trigger, and residual exposure.

A simple qualitative risk score is:

where R is a ranking score, P is a probability rating, and I is an impact rating. This is a prioritization aid, not a probability law. It is meaningful only when scales are defined consistently and when users understand that equal scores may arise from very different combinations of likelihood and consequence.

Responses to threats include avoid, mitigate, transfer, accept, and escalate. Responses to opportunities include exploit, enhance, share, accept, and escalate. In safety-critical mechatronics, risk acceptance must be consistent with applicable legislation, standards, organizational authority, and the principle of reducing risk so far as reasonably practicable.

5. Earned-Value Management

Earned-value management (EVM) integrates scope, schedule, and cost. It compares three quantities at a status date:

• Planned Value (PV): authorized budget for work scheduled to be completed.
• Earned Value (EV): authorized budget for work actually completed.
• Actual Cost (AC): actual cost incurred for the completed work.

The project budget is often called the Budget at Completion (BAC). The principal variances and indices are:

Schedule variance, SV, and cost variance, CV, are expressed in budgetary units. A positive SV indicates more budgeted work has been completed than planned at the status date; it does not literally represent calendar days. SPI below 1 indicates progress is behind the planned value profile. CPI below 1 indicates that the project is obtaining less budgeted value per cost unit than planned.

A common estimate at completion is:

This assumes current cost efficiency will continue for the remaining work. If the original estimate is believed to remain valid for unfinished work, an alternative is:

The choice must be justified rather than applied mechanically. The estimate to complete is ETC = EAC − AC, and the variance at completion is VAC = BAC − EAC.

Worked EVM example

A control-system integration project has BAC = $120,000. At the review date, PV = $60,000, EV = $54,000, and AC = $63,000.

The project is behind its planned progress profile and is spending inefficiently. Assuming the current cost efficiency continues:

Thus, the forecast overrun is approximately $20,040, since VAC = 120,000 − 140,040 = −$20,040. Management should investigate the causes rather than simply increase the budget. Possible causes include rework, underestimated integration effort, supplier defects, or an unrealistic baseline.

EVM is less informative when scope is poorly defined, work is highly exploratory, or value is credited in large increments only at the end. Agile teams may use completed backlog items, release burn-up, flow metrics, and forecasting in addition to EVM, provided that the measurement rules are stable and transparent.

6. Predictive, Agile, and Hybrid Delivery

6.1 Predictive approaches

Predictive, or plan-driven, approaches define substantial scope early and proceed through planned phases. They are useful when requirements are stable, interfaces are regulated, physical change is expensive, or formal approvals are necessary. A systems-engineering V-model is often suitable for mechatronics because it links decomposition and design activities with corresponding integration, verification, and validation activities.

Predictive methods can fail when early requirements are uncertain or when users cannot evaluate the system until they experience a working prototype. Excessive documentation and late integration can also expose interface problems too late.

6.2 Agile principles and practices

Agile approaches deliver increments, obtain feedback, and adapt priorities. Scrum uses a product goal, product backlog, time-boxed sprints, a product owner, a Scrum Master, and a cross-functional development team. Kanban visualizes work, limits work in progress, and manages flow. Agile is not synonymous with “no planning”; it uses rolling-wave planning at different levels of detail.

A useful Agile concept is the definition of done. For a mechatronics increment, done may require assembled hardware, reviewed firmware, automated tests, safety checks, documentation, and demonstration on representative equipment. A software feature that compiles but has not been tested with the real sensor is not complete.

Agile is especially effective for uncertain algorithms, user interfaces, data services, and prototype learning. It is more difficult where long-lead procurement, certification, tooling, or irreversible physical fabrication dominates. These constraints support a hybrid model.

6.3 Hybrid management

A hybrid approach combines predictive governance with iterative technical development. For example, a project may use a predictive phase for safety requirements, procurement, facilities approval, and release authorization, while using Agile sprints for motion algorithms, operator screens, and diagnostic software.

Hybrid planning requires explicit integration points. The project should define which decisions are fixed, which are negotiable, who can reorder work, how physical and digital increments are tested together, and how changes affect certification and configuration baselines. Without such rules, hybrid delivery can become an ambiguous mixture in which neither formal control nor rapid learning works effectively.

7. Portfolio Management and Project Selection

A portfolio is a collection of projects, programs, products, and operational investments managed together to achieve strategic objectives. Portfolio management asks not only whether a project can be delivered, but whether it should be funded relative to competing opportunities.

7.1 Strategic alignment and selection criteria

Common criteria include:

• strategic alignment;
• expected financial or operational benefits;
• customer and market importance;
• regulatory or safety necessity;
• technical feasibility;
• cybersecurity and resilience;
• resource demand and capability development;
• environmental and social impact;
• dependency on other initiatives;
• urgency and opportunity cost.

A weighted-scoring model can make assumptions visible. If project j receives score s_ij on criterion i and criterion weights sum to 1, its aggregate score is:

Here, w_i is the weight of criterion i and s_ij is the normalized score of project j on that criterion. Scores must use a defined scale, such as 0 to 100. A weighted score is not an objective truth; it supports discussion and should be supplemented by feasibility, risk, and dependency analysis.

Financial analysis may include net present value (NPV). For cash flows occurring at periods t = 0 to n:

where CF_t is net cash flow at time t, r is the discount rate per period, and n is the final period. A positive NPV means the discounted inflows and outflows produce value relative to the selected discount rate and assumptions. NPV should not override legal, safety, or strategic necessities.

7.2 Balancing the portfolio

A strong portfolio is not simply the set of highest-scoring projects. It balances short-term improvements with long-term innovation, incremental upgrades with transformational initiatives, and revenue projects with enabling infrastructure. It also considers correlated risk. Funding five projects that depend on the same scarce controls engineer may create a portfolio bottleneck even if each project appears attractive independently.

Portfolio governance should include periodic review of continuation, acceleration, suspension, termination, or re-scoping. Stopping a project is not necessarily failure; it may be rational capital allocation when evidence shows that benefits are unlikely or assumptions have changed.

8. Benefits Realization and Governance

Benefits realization connects project outputs to measurable organizational value. A benefits-management plan should identify each benefit, its owner, baseline, target, measurement method, expected date, dependencies, and risks. For example:

Benefits may not appear immediately at project closure. Training, process redesign, maintenance capability, and user adoption may be required. The project manager delivers outputs; a business or operations owner is usually accountable for realizing outcomes after transition.

Governance defines decision rights, escalation routes, reporting cadence, approval thresholds, and records. Configuration management is essential where hardware, firmware, software, parameter files, and safety documentation evolve together. Every released configuration should be identifiable and reproducible.

Ethical and regulatory governance is particularly important in mechatronics. Projects may affect worker safety, privacy, employment, accessibility, and environmental performance. A vision system may collect identifiable images; an autonomous machine may make decisions that affect people; a connected controller may create cybersecurity exposure. Engineers must comply with applicable machinery, electrical, functional-safety, data-protection, cybersecurity, and sector-specific requirements. Compliance is a minimum obligation, not a substitute for professional judgment.

9. Illustrative Case: Automated Vision Inspection Cell

Background

A manufacturer of precision components proposes an automated vision inspection cell. The current process is manual, inconsistent across shifts, and exposes inspectors to repetitive handling. The proposed system combines a robot, camera, lighting, programmable controller, database connection, and reject mechanism.

Problem

The initial proposal focuses on purchasing hardware but does not define inspection accuracy, data ownership, operator interaction, maintenance responsibility, or integration with production scheduling. The sponsor requests completion in six months with a budget of $250,000.

Analysis

The project team conducts stakeholder interviews and identifies requirements: 99% detection of specified defects under defined conditions, a 20-second maximum cycle time, safe access for loading and maintenance, traceability of inspection results, and changeover in less than 10 minutes. A WBS reveals that lighting trials, data integration, safety validation, and operator training were absent from the original estimate.

A risk review identifies reflective surfaces, variation in ambient light, supplier lead time, false rejects, cybersecurity of the network connection, and insufficient maintenance skills. The team decides that a fully predictive approach would be unsuitable for the inspection algorithm, but formal stage gates are required for safety and production release.

Approach and solution

The project adopts a hybrid method. Requirements, safety architecture, procurement approval, and site readiness are managed through predictive gates. Vision experiments and operator-interface development proceed in two-week iterations. Each iteration must produce a testable increment using representative components.

The portfolio board compares this project with a conveyor modernization project. The inspection cell receives a high strategic score because it supports quality and traceability, but its resource demand conflicts with another project requiring the same controls engineer. The board delays the second project by one month rather than overloading both teams.

The team establishes a baseline budget, a risk reserve, a requirements traceability matrix, and a benefits plan. Benefits will be measured three months after deployment using cycle time, first-pass yield, false-reject rate, and manual exposure. The operations manager owns benefits realization; the project manager owns delivery.

Outcome

During integration, the team discovers that a camera algorithm that performed well in laboratory trials fails under production lighting. Because iterative testing was planned, the issue is found before final acceptance. The team redesigns the lighting enclosure and updates the test set. The project enters production two weeks later than the original internal target but meets the approved release date after an early schedule reserve is used. The system achieves a 31-second average cycle time, 98.5% detection for the specified defect class, and a substantial reduction in manual handling.

Learning points

1. A technology purchase is not a complete project definition.
2. Requirements must include operating conditions and acceptance tests.
3. Hybrid methods accommodate both physical governance and software uncertainty.
4. Portfolio decisions must consider shared specialist capacity.
5. Benefits require named owners and post-project measurement.
6. Early representative testing is more valuable than late demonstration with ideal samples.

10. Challenges, Limitations, and Contemporary Developments

Project plans are models of future work, not predictions with certainty. Estimates contain epistemic uncertainty, and novel engineering may reveal unknowns that cannot be eliminated through more detailed planning. Excessive control can suppress learning; insufficient control can create unsafe or unaffordable experimentation.

Digital engineering and digital twins can improve traceability between requirements, models, simulations, physical assets, and operating data. Artificial intelligence can support schedule-risk prediction, defect classification, resource forecasting, and document analysis. However, AI-generated estimates and recommendations require human review because training data may be biased, assumptions may be hidden, and outputs may not be explainable. Sensitive engineering data also requires access control and protection against unauthorized model training or disclosure.

Contemporary project practice increasingly emphasizes product thinking, continuous delivery, sustainability, lifecycle carbon, resilience, and cybersecurity by design. These developments do not replace fundamental management disciplines. They increase the need for clear objectives, transparent assumptions, competent decision-making, and evidence-based control.

Best-Practice Checklist

Before authorizing a mechatronics technology initiative, confirm that:

• the problem and intended benefits are clear;
• scope boundaries and acceptance criteria are documented;
• requirements are traceable to verification evidence;
• the WBS includes integration, safety, training, and handover;
• schedule logic reflects resource and supplier constraints;
• the budget identifies assumptions and reserves;
• quality and configuration plans are established;
• risks have owners, triggers, and responses;
• the delivery approach matches uncertainty and regulatory needs;
• portfolio dependencies and capacity constraints are visible;
• benefits have accountable owners and measurement dates;
• ethical, safety, cybersecurity, and environmental implications are reviewed.

Chapter Summary

Project management organizes temporary work so that mechatronics outputs are delivered within controlled scope, schedule, cost, quality, and risk boundaries. Scope is defined through requirements, acceptance criteria, and a work breakdown structure. Network schedules, critical-path analysis, resource planning, and three-point estimation support realistic delivery planning.

Cost and quality must be managed throughout the lifecycle rather than inspected only at the end. Earned-value management compares planned value, earned value, and actual cost to reveal progress and efficiency trends. Predictive methods support stable requirements and formal control; Agile methods support learning and rapid feedback; hybrid methods combine both where physical, software, safety, and procurement constraints coexist.

Portfolio management selects and balances initiatives according to strategic alignment, value, risk, capability, dependencies, and capacity. Weighted scoring and NPV can support analysis but do not replace judgment. Finally, benefits realization connects project outputs to operational outcomes through named owners, baselines, targets, and post-delivery measurement. Effective technology management is therefore not merely completing projects; it is creating safe, usable, sustainable, and strategically valuable results.

Key Terms

Project: A temporary endeavor that creates a unique product, service, or result.

Project charter: An authorization document describing purpose, authority, objectives, and high-level constraints.

Scope: The total work and deliverables included in a project.

Work breakdown structure: A hierarchical decomposition of project scope into manageable components.

Requirement: A needed capability, condition, or performance characteristic.

Acceptance criterion: A measurable condition used to determine whether a deliverable is acceptable.

Baseline: An approved plan used as a reference for performance measurement.

Critical path: The longest logical path through a schedule network.

Float: The amount of time an activity can be delayed without violating a schedule constraint.

Earned value: The budgeted value of work actually completed.

Cost performance index: Earned value divided by actual cost.

Schedule performance index: Earned value divided by planned value.

Agile: An adaptive approach based on incremental delivery, feedback, and reprioritization.

Hybrid project management: A deliberate combination of predictive and adaptive practices.

Portfolio: A group of initiatives managed together to achieve strategic objectives.

Weighted scoring: A decision method that combines criterion scores using assigned weights.

Benefits realization: The process of ensuring that project outputs produce intended organizational value.

Configuration management: Control of the identity, versions, and relationships of system components.

Stakeholder: A person or group that affects, is affected by, or perceives effects from a project.

Risk register: A controlled record of identified risks, analysis, ownership, and responses.

Review Questions

5 Short Answer Questions

1. Distinguish a project output from an operational benefit.
2. What is the purpose of a work breakdown structure?
3. Define earned value and actual cost.
4. State one situation in which a hybrid approach is appropriate.
5. Why should benefits have named owners?

5 Long Answer Questions

1. Explain how requirements, scope, acceptance criteria, and the WBS are related in a mechatronics project.
2. Compare predictive, Agile, and hybrid approaches, including their strengths and limitations.
3. Explain how quality management differs from end-of-project inspection.
4. Describe how a portfolio board should balance strategic value, risk, dependencies, and scarce resources.
5. Discuss ethical, safety, cybersecurity, and regulatory responsibilities in an automated-cell project.

3 Analytical / Application Questions

1. A project has BAC = $200,000, PV = $100,000, EV = $90,000, and AC = $110,000. Calculate SV, CV, SPI, CPI, and EAC using the assumption that current cost efficiency continues. Interpret the results.
2. Design a weighted portfolio-selection model for three mechatronics projects. Choose at least four criteria, assign weights totaling 1, define a scoring scale, and explain how you would test whether the decision is robust.
3. Develop a hybrid delivery plan for an autonomous mobile robot project. Identify which activities should be managed predictively, which should be iterative, and which integration and safety gates are required.

Multiple Choice Questions with Answers

Question 1

Which document decomposes total project scope into progressively smaller deliverable-oriented components?

A. Risk register

B. Work breakdown structure

C. Benefits register

D. Resource histogram

Correct Answer: B. Work breakdown structure

Question 2

A project has PV = $80,000, EV = $72,000, and AC = $75,000. What is its cost performance index?

A. 0.90

B. 0.96

C. 1.07

D. 1.11

Correct Answer: B. 0.96

Question 3

Which statement about schedule variance in earned-value management is correct?

A. It is measured directly in calendar days

B. It equals AC minus EV

C. It equals EV minus PV and is expressed in budgetary units

D. It is always positive when a project is under budget

Correct Answer: C. It equals EV minus PV and is expressed in budgetary units

Question 4

Which situation most strongly supports an Agile approach?

A. Stable requirements with mandatory fixed approvals

B. Highly uncertain software and algorithm requirements requiring frequent user feedback

C. A long-lead component with no design alternatives

D. A legally prescribed test sequence that cannot change

Correct Answer: B. Highly uncertain software and algorithm requirements requiring frequent user feedback

Question 5

What is the main purpose of a definition of done?

A. To assign the project budget

B. To specify when an increment satisfies agreed completion conditions

C. To identify the project sponsor

D. To calculate net present value

Correct Answer: B. To specify when an increment satisfies agreed completion conditions

Question 6

If CPI is below 1.0, what does this generally indicate?

A. The project is obtaining less budgeted value per cost unit than planned

B. The project is ahead of schedule

C. The project has no remaining risk

D. The approved scope has increased

Correct Answer: A. The project is obtaining less budgeted value per cost unit than planned

Question 7

Which criterion is especially important when selecting projects for a technology portfolio?

A. The project manager’s personal preference

B. Strategic alignment and resource capacity

C. The number of pages in the project charter

D. Whether the project has the newest technology

Correct Answer: B. Strategic alignment and resource capacity

Question 8

What is the primary difference between verification and validation?

A. Verification checks conformance to specification; validation checks fitness for intended use

B. Verification occurs after benefits realization; validation occurs before initiation

C. Verification concerns cost; validation concerns schedule

D. Verification is optional; validation is mandatory for every project

Correct Answer: A. Verification checks conformance to specification; validation checks fitness for intended use

Question 9

For an activity with optimistic duration 3 days, most likely duration 5 days, and pessimistic duration 9 days, what is the PERT expected duration?

A. 4.33 days

B. 5.33 days

C. 5.67 days

D. 6.00 days

Correct Answer: B. 5.33 days

Question 10

Who is normally accountable for realizing an operational benefit after a project transitions into operation?

A. Only the procurement officer

B. The business or operations owner

C. The external equipment vendor in every case

D. The schedule analyst

Correct Answer: B. The business or operations owner