Project Management Foundations Practice Quiz (69 questions)

Explanation

A project is temporary and creates a unique product, service, or result between a definite start and end. Ongoing routine work describes operations rather than a project.

Explanation

Operational work is ongoing, whereas project work has a definite end. The platform implementation has a defined completion point, while routine payment processing continues.

Explanation

The five process groups are initiating, planning, executing, monitoring and controlling, and closing. The other choices mix in activities or knowledge areas rather than naming the complete set of process groups.

Explanation

A project is considered complete when it meets the objectives defined in its charter. Termination applies when the objectives are not met, not when they are achieved.

Explanation

Initiating formally authorizes a project and can produce the project charter, identified stakeholders, and a stakeholder management strategy. Completing project work is associated with executing, not initiating.

Explanation

Planning develops the project management plan and project documents, providing a roadmap for accomplishing the project. Monitoring and controlling uses that plan to assess performance rather than create the roadmap.

Explanation

Monitoring and controlling measures performance against the project management plan and handles change requests, corrective and preventive actions, and defect repair. Executing carries out planned work but does not serve as the group for comparing performance and managing these responses.

Explanation

Closure requires completed closure activities and formal sign-off confirming that the product is acceptable; the project manager can then release resources involved in closing it. Apparent readiness does not substitute for the required formal acceptance.

Explanation

The project manager is accountable for project success or failure and integrates the project’s components into a cohesive whole that meets customer needs. Selecting and governing projects for organizational return is a portfolio-level responsibility.

Explanation

A program manager manages related projects together to achieve results not obtainable separately and ensures selected projects support organizational strategic goals. A portfolio manager governs projects or programs at the executive level rather than managing a related-project program.

Explanation

The sponsor advocates for the project, secures support and funding, and grants the project manager authority as outlined in the charter. The project manager is accountable for project outcomes but is not the role identified as granting that charter-based authority.

Explanation

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, whereas in a functional organization the functional manager directs it.

Explanation

Scope management ensures that all required work, and only that work, is performed; adding an unrequested feature is gold plating. Treating any completed work as project scope confuses work performed with work included in the agreed scope.

Explanation

Product scope refers to what the customer wants from the product. Project scope instead concerns the work performed to deliver that product scope.

Explanation

Project scope includes the work needed to deliver product scope, including planning, coordination, and management activities. Product scope describes the desired product rather than the work required to create it.

Explanation

The scope management plan is created as part of project management planning and covers scope planning, execution, and control. Creating it as a separate scope management process confuses the plan’s role with a standalone process.

Explanation

Collect Requirements begins by identifying stakeholders and recording them in a stakeholder register, followed by gathering and documenting detailed requirements with suitable methods. Defining acceptance criteria and focusing on the sponsor does not describe this process sequence.

Explanation

Observation and prototypes are both recognized methods for gathering requirements. Interviews and questionnaires are valid methods too, but they do not match the direct-observation and working-model approach described.

Explanation

The Requirements Traceability Matrix links requirements to project objectives and to other requirements, supporting assessment of scope changes and strategic alignment. The stakeholder register records stakeholders rather than tracing requirement relationships.

Explanation

Balancing requirements involves prioritizing them, resolving conflicts, and adjusting competing constraints such as scope, time, cost, quality, and resources to meet project objectives. Simply accepting every request does not resolve the underlying trade-offs.

Explanation

Define Scope uses requirements documentation, the project charter, and information about risks, assumptions, and constraints to establish what is and is not included. The WBS and WBS dictionary are components of the scope baseline, not the specified inputs in this unit.

Explanation

The project scope statement is an output of Define Scope and can include product and project scope, deliverables, acceptance criteria, exclusions, constraints, and assumptions. A decomposition into work packages describes the WBS instead.

Explanation

The scope baseline consists of the approved project scope statement, WBS, and WBS dictionary; deviations require a change request, and approved changes update these components. Recording a change without approval does not authorize a baseline revision.

Explanation

The WBS hierarchically decomposes the complete project scope and its deliverables into manageable work packages. Comparing completed work with the baseline is a control activity, not the function of the WBS.

Explanation

Define Activities decomposes WBS work packages into manageable activities, using the scope baseline and available project team. Assigning resources and durations is not the purpose of this decomposition process.

Explanation

Finish-to-Start is the most commonly used PDM relationship, and Start-to-Finish is rarely used. Start-to-Start is a valid relationship type, but it is not the most common.

Explanation

Padding is unacceptable, and estimates should be periodically checked for achievability, padding, and risks; the project manager is responsible for accurate, feasible estimates. A reserve is based on identified risks, so arbitrary extra time should not be relabeled as a reserve.

Explanation

Duration estimates are made after activities have been defined and sequenced and resource types and quantities have been identified. Setting the schedule baseline first would establish it before the activity durations are known.

Explanation

Padding is arbitrary extra time or cost added when the estimator lacks information, whereas reserves are based on identified risks and risk management. A risk-based allowance is therefore not padding merely because it adds time.

Explanation

Analogous estimating draws on expert judgment and historical information from similar work, while parametric estimating uses relationships between variables and activity outcomes. Reversing these methods confuses similarity-based comparison with a data-based relationship.

Explanation

Three-point estimating uses optimistic, pessimistic, and most likely estimates to produce a risk-based expected duration, often through an average or weighted average such as PERT. Analogous estimating instead relies on comparison with similar work.

Explanation

The critical path is defined as the longest path in the project network diagram. The number of activities alone does not determine which path has the longest duration.

Explanation

Total float is the delay possible without delaying the project end date, even if a successor's early start is affected. Free float specifically describes delay that does not delay a successor's early start.

Explanation

Monte Carlo analysis simulates project outcomes using a network diagram and three-point activity estimates to assess completion-date and cost probabilities, critical-path likelihood, and overall risk. Critical-path analysis identifies the longest route but does not itself provide these simulated outcome probabilities.

Explanation

The labor expense varies with the amount of work, while the subscription does not. Direct and indirect costs instead distinguish whether a cost can be attributed to project work.

Explanation

The contractor expense can be attributed to the project, whereas general rent is overhead that may serve multiple projects. Variable and fixed classifications concern whether costs change with the amount of work.

Explanation

Bottom-up estimating builds the total from individual activities or work packages through control units. Analogous estimating instead uses the cost of a comparable project as a basis.

Explanation

Contingency reserves address known risks remaining after risk responses, while management reserves address unknown risks. Reversing the two reserve types confuses known and unknown risks.

Explanation

Quality is the degree to which a project fulfills its requirements. Meeting a budget or schedule is a different measure of project performance.

Explanation

Quality management establishes and follows policies and procedures so the project meets the customer needs it was intended to meet. Inspection alone does not provide that broader system of policies and procedures.

Explanation

Kaizen is the ongoing search for small improvements in a process. Inspection checks a product or deliverable rather than describing this continuing improvement approach.

Explanation

The project manager holds ultimate responsibility, while quality responsibilities are shared across the organization. Assigning ultimate responsibility to a quality department overlooks the project manager’s role.

Explanation

Plan Quality defines project quality and how to achieve it; assurance checks process adherence, and control examines actual deliverables. Swapping assurance and control confuses process checks with deliverable checks.

Explanation

Plan Quality identifies relevant organizational and industry practices, standards, and requirements, and produces a Quality Management Plan. A control chart is a tool for monitoring process performance rather than this process’s stated output.

Explanation

Control limits are calculated from process variation at plus or minus three standard deviations, while specification limits reflect customer expectations or contractual requirements. Treating specification limits as statistical limits confuses the source of the two boundaries.

Explanation

A non-random pattern such as seven points on one side of the mean signals that a process is out of statistical control, even when all points fall within control limits. A point outside specification limits concerns defects against customer requirements, which is a different test.

Explanation

Team development aims to reduce turnover while improving individual knowledge, skills, and teamwork. Clarifying roles and publishing an organization chart are elements of the Human Resource Plan, not the primary aim of team development.

Explanation

The Human Resource Plan covers roles and responsibilities, project organization charts, and the staffing management plan. Staff acquisition and training needs are details within the staffing management plan rather than the complete set requested here.

Explanation

Conflict sources descend in frequency from schedule to project priorities, resources, technical opinions, administrative procedures, cost, and personality. Project priorities are the second most frequent cause, so placing them ahead of schedule changes the stated ranking.

Explanation

Confronting addresses the underlying problem and aims for a win-win solution. Compromising may give both parties partial satisfaction, but it is characterized as lose-lose because neither gets everything.

Explanation

Project managers spend about 85%–90% of their time communicating, and communication problems are among their most frequent challenges. An estimate of 60%–70% understates the stated share.

Explanation

Stakeholder management includes identification, assessment of requirements, expectations, interests, and influence, communication planning and execution, and ongoing management of expectations and influence. Recording names and sending updates at completion omits the continuous assessment and management work.

Explanation

Stakeholder analysis can draw on the project charter, past-project records, brainstorming, interviews, and names suggested by existing stakeholders. Resource calendars and performance measurements are not the listed sources for identifying stakeholders and assessing their influence.

Explanation

The Stakeholder Register is an output of Identify Stakeholders and compiles stakeholder information. The Communications Management Plan instead documents how communication will be managed and controlled.

Explanation

A risk is an uncertain event or condition that may affect project objectives positively or negatively. A threat is specifically a potential negative effect, so it does not cover the possibility of a beneficial effect.

Explanation

A risk threshold is the specific point at which risk becomes unacceptable. Risk tolerance describes the degree or level of risk considered acceptable, rather than the boundary marking unacceptability.

Explanation

The six processes are planning risk management, identifying risks, conducting qualitative and then quantitative analysis, planning responses, and monitoring and controlling risks. The sequence that places quantitative analysis before qualitative analysis reverses the two analysis processes.

Explanation

Procurement management proceeds from planning through conducting and administering procurements, then closing them. Administering occurs before closure, not before conducting.

Explanation

A change management procedure provides the formal means to add work outside the existing contract. An informal agreement does not meet the requirement that procurement contracts be formal.

Explanation

Idle workforce, proprietary procedures, and a desire to retain control all favor making the work internally. Buying may decrease project constraints, but it does not match these stated reasons for choosing to make.

Explanation

Procurement planning includes the make-or-buy analysis, procurement plan and statement of work, contract-type selection, procurement documents, and source-selection criteria. Evaluating performance and settling claims are administration or closure activities.

Explanation

A procurement statement of work describes all required seller work, including supporting activities such as meetings, reports, and communications, and should be clear, complete, and concise. A broad purpose without the required activities is not a complete description of the seller’s work.

Explanation

A functional statement of work emphasizes the end purpose or results rather than specific procedures. A design statement of work instead specifies precisely what work is to be done.

Explanation

Cost-reimbursable contracts are suited to uncertain scopes whose costs cannot be estimated accurately enough for fixed pricing. Fixed-price contracts fit well-defined requirements and sufficient competition to establish a fair price.

Explanation

In a fixed-price contract, the seller is responsible for costs above the agreed price, giving the buyer the least cost risk. The buyer does not automatically share those overruns through a routine adjustment.

Explanation

An RFP requests a detailed proposal describing how and by whom work will be done. An IFB usually seeks a total price, while an RFQ seeks prices per unit.

Explanation

Negotiations aim for a fair and reasonable price and a good relationship with the seller, with scope, schedule, and price as the main topics. Settling claims and updating records are associated with closing procurement rather than its main negotiation aims.

Explanation

A contract is the legally binding buyer-seller agreement that defines roles and responsibilities and mitigates risks, and it may contain a range of terms. A source-selection document compares offers but is not itself the binding agreement described here.

Explanation

Procurement closure occurs when a contract is completed or terminated early, and every procurement must be closed out regardless of how it ends. Early termination does not remove the need for closure.