What is a passing score on the CAPM exam?

The CAPM is pass/fail — PMI does not release a numeric passing score or percentage. Your result is based on a psychometric analysis of the 135 scored questions, with per-domain proficiency feedback (Above Target through Needs Improvement).

How much does the CAPM exam cost?

The CAPM exam costs $225 for PMI members and $300 for non-members. PMI membership costs about $129/year; members also pay lower retake fees ($150 vs. $200).

How do I maintain my CAPM certification?

To maintain the CAPM, you must earn 15 professional development units (PDUs) every 3-year cycle under PMI's Continuing Certification Requirements (CCR) program, log them in PMI's CCR System, and pay the renewal fee to keep the credential active.

Can I retake the CAPM exam if I don't pass?

Yes — you can take the CAPM exam up to three times within the 1-year eligibility window your accepted application grants. If you don't pass on an attempt, you can re-sit within that window after paying the retake fee — $150 for PMI members and $200 for non-members. If you use all three attempts without passing, you must wait one year from your last attempt before reapplying.

What is provided at the test center for the CAPM?

At the CAPM test center, PMI provides an erasable note board and an on-screen calculator — no outside notes are permitted. You store phones and personal items in a locker, check in with a government-issued photo ID, and complete a short tutorial before the 3-hour exam begins. If you test via online proctoring, the same tools are available on screen along with a room and ID scan.

Which of the following best describes the primary purpose of the project charter within the context of project initiation?

To formally authorize the project manager to apply organizational resources to project activities

To document the high-level requirements and the outcome of the project

To serve as a preliminary delineation of roles and responsibilities

To outline the project budget and schedule in detail

In project management, what does the term 'stakeholder' specifically refer to?

Individuals or organizations that are actively involved in the project or whose interests may be affected as a result of project execution or project completion

Only the project team members who are actively involved in project execution

Only the clients or customers who will use the project's final deliverable

Only the project sponsor and the project manager

Which of the following best describes a functional organizational structure in the context of project management?

A structure where team members are grouped by their specialized skills or functions and report to a functional manager

A structure where team members report to multiple managers, typically a functional manager and a project manager

A structure where the project manager has full authority over the project and the team

A structure designed to reduce the duplication of resources and efforts across projects

What does the term 'matrix organization' signify in project management?

An organization where project team members report to both a functional manager and a project manager

An organization that strictly follows a hierarchical structure with clear lines of authority and communication

An organization that eliminates traditional management layers to foster direct communication

An organization that operates with a flexible team structure, adapting quickly to changing needs without a formal hierarchy

The Pareto Principle, often applied in project management, suggests that:

20% of the work consumes 80% of the project's time and resources

All tasks have equal importance and should be given equal priority

Communication accounts for 90% of a project manager's time

Projects typically exceed their initial cost estimates by 20%

Earned Value Management (EVM) is a technique used to measure project performance and progress. Which of the following best describes the purpose of EVM?

To compare the amount of work actually completed to the original budget

To measure project performance against the project scope exclusively

To identify the project risks and develop appropriate response strategies

To solely focus on the time management aspect of project execution

Which of the following is NOT a typical characteristic of a project?

Projects are ongoing operations.

Projects have defined objectives.

Projects are temporary endeavors.

Projects produce unique products, services, or results.

The 'critical path method' (CPM) is a key tool in project management. What is its primary purpose?

To identify the longest sequence of dependent tasks and calculate the shortest possible project duration

To allocate resources in the most efficient way possible across all project tasks

To track project expenses and ensure the project does not exceed its budget

To manage the project team's performance and address any skill gaps

In project management, 'risk appetite' is defined as:

The degree to which an organization is willing to make risky decisions, especially with respect to investment

The level of uncertainty an organization is willing to pursue or retain

The specific amount of risk an organization is willing to accept for a given project

The quantifiable limit of risk exposure that an organization is willing to accept in the pursuit of its objectives

In the context of project scope management, what is the primary purpose of creating a Work Breakdown Structure (WBS)?

To organize and define the total scope of the project hierarchically

To allocate the project budget across various tasks

To list all the materials needed for the project completion

To establish a timeline for project deliverables

Which of the following best defines 'Project Procurement Management'?

The process of identifying, acquiring, and managing the resources and suppliers necessary for the project

The process of tracking and managing project costs to adhere to the budget

The methodology for managing the physical resources of the project, including equipment and facilities

The strategy for managing team members and their tasks within the project

What is the significance of 'Monte Carlo Simulation' in project management?

It is a method for estimating the probability of completing project tasks within the scheduled time frame

It is used to create a detailed project schedule

It is a technique to visually represent project stakeholders

It is a tool for determining the project's budget at completion

In the context of project risk management, what is a 'risk register' primarily used for?

Recording all identified project risks along with their characteristics

Documenting the responses to project risks

Listing all approved project expenditures

Scheduling periodic risk assessment meetings

Which of the following is an example of a 'lag' in a project schedule?

A delay in the start of an activity due to the late completion of its predecessor

The amount of time an activity can be delayed without delaying the project finish date

The acceleration of an activity start date by allocating more resources

The shortest duration within which an activity needs to be completed

The term 'fast tracking' in project management refers to:

Performing more activities in parallel to shorten the project duration

Increasing the project budget to meet escalating costs

Adding more resources to activities to shorten their duration

Extending the project timeline to accommodate scope changes

What is the primary function of 'Configuration Management' in project management?

To ensure that the project's products, services, or results are consistent and meet requirements

To manage changes to the project schedule

To track project expenses and budget modifications

To monitor and control the project team's performance

In project management, what does the 'Critical Chain Method' (CCM) primarily focus on?

Managing project resources constraints

Identifying the project's longest sequence of dependent tasks

Estimating the project's total cost

Allocating the project budget across tasks

What role does 'benefit cost ratio' (BCR) play in project selection?

It evaluates the financial viability of a project by comparing its benefits to its costs

It determines the functional requirements of the project

It assesses the feasibility of the project based on technical aspects

It identifies the project with the shortest duration

Which of the following is a key feature of 'Agile Project Management'?

Regular adaptation to changes and ongoing stakeholder involvement

A fixed project scope that remains unchanged throughout the project lifecycle

Complete reliance on upfront planning and design phases

Strict adherence to a predetermined sequence of project tasks

The 'Resource Leveling' technique in project management is used to:

Even out resource allocation over the course of the project to address resource constraints

Increase the project budget to incorporate additional resources

Address conflicts among project stakeholders

Accelerate the project timeline to meet tight deadlines

In project communication management, what is the primary purpose of an 'Information Distribution Matrix'?

To detail who needs what information, when they need it, and how it will be delivered

To identify and track project risks

To allocate tasks among project team members

To outline the project budget across different departments

In the context of project time management, what is 'Resource Smoothing'?

Adjusting resources so that their usage does not exceed certain predefined limits

Adjusting the project schedule to expedite the project completion

Reducing the project scope to meet resource availability

Increasing the budget to hire additional resources

What does 'Project Integration Management' primarily focus on?

Coordinating all aspects of the project plan to ensure cohesive project execution

Managing the project budget and financial resources

Ensuring that project processes are as efficient as possible

Integrating new technology tools into project management practices

The 'Delphi Technique' is used in project management for what purpose?

To gather expert opinions on specific project-related issues anonymously

To develop the project schedule

To estimate project costs accurately

To allocate resources efficiently across project tasks

What is the significance of 'Sunk Costs' in project decision-making?

They are costs that have already been incurred and cannot be recovered.

They represent future costs that have not yet been incurred but are projected.

They are indirect costs that are not directly attributable to the project activities.

They include costs associated with the potential risks of the project.

Earned Schedule' technique in project management is used to:

Determine the project's schedule variance and forecast its completion date.

Calculate the total cost at the completion of the project.

Allocate the project's budget across its various phases.

Measure the team's performance and productivity.

The 'RACI Matrix' in project management is a tool used to:

Clarify roles and responsibilities in task completion.

Identify and assess project risks.

Develop a comprehensive project budget.

Schedule project tasks and milestones.

In project quality management, 'Control Charts' are used to:

Analyze process variations and stability over time.

Track expenses over the course of the project.

Monitor the time variance of project tasks.

Allocate resources based on project phases.

The process of 'Qualitative Risk Analysis' in project management involves:

Prioritizing risks based on their probability and impact on project objectives.

Quantifying the financial impact of each identified risk.

Calculating the exact time delay risks will introduce to the project schedule.

Assigning a specific cost to mitigating identified risks.

In project stakeholder management, the 'Power/Interest Grid' is used to:

Map stakeholders based on their level of authority and concern regarding project outcomes.

Calculate the budget required for stakeholder engagement activities.

Schedule stakeholder meetings throughout the project lifecycle.

Determine the salary increments for project team members based on stakeholder feedback.

Analogous Estimating' in project management is primarily used for:

Estimating the duration or cost of activities based on past similar projects.

Determining the project's total cost by summing up individual task costs.

Calculating the exact amount of resources needed for each project phase.

Developing a detailed schedule for the project execution phase.

In project management, what is the primary purpose of 'Cost Variance' (CV) analysis?

To measure the degree of variation from the original project budget.

To track the physical progress of the project against its schedule.

To identify the effectiveness of the project communication plan.

To evaluate the project team's performance efficiency.

What does the 'Schedule Performance Index' (SPI) indicate in project management?

The efficiency of the team's use of allocated time for project tasks.

The accuracy of the project's initial cost estimates.

The effectiveness of the project's risk management efforts.

The project team's ability to manage stakeholder expectations.

In the context of project scope management, the 'Scope Baseline' includes which of the following components?

Work Breakdown Structure (WBS), WBS Dictionary, and Scope Statement

Project charter, project schedule, and risk register

Project budget, stakeholder list, and communications plan

Quality management plan, resource calendar, and procurement documents

Parametric Estimating' in project management is best described as:

A method that applies project parameters, such as unit costs or historical productivity rates, to estimate project costs or durations.

A technique that uses statistical methods to predict outcomes based on historical data.

An approach that uses the project team's consensus to estimate project durations and costs.

The process of breaking down the project scope into smaller parts to estimate costs more accurately.

What role does 'Variance at Completion' 'VAC' play in project management?

It forecasts the total cost variation between the project's budget at completion and its estimated cost at completion.

It indicates the expected degree of variation in the project's final deliverables from the original scope.

It measures the project team's variance in performance from the project plan.

It calculates the time variance between the project's scheduled completion and its actual completion date.

In project risk management, 'Secondary Risks' are best described as:

Risks that arise as a direct result of implementing a risk response.

Risks identified after the project has entered its closing phase.

Minor risks that do not have a significant impact on the project's objectives.

Risks that have been identified but are deemed unlikely to occur.

The technique of 'Progressive Elaboration' in project management is primarily used to:

Incrementally improve the project plan as more detailed information becomes available.

Reduce the project scope systematically to meet budget constraints.

Increase the efficiency of project team members over the project lifecycle.

Elaborate on the project's risks as the project progresses through its phases.

Your FREE Certified Associate in Project Management (CAPM) Practice Test 2026 – 330+ Q&A

Q: What's on the CAPM exam?

The CAPM exam covers four domains per PMI's Examination Content Outline: Project Management Fundamentals & Core Concepts (36%), Business Analysis Frameworks (27%), Agile Frameworks/Methodologies (20%), and Predictive, Plan-Based Methodologies (17%).

Q: Who is eligible to take the CAPM exam?

To be eligible for the CAPM exam, you need a secondary degree (high school diploma, associate degree, or global equivalent) plus 23 contact hours of project management education completed before the exam. No project leadership experience is required, which is the main difference from the PMP.

Prepare with realistic, CAPM exam-style questions — take a full 150-question practice test or drill one domain.

Master questions to boost your scoreMaster questions to raise your exam readiness score

How ready are you?

CAPM Practice Questions

Which of the following best describes the primary purpose of the project charter within the context of project initiation?
- To formally authorize the project manager to apply organizational resources to project activities
- To document the high-level requirements and the outcome of the project
- To serve as a preliminary delineation of roles and responsibilities
- To outline the project budget and schedule in detail
Correct answer: To formally authorize the project manager to apply organizational resources to project activities
Correct answer: To formally authorize the project manager to apply organizational resources to project activities. Explanation: The project charter serves as a formal document that authorizes the project manager to apply organizational resources to project activities. It signifies the official start of the project and provides the project manager with the authority to request resources and direct project activities.
In project management, what does the term 'stakeholder' specifically refer to?
- Only the project team members who are actively involved in project execution
- Only the clients or customers who will use the project's final deliverable
- Individuals or organizations that are actively involved in the project or whose interests may be affected as a result of project execution or project completion
- Only the project sponsor and the project manager
Correct answer: Individuals or organizations that are actively involved in the project or whose interests may be affected as a result of project execution or project completion
Correct answer: Individuals or organizations that are actively involved in the project or whose interests may be affected as a result of project execution or project completion. Explanation: Stakeholders refer to all individuals or organizations that are actively involved or whose interests may be positively or negatively affected by the project. This includes a wide range of parties such as project team members, sponsors, customers, and others who may be influenced by the project.
Which of the following best describes a functional organizational structure in the context of project management?
- A structure where team members report to multiple managers, typically a functional manager and a project manager
- A structure where the project manager has full authority over the project and the team
- A structure where team members are grouped by their specialized skills or functions and report to a functional manager
- A structure designed to reduce the duplication of resources and efforts across projects
Correct answer: A structure where team members are grouped by their specialized skills or functions and report to a functional manager
Correct answer: A structure where team members are grouped by their specialized skills or functions and report to a functional manager. structure where team members are grouped by their specialized skills or functions and report to a functional manager. Explanation: In a functional organizational structure, employees are grouped by their specific functions or departments (such as marketing, engineering, etc.) and report to a functional manager. This structure emphasizes specialization and efficiency in operations but can pose challenges for project coordination and resource allocation.
What does the term 'matrix organization' signify in project management?
- An organization that strictly follows a hierarchical structure with clear lines of authority and communication
- An organization where project team members report to both a functional manager and a project manager
- An organization that eliminates traditional management layers to foster direct communication
- An organization that operates with a flexible team structure, adapting quickly to changing needs without a formal hierarchy
Correct answer: An organization where project team members report to both a functional manager and a project manager
Correct answer: An organization where project team members report to both a functional manager and a project manager. Explanation: A matrix organization is characterized by a dual reporting system where project team members report to both a functional manager (for their functional role) and a project manager (for their role within the project). This structure aims to combine the benefits of functional and projectized structures, offering flexibility and efficiency in resource allocation and task execution.
The Pareto Principle, often applied in project management, suggests that:
- All tasks have equal importance and should be given equal priority
- 20% of the work consumes 80% of the project's time and resources
- Communication accounts for 90% of a project manager's time
- Projects typically exceed their initial cost estimates by 20%
Correct answer: 20% of the work consumes 80% of the project's time and resources
Correct answer: 20% of the work consumes 80% of the project's time and resources. Explanation: The Pareto Principle, or the 80/20 rule, suggests that a small portion of work (around 20%) often accounts for a large portion (around 80%) of the value or results. In project management, this principle can be used to prioritize tasks and focus on the activities that will provide the most significant benefit to the project.
In the context of project management, 'scope creep' refers to:
- The reduction of the project scope due to budget cuts
- The formal process of scope reduction, as approved by the project sponsor
- The uncontrolled expansion to project scope without adjustments to time, cost, and resources
- The intentional expansion of scope to include additional features beneficial to the project
Correct answer: The uncontrolled expansion to project scope without adjustments to time, cost, and resources
Correct answer: The uncontrolled expansion to project scope without adjustments to time, cost, and resources. Explanation: Scope creep is the term used to describe the gradual, often unnoticed, expansion of the project's scope without corresponding adjustments in time, budget, and resources. This phenomenon can lead to project delays, cost overruns, and other issues.
Which project management process group focuses primarily on defining and refining objectives and selecting the best courses of action to achieve the project goals?
- Initiating
- Planning
- Executing
- Closing
Correct answer: Planning
Correct answer: Planning. Explanation: The Planning process group is centered on defining and refining the project objectives and planning the necessary course of action to achieve those objectives. This involves detailed planning in all areas of the project, such as scope, budget, schedule, quality, and risk management.
Earned Value Management (EVM) is a technique used to measure project performance and progress. Which of the following best describes the purpose of EVM?
- To compare the amount of work actually completed to the original budget
- To measure project performance against the project scope exclusively
- To identify the project risks and develop appropriate response strategies
- To solely focus on the time management aspect of project execution
Correct answer: To compare the amount of work actually completed to the original budget
Correct answer: To compare the amount of work actually completed to the original budget. Explanation: Earned Value Management (EVM) is a project management technique that integrates scope, cost, and schedule measures to assess project performance and progress. It provides a means to compare the amount of work actually completed at any point in a project to the original budget, along with the original schedule.
Which of the following is NOT a typical characteristic of a project?
- Projects are ongoing operations.
- Projects have defined objectives.
- Projects are temporary endeavors.
- Projects produce unique products, services, or results.
Correct answer: Projects are ongoing operations.
Correct answer: Projects are ongoing operations. Explanation: Projects are not ongoing operations; they are temporary endeavors undertaken to create a unique product, service, or result. Projects have a defined beginning and end, in contrast to ongoing operations, which are repetitive and permanent or semi-permanent functional work to produce the same product or provide the same service over time.
The 'critical path method' (CPM) is a key tool in project management. What is its primary purpose?
- To identify the longest sequence of dependent tasks and calculate the shortest possible project duration
- To allocate resources in the most efficient way possible across all project tasks
- To track project expenses and ensure the project does not exceed its budget
- To manage the project team's performance and address any skill gaps
Correct answer: To identify the longest sequence of dependent tasks and calculate the shortest possible project duration
Correct answer: To identify the longest sequence of dependent tasks and calculate the shortest possible project duration. Explanation: The critical path method (CPM) is a step-by-step project management technique used to identify the sequence of critical and non-critical tasks necessary to complete a project. The primary purpose of CPM is to determine the longest path of planned tasks to the end of the project and the earliest possible completion date, considering the dependencies between tasks.
In project management, 'risk appetite' is defined as:
- The level of uncertainty an organization is willing to pursue or retain
- The specific amount of risk an organization is willing to accept for a given project
- The degree to which an organization is willing to make risky decisions, especially with respect to investment
- The quantifiable limit of risk exposure that an organization is willing to accept in the pursuit of its objectives
Correct answer: The degree to which an organization is willing to make risky decisions, especially with respect to investment
Correct answer: The degree to which an organization is willing to make risky decisions, especially with respect to investment. Explanation: Risk appetite refers to the degree of risk that an organization is willing to accept in pursuit of its goals before action is deemed necessary to reduce the risk. It reflects the organization's attitude towards risk-taking, particularly in terms of investment decisions and project selection.
In the context of project scope management, what is the primary purpose of creating a Work Breakdown Structure (WBS)?
- To allocate the project budget across various tasks
- To list all the materials needed for the project completion
- To organize and define the total scope of the project hierarchically
- To establish a timeline for project deliverables
Correct answer: To organize and define the total scope of the project hierarchically
Correct answer: To organize and define the total scope of the project hierarchically. Explanation: The primary purpose of a Work Breakdown Structure (WBS) is to organize and define the total scope of the project in a hierarchical fashion. It breaks down the project into smaller, more manageable parts, helping the project team to understand and execute the project scope more effectively.
Which of the following best defines 'Project Procurement Management'?
- The process of tracking and managing project costs to adhere to the budget
- The process of identifying, acquiring, and managing the resources and suppliers necessary for the project
- The methodology for managing the physical resources of the project, including equipment and facilities
- The strategy for managing team members and their tasks within the project
Correct answer: The process of identifying, acquiring, and managing the resources and suppliers necessary for the project
Correct answer: The process of identifying, acquiring, and managing the resources and suppliers necessary for the project. Explanation: Project Procurement Management involves the processes necessary to purchase or acquire products, services, or results needed from outside the project team. It includes identifying, acquiring, and managing the resources and suppliers necessary to complete the project successfully.
What is the significance of 'Monte Carlo Simulation' in project management?
- It is used to create a detailed project schedule
- It is a technique to visually represent project stakeholders
- It is a method for estimating the probability of completing project tasks within the scheduled time frame
- It is a tool for determining the project's budget at completion
Correct answer: It is a method for estimating the probability of completing project tasks within the scheduled time frame
Correct answer: It is a method for estimating the probability of completing project tasks within the scheduled time frame. Explanation: The Monte Carlo Simulation is a statistical technique that allows project managers to account for risk in quantitative analysis and decision making. By simulating a range of possible outcomes in a project's schedule or budget, it helps estimate the probability of completing project tasks within the scheduled time frame or budget.
In the context of project risk management, what is a 'risk register' primarily used for?
- Documenting the responses to project risks
- Listing all approved project expenditures
- Recording all identified project risks along with their characteristics
- Scheduling periodic risk assessment meetings
Correct answer: Recording all identified project risks along with their characteristics
Correct answer: Recording all identified project risks along with their characteristics. Explanation: A risk register is a project management tool used for risk identification and risk analysis purposes. It serves as a repository for all identified risks and their characteristics, including their descriptions, categories, priorities, and responses.
Which of the following is an example of a 'lag' in a project schedule?
- A delay in the start of an activity due to the late completion of its predecessor
- The amount of time an activity can be delayed without delaying the project finish date
- The acceleration of an activity start date by allocating more resources
- The shortest duration within which an activity needs to be completed
Correct answer: A delay in the start of an activity due to the late completion of its predecessor
Correct answer: A delay in the start of an activity due to the late completion of its predecessor. delay in the start of an activity due to the late completion of its predecessor. Explanation: A 'lag' is a delay between tasks that have a dependency. For example, if a task cannot start until a certain number of days after its predecessor task is complete, that delay is referred to as a lag. It represents a waiting period between activities.
The term 'fast tracking' in project management refers to:
- Increasing the project budget to meet escalating costs
- Adding more resources to activities to shorten their duration
- Performing more activities in parallel to shorten the project duration
- Extending the project timeline to accommodate scope changes
Correct answer: Performing more activities in parallel to shorten the project duration
Correct answer: Performing more activities in parallel to shorten the project duration. Explanation: Fast tracking is a schedule compression technique used in project management where activities or phases normally done in sequence are performed in parallel. This can shorten the project duration but may also increase risk and complexity.
What is the primary function of 'Configuration Management' in project management?
- To manage changes to the project schedule
- To track project expenses and budget modifications
- To ensure that the project's products, services, or results are consistent and meet requirements
- To monitor and control the project team's performance
Correct answer: To ensure that the project's products, services, or results are consistent and meet requirements
Correct answer: To ensure that the project's products, services, or results are consistent and meet requirements. Explanation: Configuration Management in project management is a process for maintaining the consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. It helps ensure that the project outputs remain consistent and meet the specified requirements and functionalities.
In project management, what does the 'Critical Chain Method' (CCM) primarily focus on?
- Identifying the project's longest sequence of dependent tasks
- Managing project resources constraints
- Estimating the project's total cost
- Allocating the project budget across tasks
Correct answer: Managing project resources constraints
Correct answer: Managing project resources constraints. Explanation: The Critical Chain Method (CCM) is a schedule management technique that focuses on managing resource constraints and reducing project duration by addressing resource availability. Unlike the Critical Path Method, which emphasizes task order and durations, CCM prioritizes resource allocation and incorporates buffers to manage risks and uncertainties.
What role does 'benefit cost ratio' (BCR) play in project selection?
- It determines the functional requirements of the project
- It assesses the feasibility of the project based on technical aspects
- It evaluates the financial viability of a project by comparing its benefits to its costs
- It identifies the project with the shortest duration
Correct answer: It evaluates the financial viability of a project by comparing its benefits to its costs
Correct answer: It evaluates the financial viability of a project by comparing its benefits to its costs. Explanation: The Benefit Cost Ratio (BCR) is a financial metric used in project selection and analysis. It compares the benefits of a project to its costs, helping stakeholders understand the financial value of undertaking the project. A BCR greater than 1 indicates that the project's benefits outweigh its costs, making it financially viable.
Which of the following is a key feature of 'Agile Project Management'?
- A fixed project scope that remains unchanged throughout the project lifecycle
- Regular adaptation to changes and ongoing stakeholder involvement
- Complete reliance on upfront planning and design phases
- Strict adherence to a predetermined sequence of project tasks
Correct answer: Regular adaptation to changes and ongoing stakeholder involvement
Correct answer: Regular adaptation to changes and ongoing stakeholder involvement. Explanation: Agile Project Management is characterized by its flexibility and adaptability to changes. It emphasizes regular feedback, continuous improvement, and active stakeholder involvement throughout the project lifecycle, rather than strictly following a fixed plan or scope.
The 'Resource Leveling' technique in project management is used to:
- Increase the project budget to incorporate additional resources
- Address conflicts among project stakeholders
- Even out resource allocation over the course of the project to address resource constraints
- Accelerate the project timeline to meet tight deadlines
Correct answer: Even out resource allocation over the course of the project to address resource constraints
Correct answer: Even out resource allocation over the course of the project to address resource constraints. Explanation: Resource Leveling is a technique used in project management to address resource constraints by evening out the demand for resources. It involves adjusting the start and finish dates of tasks to ensure that resources are not over-allocated, which might result in a project's duration being extended but helps in managing limited resources more effectively.
In project communication management, what is the primary purpose of an 'Information Distribution Matrix'?
- To identify and track project risks
- To allocate tasks among project team members
- To detail who needs what information, when they need it, and how it will be delivered
- To outline the project budget across different departments
Correct answer: To detail who needs what information, when they need it, and how it will be delivered
Correct answer: To detail who needs what information, when they need it, and how it will be delivered. Explanation: An Information Distribution Matrix is a tool used in project communication management to outline the information needs of project stakeholders. It specifies what information is needed, who needs it, when it is needed, and the methods for its distribution, ensuring efficient and effective communication throughout the project.
In the context of project time management, what is 'Resource Smoothing'?
- Adjusting the project schedule to expedite the project completion
- Adjusting resources so that their usage does not exceed certain predefined limits
- Reducing the project scope to meet resource availability
- Increasing the budget to hire additional resources
Correct answer: Adjusting resources so that their usage does not exceed certain predefined limits
Correct answer: Adjusting resources so that their usage does not exceed certain predefined limits. Explanation: Resource Smoothing is a technique used in project time management where the project schedule is adjusted in a way that the demand for resources does not exceed certain predefined limits, while the project's critical path remains unchanged. It aims to optimize the use of resources within the constraints of the project schedule.
What does 'Project Integration Management' primarily focus on?
- Managing the project budget and financial resources
- Ensuring that project processes are as efficient as possible
- Coordinating all aspects of the project plan to ensure cohesive project execution
- Integrating new technology tools into project management practices
Correct answer: Coordinating all aspects of the project plan to ensure cohesive project execution
Correct answer: Coordinating all aspects of the project plan to ensure cohesive project execution. Explanation: Project Integration Management is concerned with coordinating all elements of the project plan, including scope, time, cost, quality, human resources, communications, risk, procurement, and stakeholders, to ensure cohesive and consistent execution and alignment with project objectives.
The 'Delphi Technique' is used in project management for what purpose?
- To develop the project schedule
- To estimate project costs accurately
- To gather expert opinions on specific project-related issues anonymously
- To allocate resources efficiently across project tasks
Correct answer: To gather expert opinions on specific project-related issues anonymously
Correct answer: To gather expert opinions on specific project-related issues anonymously. Explanation: The Delphi Technique is a method used in project management to collect and distill the opinions of experts through a series of questionnaires, with the aim of reaching a consensus on specific project-related issues. It is done anonymously to prevent the influence of dominant individuals and to encourage honest and uninhibited feedback.
What is the significance of 'Sunk Costs' in project decision-making?
- They represent future costs that have not yet been incurred but are projected.
- They are indirect costs that are not directly attributable to the project activities.
- They are costs that have already been incurred and cannot be recovered.
- They include costs associated with the potential risks of the project.
Correct answer: They are costs that have already been incurred and cannot be recovered.
Correct answer: They are costs that have already been incurred and cannot be recovered. Explanation: Sunk Costs refer to the money that has already been spent and cannot be recovered. In project decision-making, it's important to ignore sunk costs when evaluating the viability of continuing a project or choosing between alternatives, as these costs should not influence future decisions.
Earned Schedule' technique in project management is used to:
- Calculate the total cost at the completion of the project.
- Determine the project's schedule variance and forecast its completion date.
- Allocate the project's budget across its various phases.
- Measure the team's performance and productivity.
Correct answer: Determine the project's schedule variance and forecast its completion date.
Correct answer: Determine the project's schedule variance and forecast its completion date. Explanation: Earned Schedule is an extension of Earned Value Management (EVM) that applies earned value concepts to the schedule dimension, allowing project managers to determine the schedule variance and forecast the project's completion date based on current performance.
The 'RACI Matrix' in project management is a tool used to:
- Identify and assess project risks.
- Develop a comprehensive project budget.
- Clarify roles and responsibilities in task completion.
- Schedule project tasks and milestones.
Correct answer: Clarify roles and responsibilities in task completion.
Correct answer: Clarify roles and responsibilities in task completion. Explanation: The RACI Matrix is a responsibility assignment chart that clarifies roles and responsibilities in completing tasks or deliverables within a project. RACI stands for Responsible, Accountable, Consulted, and Informed, helping to ensure clarity and alignment in who does what.
In project quality management, 'Control Charts' are used to:
- Track expenses over the course of the project.
- Monitor the time variance of project tasks.
- Analyze process variations and stability over time.
- Allocate resources based on project phases.
Correct answer: Analyze process variations and stability over time.
Correct answer: Analyze process variations and stability over time. Explanation: Control Charts are statistical tools used in project quality management to analyze how a process changes over time, identifying whether it is under control or if there are variations that might impact quality. They help in monitoring performance and ensuring processes remain within acceptable limits.
The process of 'Qualitative Risk Analysis' in project management involves:
- Quantifying the financial impact of each identified risk.
- Prioritizing risks based on their probability and impact on project objectives.
- Calculating the exact time delay risks will introduce to the project schedule.
- Assigning a specific cost to mitigating identified risks.
Correct answer: Prioritizing risks based on their probability and impact on project objectives.
Correct answer: Prioritizing risks based on their probability and impact on project objectives. Explanation: Qualitative Risk Analysis is a process used in project risk management to prioritize risks for further analysis or action by assessing their probability of occurrence and impact on project objectives. This helps in focusing on high-priority risks.
In project stakeholder management, the 'Power/Interest Grid' is used to:
- Calculate the budget required for stakeholder engagement activities.
- Schedule stakeholder meetings throughout the project lifecycle.
- Map stakeholders based on their level of authority and concern regarding project outcomes.
- Determine the salary increments for project team members based on stakeholder feedback.
Correct answer: Map stakeholders based on their level of authority and concern regarding project outcomes.
Correct answer: Map stakeholders based on their level of authority and concern regarding project outcomes. Explanation: The Power/Interest Grid is a stakeholder analysis tool that helps in mapping stakeholders according to their power to influence the project and their interest in the project outcomes. It assists in identifying which stakeholders need to be managed closely, monitored, kept informed, or kept satisfied.
Analogous Estimating' in project management is primarily used for:
- Determining the project's total cost by summing up individual task costs.
- Estimating the duration or cost of activities based on past similar projects.
- Calculating the exact amount of resources needed for each project phase.
- Developing a detailed schedule for the project execution phase.
Correct answer: Estimating the duration or cost of activities based on past similar projects.
Correct answer: Estimating the duration or cost of activities based on past similar projects. Explanation: Analogous Estimating is an estimation technique used in project management that uses the values of parameters, such as duration or cost, from a previous, similar project as the basis for estimating the same parameter for a current project. It is often used when there is limited information available.
In project management, what is the primary purpose of 'Cost Variance' (CV) analysis?
- To measure the degree of variation from the original project budget.
- To track the physical progress of the project against its schedule.
- To identify the effectiveness of the project communication plan.
- To evaluate the project team's performance efficiency.
Correct answer: To measure the degree of variation from the original project budget.
Correct answer: To measure the degree of variation from the original project budget. Explanation: Cost Variance (CV) analysis is a key component of Earned Value Management (EVM) and is used to measure the amount of budget variance at any given point in the project. It compares the budgeted cost of work performed with the actual cost of work performed, helping project managers understand whether the project is under, over, or exactly on budget.
What does the 'Schedule Performance Index' (SPI) indicate in project management?
- The efficiency of the team's use of allocated time for project tasks.
- The accuracy of the project's initial cost estimates.
- The effectiveness of the project's risk management efforts.
- The project team's ability to manage stakeholder expectations.
Correct answer: The efficiency of the team's use of allocated time for project tasks.
Correct answer: The efficiency of the team's use of allocated time for project tasks. Explanation: The Schedule Performance Index (SPI) is a measure used in Earned Value Management (EVM) to calculate the efficiency of time usage for project tasks. It is calculated by dividing the Earned Value (EV) by the Planned Value (PV). An SPI greater than 1 indicates that the project is ahead of schedule, while an SPI less than 1 indicates that the project is behind schedule.
In the context of project scope management, the 'Scope Baseline' includes which of the following components?
- Project charter, project schedule, and risk register
- Work Breakdown Structure (WBS), WBS Dictionary, and Scope Statement
- Project budget, stakeholder list, and communications plan
- Quality management plan, resource calendar, and procurement documents
Correct answer: Work Breakdown Structure (WBS), WBS Dictionary, and Scope Statement
Correct answer: Work Breakdown Structure (WBS), WBS Dictionary, and Scope Statement. Explanation: The Scope Baseline is a component of the project management plan that includes the approved version of a project scope statement, the Work Breakdown Structure (WBS), and its associated WBS Dictionary. It defines the project's detailed scope and is used as a basis for making future project decisions and for comparison with actual results.
Parametric Estimating' in project management is best described as:
- A technique that uses statistical methods to predict outcomes based on historical data.
- A method that applies project parameters, such as unit costs or historical productivity rates, to estimate project costs or durations.
- An approach that uses the project team's consensus to estimate project durations and costs.
- The process of breaking down the project scope into smaller parts to estimate costs more accurately.
Correct answer: A method that applies project parameters, such as unit costs or historical productivity rates, to estimate project costs or durations.
Correct answer: A method that applies project parameters, such as unit costs or historical productivity rates, to estimate project costs or durations. method that applies project parameters, such as unit costs or historical productivity rates, to estimate project costs or durations. Explanation: Parametric Estimating is a technique in project management that uses the relationship between variables (parameters) to calculate the cost or duration of a project. It often involves using unit costs and historical data to produce a more accurate estimate based on the quantities of the items being estimated.
What role does 'Variance at Completion' 'VAC' play in project management?
- It indicates the expected degree of variation in the project's final deliverables from the original scope.
- It forecasts the total cost variation between the project's budget at completion and its estimated cost at completion.
- It measures the project team's variance in performance from the project plan.
- It calculates the time variance between the project's scheduled completion and its actual completion date.
Correct answer: It forecasts the total cost variation between the project's budget at completion and its estimated cost at completion.
Correct answer: It forecasts the total cost variation between the project's budget at completion and its estimated cost at completion. Explanation: Variance at Completion 'VAC' is an Earned Value Management (EVM) metric that forecasts the difference between the budget at completion 'BAC' and the estimate at completion 'EAC'. It is used to predict whether the project will finish under, over, or on its original budget.
In project risk management, 'Secondary Risks' are best described as:
- Risks that arise as a direct result of implementing a risk response.
- Risks identified after the project has entered its closing phase.
- Minor risks that do not have a significant impact on the project's objectives.
- Risks that have been identified but are deemed unlikely to occur.
Correct answer: Risks that arise as a direct result of implementing a risk response.
Correct answer: Risks that arise as a direct result of implementing a risk response. Explanation: Secondary Risks are those risks that are a consequence of applying a risk response to an identified primary risk. These risks occur as a result of the actions taken to mitigate or avoid another risk, requiring their own set of responses and management strategies.
The technique of 'Progressive Elaboration' in project management is primarily used to:
- Incrementally improve the project plan as more detailed information becomes available.
- Reduce the project scope systematically to meet budget constraints.
- Increase the efficiency of project team members over the project lifecycle.
- Elaborate on the project's risks as the project progresses through its phases.
Correct answer: Incrementally improve the project plan as more detailed information becomes available.
Correct answer: Incrementally improve the project plan as more detailed information becomes available. Explanation: Progressive Elaboration is a technique where planning and documentation are developed in steps, and continue to be refined and detailed as more information becomes available. It acknowledges that a project cannot be completely planned at the outset and requires adjustments and refinements as work progresses and more is learned.
In the context of project scope management, which of the following tools or techniques is considered most effective for defining the project scope?
- Expert Judgment
- Market Research
- Stakeholder Analysis
- Product Analysis
Correct answer: Product Analysis
Correct answer: Product Analysis. Explanation: Product analysis is considered the most effective tool for defining the project scope because it involves understanding the characteristics of the product or service that the project is undertaken to create. This understanding helps in detailing the project scope, including the product requirements and project boundaries.
Which of the following risk response strategies involves allocating ownership of a threat to a third party?
- Mitigate
- Accept
- Transfer
- Avoid
Correct answer: Transfer
Correct answer: Transfer. Explanation: The transfer strategy involves shifting the impact of a risk, along with the responsibility for managing the response to that risk, to a third party. This strategy is often used with financial risks through mechanisms such as insurance or outsourcing contracts.
When performing quantitative risk analysis, which tool or technique is essential for determining the probability and impact of project risks?
- SWOT Analysis
- Monte Carlo Simulation
- Checklist Analysis
- Expert Judgment
Correct answer: Monte Carlo Simulation
Correct answer: Monte Carlo Simulation. Explanation: Monte Carlo Simulation is a tool or technique used in quantitative risk analysis to model the probability of different outcomes in a process that cannot easily be predicted due to the intervention of random variables. It is particularly useful for assessing the impact and likelihood of project risks.
In the context of project procurement management, which type of contract provides the greatest incentive for the seller to control costs and operate efficiently?
- Cost Plus Fixed Fee (CPFF)
- Fixed Price Incentive Fee (FPIF)
- Time and Materials (T&M)
- Cost Plus Incentive Fee (CPIF)
Correct answer: Cost Plus Incentive Fee (CPIF)
Correct answer: Cost Plus Incentive Fee (CPIF). Explanation: The Cost Plus Incentive Fee (CPIF) contract provides a reimbursement for all legitimate costs incurred during the project, but it also includes an additional incentive fee that is earned only if the seller meets defined performance criteria, such as staying under budget, which encourages efficient operation and cost control.
Which stakeholder engagement tool or technique involves analyzing quantitative and qualitative information to determine the interest of various stakeholders?
- Communication Models
- Stakeholder Mapping
- Engagement Assessment Matrix
- Power/Interest Grid
Correct answer: Power/Interest Grid
Correct answer: Power/Interest Grid. Explanation: The Power/Interest Grid is a tool used to categorize stakeholders based on their level of authority (power) and their level or concern (interest) regarding the project outcomes. This helps in prioritizing stakeholder engagement and management strategies.
In project communication management, what is the primary goal of the Manage Communications process?
- To ensure that project information is generated, collected, and disseminated
- To update the project management plan
- To archive project documents for future use
- To resolve project conflicts
Correct answer: To ensure that project information is generated, collected, and disseminated
Correct answer: To ensure that project information is generated, collected, and disseminated. Explanation: The primary goal of the Manage Communications process is to ensure timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information. This process enables effective internal and external communications with project stakeholders.
What is the main objective of the Perform Integrated Change Control process in project integration management?
- To approve or reject changes to the project scope
- To ensure that changes are recorded and evaluated
- To communicate changes to stakeholders
- To update the project schedule
Correct answer: To ensure that changes are recorded and evaluated
Correct answer: To ensure that changes are recorded and evaluated. Explanation: The main objective of the Perform Integrated Change Control process is to review all change requests, approve changes, and manage changes to the deliverables, organizational process assets, project documents, and the project management plan. It ensures that every proposed change is defined, reviewed, and approved before implementation.
Which of the following best describes the purpose of the Validate Scope process in project management?
- To formalize acceptance of the completed project deliverables
- To monitor the status of project activities
- To update the project management plan
- To control project costs
Correct answer: To formalize acceptance of the completed project deliverables
Correct answer: To formalize acceptance of the completed project deliverables. Explanation: The purpose of the Validate Scope process is to formalize acceptance of the completed project deliverables by the customer or sponsor. This process ensures that deliverables meet the acceptance criteria and receive formal acceptance, which is essential for the project's success.
Which document is primarily used to record and track detailed descriptions of identified risks along with their causes and consequences?
- Risk Register
- Risk Management Plan
- Stakeholder Register
- Project Charter
Correct answer: Risk Register
Correct answer: Risk Register. Explanation: The Risk Register is a document that is used to record details of identified risks, including their description, causes, and potential consequences. It serves as a central repository for all risks identified throughout the project, facilitating risk analysis and response planning.
In project quality management, which tool or technique involves the graphical representation of a process, showing the inputs, process actions, and outputs?
- Control Charts
- Flowcharts
- Histograms
- Scatter Diagrams
Correct answer: Flowcharts
Correct answer: Flowcharts. Explanation: Flowcharts are graphical representations of a process that show the sequence of steps, decisions that need to be made, and how processes interrelate. This tool is used in quality management to identify potential points of failure or inefficiencies in a process.
Which term describes the process of aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline?
- Cost Aggregation
- Budget Determination
- Cost Baseline
- Cost Forecasting
Correct answer: Cost Aggregation
Correct answer: Cost Aggregation. Explanation: Cost Aggregation is the process of summing the costs for individual activities or work packages to establish a total project cost, which then becomes part of the authorized cost baseline. This baseline is used to monitor and control project costs.
What is the main purpose of conducting a Procurement Audit in the context of project procurement management?
- To ensure compliance with the procurement plan
- To evaluate the effectiveness of the procurement process
- To review the accuracy of vendor invoices
- To determine the project's financial status
Correct answer: To evaluate the effectiveness of the procurement process
Correct answer: To evaluate the effectiveness of the procurement process. Explanation: A Procurement Audit is conducted to evaluate the effectiveness and efficiency of the procurement processes used in a project. It involves assessing whether the procurement activities met the project's objectives and identifying lessons learned to improve future procurement practices.
In the context of project communication management, what is the main advantage of using an interactive communication model?
- It is the most cost-effective method
- It allows for real-time feedback and adjustments
- It is suitable for large, dispersed audiences
- It requires minimal technology infrastructure
Correct answer: It allows for real-time feedback and adjustments
Correct answer: It allows for real-time feedback and adjustments. Explanation: The main advantage of using an interactive communication model is that it allows for two-way exchanges of information, including real-time feedback and adjustments. This model is particularly useful in complex or sensitive situations where understanding and agreement are critical.
Which process involves reviewing all change requests, approving changes, and managing changes to the project deliverables or project management plan?
- Direct and Manage Project Work
- Perform Integrated Change Control
- Control Scope
- Monitor and Control Project Work
Correct answer: Perform Integrated Change Control
Correct answer: Perform Integrated Change Control. Explanation: Perform Integrated Change Control is the process that involves reviewing all change requests, approving changes, and managing changes to the deliverables, organizational process assets, project documents, and the project management plan. This process ensures that every proposed change is defined, reviewed, and approved or rejected.
What does the "Parametric Estimating" technique involve in project cost management?
- Using historical data to estimate costs based on project parameters
- Aggregating the estimated costs of individual work packages
- Analyzing current market trends to forecast project costs
- Applying a percentage of the cost of similar projects to estimate costs
Correct answer: Using historical data to estimate costs based on project parameters
Correct answer: Using historical data to estimate costs based on project parameters. Explanation: Parametric Estimating involves using historical data and project parameters (such as square footage in construction) to calculate an estimate for project costs. This method is often more accurate than other estimating methods because it relies on the statistical relationship between historical data and other variables.
Which type of diagram is primarily used in project risk management to identify the root cause of a problem?
- Gantt Chart
- Ishikawa (Fishbone) Diagram
- Pareto Chart
- Work Breakdown Structure (WBS)
Correct answer: Ishikawa (Fishbone) Diagram
Correct answer: Ishikawa (Fishbone) Diagram. Explanation: The Ishikawa Diagram, also known as the Fishbone Diagram, is a cause-and-effect diagram that helps identify the root causes of a problem. It is particularly useful in project risk management for tracing adverse effects back to their root causes.
What is the primary focus of the "Plan Stakeholder Engagement" process in project stakeholder management?
- To monitor overall project stakeholder relationships
- To develop strategies to effectively engage stakeholders
- To identify all potential project stakeholders
- To communicate project information to stakeholders
Correct answer: To develop strategies to effectively engage stakeholders
Correct answer: To develop strategies to effectively engage stakeholders. Explanation: The primary focus of the "Plan Stakeholder Engagement" process is to develop appropriate strategies and plans for effectively engaging stakeholders based on their needs, expectations, interests, and potential impact on the project. This planning ensures that stakeholder engagement is managed throughout the project life cycle.
During which process group is the project management plan developed and approved?
- Initiating
- Planning
- Executing
- Monitoring and Controlling
Correct answer: Planning
Correct answer: Planning. Explanation: The project management plan is developed and approved during the Planning process group. This group involves defining the project's objectives and scope, and outlining the course of action required to achieve the project's goals.
In project schedule management, what does "fast tracking" involve?
- Increasing project resources to shorten the schedule
- Performing more activities in parallel
- Extending the project schedule to reduce costs
- Adding additional tasks to ensure quality
Correct answer: Performing more activities in parallel
Correct answer: Performing more activities in parallel. Explanation: Fast tracking is a schedule compression technique that involves performing more activities in parallel that were originally planned to be done in sequence. This approach can shorten the project schedule but may also increase risk and the potential for rework.
In Agile frameworks, what is the primary purpose of a "Spike"?
- To improve team morale through a fun activity
- To resolve technical debt accumulated in previous sprints
- To research a specific concept or create a simple prototype
- To re-evaluate and adjust the product backlog
Correct answer: To research a specific concept or create a simple prototype
Correct answer: To research a specific concept or create a simple prototype. Explanation: A "Spike" in Agile frameworks is undertaken to gain knowledge or solve a specific problem. It involves researching a concept or creating a prototype to understand the feasibility or technical aspects of a feature, thereby reducing uncertainty and risk in development tasks.
What Agile methodology emphasizes feature-driven development 'FDD' and is primarily focused on client-valued functionality?
- Scrum
- Kanban
- Lean
- Feature-Driven Development
Correct answer: Feature-Driven Development
Correct answer: Feature-Driven Development. Explanation: Feature-Driven Development 'FDD' is an Agile methodology that emphasizes building and delivering client-valued features in a short amount of time. It is distinct for its focus on designing and building features specifically identified as valuable to the client, often used in larger projects involving multiple teams.
In the context of Agile frameworks, what does the term "WIP Limit" stand for, and where is it most commonly applied?
- Work In Process Limit, applied in Scrum Sprints
- Work In Progress Limit, applied in Kanban systems
- Weekly Improvement Plan, applied in XP (Extreme Programming)
- Work Integration Point, applied in Lean Software Development
Correct answer: Work In Progress Limit, applied in Kanban systems
Correct answer: Work In Progress Limit, applied in Kanban systems. Explanation: WIP Limit, or Work In Progress Limit, is a fundamental concept in Kanban systems. It restricts the number of tasks in the different stages of workflow to prevent overloading the team, thereby promoting efficiency, reducing cycle times, and improving the flow of work.
Which of the following best describes the primary goal of the Scrum framework?
- To eliminate all forms of waste
- To ensure perfect product launches
- To facilitate team control of the development process
- To maximize the value of the product incrementally
Correct answer: To maximize the value of the product incrementally
Correct answer: To maximize the value of the product incrementally. Explanation: The primary goal of the Scrum framework is to maximize the product's value through iterative and incremental development. It emphasizes the delivery of product increments that are potentially shippable, allowing for regular feedback and adaptation.
What Agile practice involves breaking down a project into small, manageable sections that can be completed in short iterations or sprints?
- Continuous Integration
- Test-Driven Development
- Incremental Development
- Pair Programming
Correct answer: Incremental Development
Correct answer: Incremental Development. Explanation: Incremental Development is an Agile practice where a project is divided into small sections (increments), allowing for parts of the project to be developed, tested, and delivered in short cycles or iterations, known as sprints in Scrum methodology. This enables quicker feedback and more adaptive planning.
In Lean Software Development, which principle focuses on ensuring that effort is concentrated only on the work that adds value to the end product?
- Amplify Learning
- Empower the Team
- Eliminate Waste
- Build Integrity In
Correct answer: Eliminate Waste
Correct answer: Eliminate Waste. Explanation: The principle of "Eliminate Waste" in Lean Software Development focuses on removing any activities, processes, or materials that do not add value to the end customer. It aims to improve efficiency by reducing unnecessary work and focusing resources on value-adding activities.
Which Agile framework is specifically designed to facilitate scalable coordination and collaboration among multiple agile teams working on the same product?
- Large-Scale Scrum (LeSS)
- Scrum of Scrums
- Scaled Agile Framework (SAFe)
- Disciplined Agile Delivery 'DAD'
Correct answer: Scaled Agile Framework (SAFe)
Correct answer: Scaled Agile Framework (SAFe). Explanation: The Scaled Agile Framework (SAFe) is designed to provide a guide for large organizations to scale Agile and Lean practices beyond single teams. It facilitates coordination, alignment, and collaboration among multiple agile teams, ensuring that they work together effectively towards common goals.
In Extreme Programming (XP), what practice ensures that system changes can be made at any time without affecting system integrity?
- Continuous Integration
- Refactoring
- Pair Programming
- Test-Driven Development
Correct answer: Refactoring
Correct answer: Refactoring. Explanation: Refactoring in Extreme Programming (XP) involves restructuring existing code without changing its external behavior to improve its internal structure. This practice ensures that the system can be modified or extended at any time while maintaining its integrity, making it easier to manage and evolve.
Which statement best describes the purpose of the "Definition of Done" 'DoD' in Agile methodologies?
- To outline the tasks required for project initiation
- To provide a checklist of items to be completed before a product can be released
- To describe the criteria under which a project task is considered complete
- To detail the responsibilities of the project manager
Correct answer: To describe the criteria under which a project task is considered complete
Correct answer: To describe the criteria under which a project task is considered complete. Explanation: The "Definition of Done" 'DoD' in Agile methodologies is a shared understanding among team members of the criteria that must be met for work to be considered complete. This ensures quality and completeness in deliverables by providing clear, objective criteria for completion.
In the Kanban method, what is the purpose of the "Cumulative Flow Diagram" 'CFD'?
- To identify team members' individual contributions
- To visualize the stability and efficiency of the workflow
- To track the total project costs
- To allocate resources across projects
Correct answer: To visualize the stability and efficiency of the workflow
Correct answer: To visualize the stability and efficiency of the workflow. Explanation: The Cumulative Flow Diagram 'CFD' in the Kanban method is a visual tool that shows the number of tasks in each stage of the workflow over time. It helps identify bottlenecks, measure lead time, and visualize the stability and efficiency of the workflow, thereby aiding in continuous improvement.
In Agile frameworks, what is the role of a "Product Owner"?
- To manage the project schedule and budget
- To ensure the technical quality of the product
- To represent the stakeholders' interests and prioritize the product backlog
- To facilitate daily stand-up meetings
Correct answer: To represent the stakeholders' interests and prioritize the product backlog
Correct answer: To represent the stakeholders' interests and prioritize the product backlog. Explanation: The Product Owner in Agile frameworks is responsible for representing the interests of the stakeholders, including customers and users. They prioritize the product backlog items according to business value and are the key decision-maker regarding what features the product will have.
In Agile project management, which metric is most useful for assessing the team's productivity over time?
- Number of tasks completed
- Lines of code written
- Velocity
- Hours worked
Correct answer: Velocity
Correct answer: Velocity. Explanation: Velocity, measured in units like story points completed per iteration, is a key Agile metric that assesses a team's productivity over time. It reflects the amount of work a team can complete in a specific timeframe, allowing for better planning and forecasting of future sprints.
What Agile framework employs the concept of "Artifacts" to ensure transparency and facilitate communication among team members?
- Scrum
- Kanban
- Lean
- XP (Extreme Programming)
Correct answer: Scrum
Correct answer: Scrum. Explanation: Scrum employs the concept of "Artifacts," such as the Product Backlog, Sprint Backlog, and Product Increment, to ensure transparency and facilitate communication among team members. These artifacts provide essential information that helps everyone involved in the project understand what is being worked on and what has been completed.
Which of the following best defines the term "Epic" in Agile methodologies?
- A small, user-centric feature that can be completed in a single sprint
- A large body of work that can be broken down into smaller stories or tasks
- A testing phase that occurs at the end of every sprint
- A daily meeting where team members discuss progress
Correct answer: A large body of work that can be broken down into smaller stories or tasks
Correct answer: A large body of work that can be broken down into smaller stories or tasks. large body of work that can be broken down into smaller stories or tasks. Explanation: An "Epic" in Agile methodologies is a large body of work that encompasses many user stories or tasks. It is too big to be completed in a single sprint and therefore needs to be broken down into more manageable parts that can be completed incrementally.
In the context of Scrum, what is the primary role of the Scrum Master?
- To prioritize the product backlog
- To represent the customer and stakeholders
- To facilitate Scrum ceremonies and remove impediments
- To ensure the product meets quality standards
Correct answer: To facilitate Scrum ceremonies and remove impediments
Correct answer: To facilitate Scrum ceremonies and remove impediments. Explanation: The primary role of the Scrum Master is to facilitate Scrum ceremonies (like daily stand-ups, sprint planning, reviews, and retrospectives) and to remove impediments that may obstruct the team's progress. The Scrum Master acts as a servant-leader for the Scrum Team, ensuring that the Scrum framework is followed and the team can work efficiently.
Which Lean principle is focused on the concept of "pulling" work only when there is a demand to reduce overproduction?
- Just-In-Time (JIT)
- Kaizen
- Genchi Genbutsu
- Jidoka
Correct answer: Just-In-Time (JIT)
Correct answer: Just-In-Time (JIT). Explanation: The Just-In-Time (JIT) principle in Lean focuses on "pulling" work through the system only when there is a demand, aiming to reduce overproduction and inventory costs. This principle ensures that production matches customer demand more closely, improving efficiency and reducing waste.
What is the purpose of "User Stories" in Agile development?
- To document the technical specifications of a feature
- To provide detailed instructions for the development team
- To describe features from the perspective of the end user
- To outline the project's budget and resources
Correct answer: To describe features from the perspective of the end user
Correct answer: To describe features from the perspective of the end user. Explanation: User Stories in Agile development are short, simple descriptions of a feature told from the perspective of the end user or customer. They focus on the value or outcome the user receives, helping the development team understand what they are building and why, and promoting a user-centric approach to product development.
In Agile methodologies, which practice is used to continuously reassess priorities and plans, based on feedback and results from previous work?
- Continuous Deployment
- Agile Modeling
- Adaptive Planning
- Code Refactoring
Correct answer: Adaptive Planning
Correct answer: Adaptive Planning. Explanation: Adaptive Planning is a practice in Agile methodologies that involves continuously reassessing work priorities and plans based on feedback and results from previous iterations. This approach allows teams to remain flexible and responsive to changes, ensuring that the product evolves in the most valuable way for the customer.
Which concept is essential in XP (Extreme Programming) and involves writing automated tests before the actual code?
- Continuous Integration
- Refactoring
- Pair Programming
- Test-Driven Development 'TDD'
Correct answer: Test-Driven Development 'TDD'
Correct answer: Test-Driven Development 'TDD'. Explanation: Test-Driven Development 'TDD' is a core practice in Extreme Programming (XP) that involves writing automated tests before the actual code to implement a new feature. This ensures that the code meets its requirements from the start and facilitates high-quality, bug-free software development.
Which of the following techniques is MOST effective in identifying underlying requirements in a complex project?
- Brainstorming
- Requirement elicitation via prototypes
- Stakeholder interviews
- Document analysis
Correct answer: Requirement elicitation via prototypes
Correct answer: Requirement elicitation via prototypes. Explanation: Requirement elicitation via prototypes is most effective in identifying underlying requirements in complex projects because it allows stakeholders to interact with a working model of the system. This interaction often reveals additional requirements and clarifies existing ones by providing a concrete basis for feedback.
In the context of business analysis, which diagram technique is best used for understanding and documenting system processes and flows?
- Gantt Chart
- Fishbone Diagram
- Data Flow Diagram
- SWOT Analysis
Correct answer: Data Flow Diagram
Correct answer: Data Flow Diagram. Explanation: A Data Flow Diagram (DFD) is best suited for understanding and documenting system processes and flows. It visually represents the flow of data through a system, making it easier to understand how the system operates, including inputs, outputs, and data stores.
Which tool or technique is most beneficial for prioritizing the requirements based on their value to stakeholders and the project's objectives?
- Cost-benefit analysis
- MoSCoW method
- Pareto analysis
- Requirement traceability matrix
Correct answer: MoSCoW method
Correct answer: MoSCoW method. Explanation: The MoSCoW method is most beneficial for prioritizing requirements because it categorizes them into Must have, Should have, Could have, and Won't have. This method helps in aligning requirements with stakeholder expectations and project objectives efficiently.
In which phase of the business analysis process would you primarily conduct a stakeholder analysis?
- Planning and Monitoring
- Elicitation and Collaboration
- Requirements Life Cycle Management
- Strategy Analysis
Correct answer: Strategy Analysis
Correct answer: Strategy Analysis. Explanation: Stakeholder analysis is primarily conducted during the Strategy Analysis phase. This phase focuses on assessing the needs of stakeholders and the business environment to define an appropriate strategy for change.
What is the primary purpose of utilizing a Balanced Scorecard in business analysis?
- To track and manage project schedule
- To evaluate organizational performance from multiple perspectives
- To assess the quality of project deliverables
- To document the business requirements
Correct answer: To evaluate organizational performance from multiple perspectives
Correct answer: To evaluate organizational performance from multiple perspectives. Explanation: The primary purpose of utilizing a Balanced Scorecard in business analysis is to evaluate organizational performance from multiple perspectives, including financial, customer, internal business processes, and learning and growth, providing a holistic view of performance beyond traditional financial measures.
Which analysis technique is most effective for determining the root cause of a problem by identifying its contributing factors?
- PESTLE Analysis
- Monte Carlo Simulation
- Root Cause Analysis
- Benchmarking
Correct answer: Root Cause Analysis
Correct answer: Root Cause Analysis. Explanation: Root Cause Analysis is the most effective technique for determining the root cause of a problem because it systematically breaks down the problem and identifies its underlying causes, rather than just addressing the symptoms.
What is the main benefit of applying the SWOT Analysis in project management?
- Identifying the project schedule
- Analyzing the project's strengths, weaknesses, opportunities, and threats
- Estimating project costs
- Determining project scope
Correct answer: Analyzing the project's strengths, weaknesses, opportunities, and threats
Correct answer: Analyzing the project's strengths, weaknesses, opportunities, and threats. Explanation: The main benefit of applying SWOT Analysis in project management is that it provides a comprehensive overview of the internal and external factors that can affect project success, allowing for more informed decision-making and strategy development.
When applying the Pareto principle in business analysis, what is the expected outcome?
- Equal importance given to all requirements
- 80% of problems are caused by 20% of causes
- Stakeholder expectations are managed through negotiation
- All projects will be completed within budget
Correct answer: 80% of problems are caused by 20% of causes
Correct answer: 80% of problems are caused by 20% of causes. Explanation: The Pareto principle, or 80/20 rule, when applied in business analysis, suggests that 80% of problems or effects come from 20% of causes. This helps in focusing efforts on the most significant factors affecting the project or process.
Which document is essential for ensuring that all project requirements are met and aligned with the project's objectives?
- Project scope statement
- Business case
- Requirements traceability matrix
- Stakeholder register
Correct answer: Requirements traceability matrix
Correct answer: Requirements traceability matrix. Explanation: The Requirements Traceability Matrix (RTM) is essential for ensuring that all project requirements are met and aligned with the project's objectives. It tracks each requirement throughout the project lifecycle, helping to ensure that requirements are delivered as specified.
In business analysis, what is the primary focus of the 'Requirements Life Cycle Management' knowledge area?
- Defining project costs and budget
- Managing and maintaining requirements from inception to retirement
- Establishing the project team and roles
- Conducting market research
Correct answer: Managing and maintaining requirements from inception to retirement
Correct answer: Managing and maintaining requirements from inception to retirement. Explanation: The primary focus of the 'Requirements Life Cycle Management' knowledge area in business analysis is managing and maintaining requirements throughout their lifecycle, from inception through to retirement. This includes tracing, prioritization, and validation to ensure they continue to meet business needs.
What technique is used to facilitate a structured exploration of all possible outcomes of a decision and their impacts on a project?
- Risk Matrix
- Decision Tree Analysis
- Critical Path Method
- Earned Value Analysis
Correct answer: Decision Tree Analysis
Correct answer: Decision Tree Analysis. Explanation: Decision Tree Analysis is used to facilitate a structured exploration of all possible outcomes of a decision and their impacts on a project. It visually maps out the decisions, chance events, and possible outcomes, allowing for a comprehensive assessment of risks and benefits.
Which approach in business analysis is primarily focused on minimizing waste and maximizing value through continuous improvement?
- Waterfall Methodology
- Lean Methodology
- Agile Methodology
- Six Sigma
Correct answer: Lean Methodology
Correct answer: Lean Methodology. Explanation: Lean Methodology is primarily focused on minimizing waste and maximizing value through continuous improvement. It emphasizes the importance of delivering value to the customer by streamlining processes and eliminating non-value-added activities.
What is the main goal of the Value Chain Analysis in business analysis?
- To identify the project's critical path
- To map out the organization's strategic advantages
- To understand how activities within an organization create value for customers
- To allocate project resources effectively
Correct answer: To understand how activities within an organization create value for customers
Correct answer: To understand how activities within an organization create value for customers. Explanation: The main goal of Value Chain Analysis is to understand how activities within an organization create value for customers. It examines the inputs, processes, and outputs involved in the production of a product or service, identifying opportunities for competitive advantage.
In business analysis, which tool is most effective for visualizing the relationships among various components of a complex system?
- Workflow Diagrams
- System Dynamics Modeling
- Gantt Charts
- Use Case Diagrams
Correct answer: System Dynamics Modeling
Correct answer: System Dynamics Modeling. Explanation: System Dynamics Modeling is most effective for visualizing the relationships among various components of a complex system. It uses stocks, flows, feedback loops, and time delays to represent the interactions within a system, facilitating understanding and analysis of dynamic behaviors.
Which technique helps in identifying the impact of external environmental factors on a project's success?
- PESTLE Analysis
- Resource Breakdown Structure
- WBS (Work Breakdown Structure)
- RACI Matrix
Correct answer: PESTLE Analysis
Correct answer: PESTLE Analysis. Explanation: PESTLE Analysis helps in identifying the impact of external environmental factors on a project's success. It examines Political, Economic, Social, Technological, Legal, and Environmental factors, providing insights into external influences that could affect project outcomes.
How is Monte Carlo Simulation used in business analysis?
- To create a detailed project schedule
- To analyze the probability of completing tasks within budget and time constraints
- To assign tasks to project team members
- To develop a project budget
Correct answer: To analyze the probability of completing tasks within budget and time constraints
Correct answer: To analyze the probability of completing tasks within budget and time constraints. Explanation: Monte Carlo Simulation is used in business analysis to analyze the probability of completing tasks within budget and time constraints. It employs random sampling and statistical modeling to estimate the likelihood of achieving various outcomes, aiding in risk assessment and decision-making.
What purpose does the Use Case Diagram serve in business analysis?
- To track project expenses
- To represent the actions that a system can perform with external users
- To assign project roles and responsibilities
- To document project scope
Correct answer: To represent the actions that a system can perform with external users
Correct answer: To represent the actions that a system can perform with external users. Explanation: The Use Case Diagram serves the purpose of representing the actions that a system can perform with external users. It visually describes how different users interact with the system, outlining the system's functionality and requirements from the user's perspective.
In the context of project management, what is the primary focus of Gap Analysis?
- Identifying differences between current project status and desired goals
- Documenting the work required to complete a project
- Calculating the budget needed for project completion
- Establishing a project timeline
Correct answer: Identifying differences between current project status and desired goals
Correct answer: Identifying differences between current project status and desired goals. Explanation: The primary focus of Gap Analysis in project management is to identify differences between the current project status and the desired goals. It helps in understanding the gaps that need to be addressed to achieve project objectives, facilitating strategic planning and execution.
Which methodology advocates for adaptive planning, evolutionary development, early delivery, and continual improvement, and encourages rapid and flexible response to change?
- Agile Methodology
- Waterfall Methodology
- PRINCE2
- Six Sigma
Correct answer: Agile Methodology
Correct answer: Agile Methodology. Explanation: Agile Methodology advocates for adaptive planning, evolutionary development, early delivery, and continual improvement, and encourages rapid and flexible response to change. It is characterized by its iterative approach and its focus on customer collaboration and responsiveness to change.
What is the primary objective of conducting a Stakeholder Impact Analysis in business analysis?
- To determine the financial impact of a project
- To identify how different stakeholders will be affected by a project
- To allocate project resources
- To schedule project tasks
Correct answer: To identify how different stakeholders will be affected by a project
Correct answer: To identify how different stakeholders will be affected by a project. Explanation: The primary objective of conducting a Stakeholder Impact Analysis is to identify how different stakeholders will be affected by a project. It helps in understanding stakeholders' interests, expectations, and potential influence, which is crucial for stakeholder engagement and project success.
How does a Business Model Canvas assist in business analysis?
- By outlining the project's budgetary requirements
- By defining project deliverables
- By providing a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances
- By scheduling project activities
Correct answer: By providing a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances
Correct answer: By providing a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances. Explanation: A Business Model Canvas assists in business analysis by providing a visual chart with elements describing a firm's value proposition, infrastructure, customers, and finances. It offers a holistic view of the business model, facilitating strategic planning and analysis.
Which analysis tool is best suited for identifying the strategic fit between an organization's internal capabilities and external opportunities?
- Cost-Benefit Analysis
- SWOT Analysis
- Pareto Chart
- Resource Histogram
Correct answer: SWOT Analysis
Correct answer: SWOT Analysis. Explanation: SWOT Analysis is best suited for identifying the strategic fit between an organization's internal capabilities (Strengths and Weaknesses) and external opportunities (Opportunities and Threats). It helps organizations in strategic planning by aligning their internal strengths and weaknesses with external opportunities and threats.
Which technique is crucial for understanding the stakeholders' power, interest, and influence over a project?
- Stakeholder Mapping
- Critical Path Method
- Delphi Technique
- Benchmarking
Correct answer: Stakeholder Mapping
Correct answer: Stakeholder Mapping. Explanation: Stakeholder Mapping is crucial for understanding the stakeholders' power, interest, and influence over a project. It involves identifying project stakeholders and categorizing them according to their level of interest, influence, and impact on the project, enabling effective stakeholder management strategies.
What is the purpose of applying the Critical Success Factor (CSF) method in business analysis?
- To identify the financial viability of project investments
- To determine key areas that must be successfully managed to achieve project objectives
- To assess the project team's performance
- To evaluate the technical feasibility of a project
Correct answer: To determine key areas that must be successfully managed to achieve project objectives
Correct answer: To determine key areas that must be successfully managed to achieve project objectives. Explanation: The purpose of applying the Critical Success Factor (CSF) method in business analysis is to determine key areas that must be successfully managed to achieve project objectives. CSFs are the essential elements critical for a project or organization to accomplish its mission, focusing management's attention on the most important success factors.
How does the Kanban methodology aid in business analysis and project management?
- By fixing the schedule for project deliverables
- By minimizing waste through lean production
- By visualizing work, limiting work in progress, and maximizing efficiency
- By ensuring compliance with regulatory standards
Correct answer: By visualizing work, limiting work in progress, and maximizing efficiency
Correct answer: By visualizing work, limiting work in progress, and maximizing efficiency. Explanation: The Kanban methodology aids in business analysis and project management by visualizing work, limiting work in progress, and maximizing efficiency. It enables teams to manage the flow of tasks and projects more effectively by using visual signals or Kanban boards, thus improving productivity and reducing bottlenecks.
In business analysis, what is the primary purpose of utilizing a Responsibility Assignment Matrix (RAM), such as a RACI chart?
- To track project expenses
- To prioritize project risks
- To assign and clarify roles and responsibilities in project tasks
- To document technical specifications
Correct answer: To assign and clarify roles and responsibilities in project tasks
Correct answer: To assign and clarify roles and responsibilities in project tasks. Explanation: The primary purpose of utilizing a Responsibility Assignment Matrix (RAM), such as a RACI chart, in business analysis is to assign and clarify roles and responsibilities in project tasks. It helps in defining who is Responsible, Accountable, Consulted, and Informed for each task, ensuring clear communication and efficient task allocation among team members.
What role does Business Process Modeling Notation (BPMN) play in business analysis?
- It serves as a guideline for project budgeting
- It provides a standardized method for documenting business processes
- It is used to allocate resources to project phases
- It helps in identifying potential project sponsors
Correct answer: It provides a standardized method for documenting business processes
Correct answer: It provides a standardized method for documenting business processes. Explanation: Business Process Modeling Notation (BPMN) plays a crucial role in business analysis by providing a standardized method for documenting business processes. BPMN offers a graphical representation of business workflows, enabling clear communication, understanding, and analysis of business processes among stakeholders.
Which tool is used in business analysis to depict the flow of information through a system and its processes, identifying inputs and outputs?
- Entity-Relationship Diagram 'ERD'
- Gantt Chart
- Control Flow Diagram
- Context Diagram
Correct answer: Context Diagram
Correct answer: Context Diagram. Explanation: A Context Diagram is used in business analysis to depict the flow of information through a system and its processes, identifying inputs and outputs. It provides a high-level overview of a system's boundaries, external entities that interact with the system, and the information flow between the system and those entities.
A team is debating how to describe their work to a new sponsor. They need a one-sentence definition of what a project actually is. Which description fits the standard definition used in project management?
- A temporary endeavor undertaken to create a unique product, service, or result
- Any task that requires more than one person and at least a week of effort
- A funded initiative that must always generate measurable profit within a year
- A repeating set of operational activities that keep the business running day to day
Correct answer: A temporary endeavor undertaken to create a unique product, service, or result
The correct description is a temporary endeavor undertaken to create a unique product, service, or result. The two defining traits are that a project is temporary (it has a definite start and end) and that it produces something unique. Ongoing operational activities are repetitive and do not end, so they are not projects, and a project does not have to be profitable to qualify.
A company groups its initiatives into three tiers: a single effort to launch one mobile app, a coordinated set of related apps managed together for shared benefits, and the full collection of all initiatives ranked against strategic goals. What are these three tiers, in order?
- Project, program, portfolio
- Portfolio, program, project
- Program, project, portfolio
- Project, portfolio, program
Correct answer: Project, program, portfolio
In order, these are a project, a program, and a portfolio. A project produces a single unique outcome, a program is a group of related projects managed together to obtain benefits not available from managing them separately, and a portfolio is the collection of all projects, programs, and operations grouped to meet strategic objectives. The portfolio is the broadest level and is about choosing the right work, while the project is the narrowest.
During a sponsor briefing, someone asks the project team to explain the high-level groupings of project management activity, sometimes called the process groups. Which list correctly names the five process groups?
- Concept, Definition, Development, Deployment, Review
- Discovery, Design, Build, Test, Release
- Charter, Scope, Schedule, Budget, Handover
- Initiating, Planning, Executing, Monitoring and Controlling, Closing
Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, Closing
The five process groups are Initiating, Planning, Executing, Monitoring and Controlling, and Closing. These are logical groupings of activity that can repeat across phases rather than a strict one-time sequence. The other lists describe life-cycle phases or generic stages that are not the recognized process groups.
A team is creating a document that lists every person and group affected by an upcoming office relocation, along with their roles, expectations, and influence. They will later create a separate plan describing how often to communicate with each one and how to win their support. Which document captures the list of these people and their attributes?
- The project charter
- The stakeholder register
- The communications matrix
- The stakeholder engagement plan
Correct answer: The stakeholder register
The list of people and their attributes belongs in the stakeholder register, which identifies stakeholders and records their roles, interests, expectations, and influence. The stakeholder engagement plan is a different artifact that describes the strategies for involving them and moving them toward desired engagement levels. The register is about who they are; the engagement plan is about what you will do with them.
A new team member asks who, exactly, counts as a stakeholder on their project. Which answer is correct?
- Only the people who provide funding or formally sign off on deliverables
- Only external customers who will ultimately use the product
- Any individual or group that can affect, be affected by, or perceive itself to be affected by the project
- Only the project manager and the assigned core team members
Correct answer: Any individual or group that can affect, be affected by, or perceive itself to be affected by the project
A stakeholder is any individual or group that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project. This deliberately broad definition includes sponsors, the team, customers, regulators, end users, and even people who only believe they are affected. Limiting it to funders or only the team would miss people whose concerns must still be managed.
A stakeholder insists the project add several new features after the schedule and budget are locked, and the team keeps quietly absorbing them without revising the plan. What is this uncontrolled growth called, and what is the recommended way to handle new requests?
- Progressive elaboration; accept all requests since detail naturally increases
- Gold plating; reward the team for exceeding the original requirements
- Scope creep; route every new request through an agreed change control process
- Fast tracking; overlap the new work with existing work to save time
Correct answer: Scope creep; route every new request through an agreed change control process
This uncontrolled growth is scope creep, and the recommended response is to route every new request through an agreed change control process so impacts to time, cost, and quality are evaluated before acceptance. Progressive elaboration is the legitimate refinement of detail over time, not the unmanaged addition of work, and gold plating is adding extras nobody asked for.
A team is defining scope for a website redesign. They want a clear statement of the work required and only the work required to deliver the product. Which statement best captures what scope means in project management?
- The calendar dates by which each deliverable must be finished
- The list of risks that could threaten the project's objectives
- The sum of the products, services, and results to be provided, and the work needed to produce them
- The total amount of money authorized for the project
Correct answer: The sum of the products, services, and results to be provided, and the work needed to produce them
Scope is the sum of the products, services, and results to be provided as the project, together with the work required to produce them. It answers what is and is not included. Budget concerns cost, the risk list concerns uncertainty, and dates concern schedule; none of those define scope, although all are constrained by it.
A traditional team commits to a fixed scope up front and follows a detailed, sequential plan, while a neighboring team works in short iterations, replanning each cycle as requirements emerge. Which statement best contrasts these two approaches?
- Agile approaches require fixed scope while predictive approaches allow scope to change freely
- Predictive approaches plan scope in detail early and change it through formal control, while agile approaches deliver iteratively and embrace evolving requirements
- The two approaches are identical except that agile uses longer phases
- Predictive approaches deliver value only at the end while agile approaches never produce documentation
Correct answer: Predictive approaches plan scope in detail early and change it through formal control, while agile approaches deliver iteratively and embrace evolving requirements
The accurate contrast is that predictive (plan-based) approaches define scope in detail early and manage changes through formal change control, while agile approaches deliver in short iterations and expect requirements to evolve. Predictive work suits stable, well-understood requirements; agile suits high uncertainty. Agile still produces documentation and value throughout, so the claims that it never documents or fixes scope are wrong.
A project has stable, well-defined requirements for its hardware components but highly uncertain, fast-changing requirements for its companion software. The team decides to manage the hardware with a plan-based approach and the software in iterations. What is this combined approach called?
- A phase-gate-only approach
- A purely predictive approach
- A hybrid approach
- A purely agile approach
Correct answer: A hybrid approach
Combining plan-based and iterative methods on the same effort is a hybrid approach. Teams choose hybrid when different parts of the work have different levels of certainty, applying predictive methods where requirements are stable and agile methods where they are volatile. Calling it purely predictive or purely agile would misrepresent the deliberate mix being used.
A sponsor asks the team to explain the broad series of stages every project passes through from start to finish, regardless of the chosen methodology. What is this overall series called?
- The work breakdown structure
- The change control board
- The project life cycle
- The critical path
Correct answer: The project life cycle
The broad series of stages a project passes through from start to finish is the project life cycle. It provides the basic framework for managing the project no matter which development approach is used. The critical path is a schedule concept, the work breakdown structure decomposes scope, and the change control board reviews changes, so none of those describes the overall life cycle.
A team maps their initiative into stages such as starting the project, organizing and preparing, carrying out the work, and ending the project. These represent the generic phases of which concept?
- The triple constraint
- The five process groups
- The stakeholder engagement levels
- The project life cycle phases
Correct answer: The project life cycle phases
Stages such as starting, organizing and preparing, carrying out the work, and ending the project are the generic project life cycle phases. Phases are time-bound stages of the work, whereas the process groups are logical groupings of management activity that can repeat within any phase. Confusing the two is common, but phases describe where the project is in its life span.
A team is asked which three interrelated factors classically constrain a project so that changing one usually forces a trade-off in the others. Which set names this classic relationship?
- Scope, schedule (time), and cost
- Charter, baseline, and milestone
- Stakeholders, communication, and resources
- Quality, risk, and procurement
Correct answer: Scope, schedule (time), and cost
The classic triple constraint is scope, schedule (time), and cost, where adjusting one typically forces a trade-off among the others, with quality often shown as affected by all three. The other groupings list legitimate project management topics but are not the traditional triple constraint that illustrates competing demands.
A sponsor wants to know what authorizes the project to exist and gives the project manager authority to apply organizational resources. Several details are mentioned. Which set best reflects what a project charter typically includes?
- The full work breakdown structure and the signed acceptance of all deliverables
- The lessons learned register and the final performance reports
- A complete activity-level schedule, the detailed budget, and the final risk register
- High-level requirements, objectives, a summary milestone schedule, the assigned project manager, and the sponsor's authorization
Correct answer: High-level requirements, objectives, a summary milestone schedule, the assigned project manager, and the sponsor's authorization
A project charter typically includes high-level requirements and objectives, a summary milestone schedule, the assigned project manager and authority level, and the sponsor's authorization that formally launches the project. It is intentionally high level. Detailed schedules, budgets, the full work breakdown structure, and final acceptance documents are produced later, not in the charter.
Before any planning begins, the sponsor signs a document that formally authorizes the project and names the project manager. A team member asks what this single document is called. What is the answer?
- The scope statement
- The project charter
- The project management plan
- The business case
Correct answer: The project charter
The document that formally authorizes the project and names the project manager is the project charter. The business case justifies the investment and usually precedes the charter, the scope statement details what is included once planning starts, and the project management plan is the comprehensive guide built during planning. Only the charter formally authorizes the project's existence.
A team finishes a usable component of the larger product and prepares to hand it over for verification. They refer to this measurable, verifiable output. What is such an output called?
- A constraint
- An assumption
- A deliverable
- A milestone
Correct answer: A deliverable
A measurable, verifiable output produced to complete a process, phase, or project is a deliverable. Deliverables are tangible or intangible results that can be handed off and verified. A milestone marks a significant point in time but has zero duration and produces nothing by itself, and a constraint is a limiting factor rather than an output.
A project schedule shows several zero-duration points that mark significant events, such as 'design approved' and 'system go-live.' What are these points called, and what is their purpose?
- Dependencies; they define the logical order between activities
- Work packages; they represent the smallest schedulable units of effort
- Buffers; they absorb schedule risk along the critical path
- Milestones; they mark significant moments and have no duration of their own
Correct answer: Milestones; they mark significant moments and have no duration of their own
These zero-duration points are milestones, used to mark significant moments such as approvals, phase ends, or major deliverables, and they consume no time or resources themselves. Work packages are actual units of work with duration, buffers absorb uncertainty, and dependencies define sequencing. Milestones are checkpoints, not work.
At project close, the team consolidates the knowledge gained, what went well, what went poorly, and recommended improvements, into a document so future projects can benefit. What is this document called?
- The risk register
- The issue log
- The stakeholder register
- The lessons learned register
Correct answer: The lessons learned register
The document capturing knowledge gained, including what went well, what went poorly, and recommended improvements, is the lessons learned register. It is built throughout the project and finalized at close so the organization can reuse the knowledge. The risk register tracks uncertainties, the stakeholder register tracks people, and the issue log tracks current problems.
A team wants to be sure they capture lessons learned while events are fresh rather than only at the very end. When should the lessons learned register ideally be updated?
- Continuously throughout the project, then finalized at closure
- Only at the formal closing of the project
- Only when a major risk actually occurs
- Only during project initiation
Correct answer: Continuously throughout the project, then finalized at closure
The lessons learned register should be updated continuously throughout the project and then finalized at closure. Capturing knowledge in the moment prevents valuable detail from being forgotten and lets the current project itself benefit from earlier lessons. Waiting until the very end risks losing insight and gives no chance to apply lessons mid-project.
A team wants a single chart that clarifies, for each task, exactly who does the work, who is ultimately answerable, who is asked for input, and who just needs updates. Which tool provides this?
- A network diagram
- A Gantt chart
- A RACI matrix
- A risk register
Correct answer: A RACI matrix
The chart that clarifies, per task, who is Responsible, Accountable, Consulted, and Informed is a RACI matrix. It is a form of responsibility assignment matrix that prevents confusion over ownership. A Gantt chart shows schedule, a risk register tracks uncertainty, and a network diagram shows activity dependencies; none assigns role clarity the way RACI does.
In a RACI matrix, a manager asks how many people should normally be marked Accountable for a single task to keep ownership clear. What is the recommended practice?
- Exactly one person should be Accountable for a given task
- Everyone Consulted should also be Accountable
- At least three people should share Accountable
- The Accountable role should be left blank to encourage shared ownership
Correct answer: Exactly one person should be Accountable for a given task
Best practice is that exactly one person is Accountable for a given task, which keeps ownership unambiguous. Multiple people can be Responsible for doing the work, but having more than one Accountable party blurs who answers for the outcome. Leaving it blank removes accountability entirely, which defeats the purpose of the matrix.
A project manager wants to map every work package or activity to the team members who will perform it, using a grid that links the work breakdown structure to people. What is this type of grid generically called?
- A burndown chart
- A responsibility assignment matrix
- A precedence diagram
- A control chart
Correct answer: A responsibility assignment matrix
A grid that links work to the people who will perform it is a responsibility assignment matrix, and RACI is one common form of it. It connects the work breakdown structure to specific resources so no activity lacks an owner. A precedence diagram shows sequencing, a control chart monitors process variation, and a burndown chart tracks remaining work over time.
A new team is sorting out who does what. They identify the person accountable for the business value of the product and prioritization, the person who coaches the team and removes impediments, and the people who actually build the increment. In Scrum terms, what are these three?
- Functional manager, project manager, and program manager
- Project sponsor, project manager, and steering committee
- Product owner, scrum master, and development team
- Portfolio manager, business analyst, and quality lead
Correct answer: Product owner, scrum master, and development team
In Scrum, the person accountable for product value and prioritization is the product owner, the person who coaches and removes impediments is the scrum master, and the people who build the increment are the developers (development team). These are the three accountabilities of a Scrum team. The other lists name governance or management roles, not the Scrum team roles.
A stakeholder confuses the sponsor with the project manager. Which statement correctly distinguishes their core responsibilities?
- The sponsor provides resources, funding, and high-level support, while the project manager leads the day-to-day work to meet objectives
- The project manager funds the project while the sponsor assigns tasks to the team
- The sponsor manages the daily schedule while the project manager only attends status meetings
- The two roles are interchangeable and can be filled by the same person on every project
Correct answer: The sponsor provides resources, funding, and high-level support, while the project manager leads the day-to-day work to meet objectives
The correct distinction is that the sponsor provides resources, funding, and high-level organizational support and champions the project, while the project manager leads the day-to-day execution to achieve the objectives. The sponsor enables and protects the project; the project manager runs it. Treating them as identical or swapping their duties misstates basic project roles.
A team identifies a possible threat to the schedule and records its description, probability, potential impact, an owner, and a planned response in one place. What is this central document called?
- A change log
- A risk register
- A milestone chart
- A scope statement
Correct answer: A risk register
The central document that records each risk's description, probability, impact, owner, and planned response is a risk register. It is the primary artifact for tracking identified uncertainties throughout the project. A change log tracks change requests, a milestone chart shows key dates, and a scope statement defines included work, so none of those serves as the risk repository.
A team identifies a threat that a key vendor may go out of business mid-project. They decide to redesign so the vendor is no longer needed, eliminating the threat entirely. Which risk response strategy is this?
- Avoid
- Transfer
- Accept
- Mitigate
Correct answer: Avoid
Eliminating a threat entirely by changing the plan so it can no longer occur is the avoid strategy. Transfer shifts the impact to a third party (such as insurance or a contract), mitigate reduces the probability or impact without removing it, and accept takes no proactive action. Because the redesign removes the threat completely, this is avoidance.
A team faces a positive risk (an opportunity): a new tool might let them finish early, but only if they ensure the condition occurs. They take deliberate action to make the opportunity happen. Which response strategy applies to this opportunity?
- Avoid
- Exploit
- Mitigate
- Escalate
Correct answer: Exploit
Taking deliberate action to ensure an opportunity actually happens is the exploit strategy, which is one of the responses for positive risks. Avoid and mitigate are threat responses, and while escalate can apply to either threats or opportunities, it means handing the risk to a higher level of authority rather than acting to realize the benefit. Exploit aims to lock in the upside.
A project team is overwhelmed listing every possible risk response. They want the recognized set of strategies specifically for threats (negative risks). Which set is correct?
- Plan, do, check, act
- Exploit, enhance, share, and accept
- Initiate, execute, monitor, close
- Avoid, transfer, mitigate, escalate, and accept
Correct answer: Avoid, transfer, mitigate, escalate, and accept
The recognized strategies for threats are avoid, transfer, mitigate, escalate, and accept. Exploit, enhance, share, and accept are the strategies for opportunities (positive risks). Plan-do-check-act is a continuous improvement cycle, and the last list names process groups, so neither describes threat responses.
A team wants to align with the value-focused mindset emphasized in current PMI guidance. They are reminded that a project should ultimately be judged not by its outputs but by something else. By what should a project ultimately be judged?
- The value and outcomes it delivers to stakeholders
- The size of its budget
- The volume of documentation created
- The number of deliverables produced
Correct answer: The value and outcomes it delivers to stakeholders
A project should ultimately be judged by the value and outcomes it delivers to stakeholders, not merely by its outputs. Current PMI guidance stresses that producing deliverables on time and on budget is meaningless if those deliverables do not generate real benefit. Counting deliverables, budget size, or documentation volume measures activity, not value.
A project manager focuses on serving the team by removing obstacles, providing what they need, and enabling them to do their best work, rather than commanding and controlling. Which leadership style is this, and why is it emphasized in modern project management?
- Transactional leadership; it relies solely on rewards and penalties
- Autocratic leadership; it speeds decisions by centralizing all authority
- Laissez-faire leadership; it removes the leader from any involvement
- Servant leadership; it empowers teams and is central to agile and value-driven delivery
Correct answer: Servant leadership; it empowers teams and is central to agile and value-driven delivery
Serving the team by removing obstacles and enabling their best work is servant leadership, emphasized in modern project management because it empowers self-organizing teams and underpins agile and value-driven delivery. Autocratic leadership centralizes command, laissez-faire abdicates involvement, and transactional leadership depends on rewards and penalties, none of which match the servant-leader's enabling posture.
A team adapts its processes, governance, and life cycle to fit the specific context, size, and risk of their project rather than applying a one-size-fits-all method. Which project management principle does this reflect?
- Gold plating
- Standardization
- Fast tracking
- Tailoring
Correct answer: Tailoring
Adapting processes, governance, and life cycle to fit the project's unique context is the tailoring principle. Tailoring recognizes that no single approach fits every project, so teams select methods proportional to the project's size, complexity, and risk. Standardization would force uniformity, gold plating adds unrequested extras, and fast tracking is a schedule compression technique.
An agile team gathers briefly each day so each member shares what they did, what they will do next, and any blockers. What is this short event called, and what is its main purpose?
- The sprint planning; to select work for the upcoming iteration
- The sprint retrospective; to improve the team's process for next time
- The sprint review; to demonstrate the increment to stakeholders
- The daily standup; to synchronize the team and surface impediments quickly
Correct answer: The daily standup; to synchronize the team and surface impediments quickly
The short daily event where members share progress, plans, and blockers is the daily standup (daily scrum), and its main purpose is to synchronize the team and surface impediments quickly. The retrospective improves process, the review demonstrates the increment, and planning selects upcoming work; each is a distinct Scrum event with a different goal.
A team member claims the daily standup is a status meeting for managers. The scrum master corrects this. Who is the daily standup primarily for, and how long should it typically last?
- For the customer, to review deliverables; about an hour
- For management reporting; it should run as long as needed
- For the team itself, to coordinate; it is time-boxed to about 15 minutes
- For the scrum master to assign tasks; about 30 minutes
Correct answer: For the team itself, to coordinate; it is time-boxed to about 15 minutes
The daily standup is primarily for the team itself, to coordinate their own work, and it is time-boxed to about 15 minutes. It is not a status report to management nor a task-assignment session run by the scrum master; the team self-organizes. Keeping it short and team-focused preserves its value as a quick synchronization event.
A team wants to apply systems thinking, one of the modern project management principles, when planning a change. What does systems thinking encourage them to do?
- Treat the budget as the only variable that matters
- Avoid engaging stakeholders until the plan is final
- Recognize and respond to the interactions among the project's parts and its environment
- Document each task in complete isolation from the others
Correct answer: Recognize and respond to the interactions among the project's parts and its environment
Systems thinking encourages the team to recognize and respond to the interactions among the project's parts and its surrounding environment, rather than viewing components in isolation. It promotes a holistic view in which a change in one area ripples into others. Documenting tasks in isolation, delaying stakeholder engagement, or fixating on budget alone all contradict a systems perspective.
A sponsor asks why the team keeps stakeholders engaged continuously rather than only informing them at the end. Which rationale best reflects the stakeholder principle in modern project management?
- Stakeholders should be engaged only when a problem has already occurred
- Engagement is a legal formality with no effect on outcomes
- Proactive, ongoing engagement helps satisfy stakeholders and drives project success and value
- Engagement should stop once requirements are documented
Correct answer: Proactive, ongoing engagement helps satisfy stakeholders and drives project success and value
The best rationale is that proactive, ongoing stakeholder engagement helps satisfy stakeholders and drives project success and value. Engaging stakeholders throughout, not just at the end or after problems arise, surfaces needs early, builds support, and reduces costly rework. Treating engagement as a one-time formality or a reaction to problems undermines the value the principle is meant to protect.
A team is asked to distinguish a project's outputs from its outcomes when describing success. Which statement is correct?
- Outputs and outcomes are identical terms used interchangeably
- Outputs are the deliverables produced, while outcomes are the changes or benefits those deliverables enable
- Outcomes are produced first and outputs are realized later
- Outputs are the benefits while outcomes are the deliverables
Correct answer: Outputs are the deliverables produced, while outcomes are the changes or benefits those deliverables enable
The correct distinction is that outputs are the deliverables a project produces, while outcomes are the changes or benefits those deliverables enable for the organization or users. A new app is an output; increased customer retention from using it is an outcome. Modern value-focused practice emphasizes outcomes, so confusing the two or reversing their meaning misstates how success is judged.
A new project manager wonders whether the process groups must be performed once, strictly in order, from Initiating to Closing. What is the accurate understanding?
- They are the same thing as the project life cycle phases
- They apply only to predictive projects and never to agile work
- The process groups are not strictly sequential phases; they overlap and can repeat across phases
- They must each be performed exactly once and never overlap
Correct answer: The process groups are not strictly sequential phases; they overlap and can repeat across phases
The accurate understanding is that the process groups are not rigid sequential phases; they overlap and can repeat across the phases of a project. For example, planning recurs as new information emerges. They differ from life-cycle phases, and the underlying management activities apply across predictive, agile, and hybrid work, so the other statements are incorrect.
A team is reminded of the change principle in current project management guidance. What does this principle encourage them to do about change?
- Enable and prepare those affected so change is adopted and benefits are sustained
- Implement changes without informing stakeholders to move faster
- Treat change only as a threat to be eliminated
- Resist all change to protect the original plan
Correct answer: Enable and prepare those affected so change is adopted and benefits are sustained
The change principle encourages enabling and preparing those affected so that change is adopted and its benefits are sustained. Modern guidance treats change as a normal, manageable part of delivering value rather than something to resist entirely or impose secretly. Viewing change purely as a threat to eliminate ignores that well-managed change is how projects realize improvement.
A team is asked which artifact serves as the comprehensive, integrated document that describes how the project will be executed, monitored, controlled, and closed. Which artifact is it?
- The project charter
- The project management plan
- The business case
- The stakeholder register
Correct answer: The project management plan
The comprehensive, integrated document describing how the project will be executed, monitored, controlled, and closed is the project management plan. It integrates the subsidiary plans and baselines. The charter authorizes the project at a high level, the business case justifies the investment, and the stakeholder register lists people; none of those serves as the integrated plan for running the project.
During execution, an agile team holds an event at the end of each iteration to inspect their own way of working and agree on improvements for the next iteration. What is this event called?
- The sprint review
- The daily standup
- The backlog refinement
- The retrospective
Correct answer: The retrospective
The end-of-iteration event focused on inspecting the team's own process and agreeing on improvements is the retrospective. It is about how the team works, distinct from the sprint review, which inspects the product increment with stakeholders. The daily standup is a brief synchronization, and backlog refinement clarifies and orders upcoming work, so neither matches.
A team must order the work to be done in an agile project. The prioritized, ever-evolving list of features, fixes, and requirements is owned by the product owner. What is this list called?
- The milestone schedule
- The product backlog
- The risk register
- The work breakdown structure
Correct answer: The product backlog
The prioritized, evolving list of features, fixes, and requirements owned by the product owner is the product backlog. It is the single source of work for an agile team and is continuously reordered by value. A work breakdown structure decomposes scope in plan-based work, a risk register tracks uncertainty, and a milestone schedule lists key dates, so none is the backlog.
A business analyst on a project is responsible for eliciting, analyzing, and documenting what stakeholders actually need so the right product is built. Which statement best describes the relationship between business analysis and project management here?
- Business analysis replaces project management on all projects
- Business analysis focuses on defining and managing requirements, complementing project management's focus on delivering the work
- Business analysis only happens after the product is delivered
- Business analysis is concerned solely with scheduling activities
Correct answer: Business analysis focuses on defining and managing requirements, complementing project management's focus on delivering the work
The best description is that business analysis focuses on eliciting, analyzing, and managing requirements so the right solution is built, complementing project management's focus on delivering the work effectively. The two disciplines work together rather than one replacing the other. Business analysis happens throughout, especially early, and is about needs and requirements, not primarily scheduling.
A team wants to confirm their understanding of the quality principle in modern project management. What does focusing on quality require them to build into the project?
- Quality inspected only at the very end to catch defects
- Quality built into processes and deliverables to meet stakeholders' requirements and expectations
- Quality defined entirely by the project manager's personal preference
- Quality treated as optional when the schedule is tight
Correct answer: Quality built into processes and deliverables to meet stakeholders' requirements and expectations
The quality principle requires building quality into both processes and deliverables so they meet stakeholders' requirements and expectations. Quality is planned in and maintained throughout, not merely inspected at the end, and it is defined by stakeholder requirements rather than personal taste. Sacrificing quality under schedule pressure contradicts the principle and typically increases rework and cost.
A project team is reminded that one principle calls on them to act as careful, responsible, and ethical caretakers of the resources and trust placed in them. Which principle is this?
- Tailoring
- Complexity navigation
- Stewardship
- Fast tracking
Correct answer: Stewardship
Acting as careful, responsible, and ethical caretakers of resources and trust is the stewardship principle, which emphasizes integrity, care, trustworthiness, and compliance both inside and outside the organization. Tailoring concerns adapting the approach, complexity navigation concerns dealing with intricate situations, and fast tracking is a scheduling technique, so none of those captures responsible caretaking.
A team encounters a project with many interdependent parts, ambiguity, and unpredictable behavior. Modern guidance has a principle for dealing with exactly this. Which principle addresses operating effectively amid complexity?
- Complexity (navigating complexity)
- Quality
- Stakeholder engagement
- Stewardship
Correct answer: Complexity (navigating complexity)
The principle for operating effectively amid many interdependent parts, ambiguity, and unpredictability is navigating complexity. It calls on teams to recognize sources of complexity, such as human behavior, system interactions, and uncertainty, and to respond appropriately. Stewardship, quality, and stakeholder engagement are valid principles addressing different concerns, not the management of complexity itself.
While planning, a team writes down two kinds of items: factors they believe to be true without proof, which they will validate later, and limiting factors such as a fixed deadline they cannot move. What are these two kinds of items called, respectively?
- Assumptions and constraints
- Risks and issues
- Requirements and objectives
- Deliverables and milestones
Correct answer: Assumptions and constraints
Items believed true without proof are assumptions, and limiting factors that bound the work are constraints. Assumptions carry risk because they may prove false, so they are validated over time, while constraints such as a fixed budget, deadline, or regulation restrict the team's options. Risks are uncertain future events, and deliverables, milestones, requirements, and objectives describe what is produced or sought, not these planning factors.
A company runs a permanent help desk that resolves the same types of customer tickets every day, and separately launches a six-month effort to design and roll out a brand-new self-service portal. Which of these is a project, and why?
- Neither, because both are funded from the same operating budget
- Both, because any organized work that produces value is a project
- The portal effort, because it is a temporary endeavor that creates a unique result
- The help desk, because it has a defined team and measurable output
Correct answer: The portal effort, because it is a temporary endeavor that creates a unique result
The portal effort is a project because a project is a temporary endeavor undertaken to create a unique product, service, or result. It has a defined beginning and end and produces something new. The help desk is ongoing operational work that repeats to sustain the business, so it is operations, not a project.
An executive asks a coordinator to explain how the organization's strategic transformation is structured. There is a single coordinated effort managing several related projects to obtain benefits not available from managing them individually, alongside a separate collection of all initiatives chosen to meet strategic goals. How should the coordinator describe these two structures?
- Both are programs because they manage multiple projects
- The coordinated effort is a portfolio; the broader collection is a program
- Both are portfolios because they align to strategy
- The coordinated effort is a program; the broader collection is a portfolio
Correct answer: The coordinated effort is a program; the broader collection is a portfolio
A program is a group of related projects managed in a coordinated way to obtain benefits not available from managing them individually, while a portfolio is the collection of projects, programs, and operations grouped to achieve strategic objectives. Programs focus on coordinated benefits across related work; portfolios focus on selecting and prioritizing the right investments overall.
A new team member asks what the five process groups of project management are. Which sequence correctly names them?
- Initiating, Planning, Executing, Monitoring and Controlling, Closing
- Concept, Development, Delivery, Operations, Retirement
- Defining, Designing, Building, Testing, Releasing
- Discovery, Analysis, Construction, Transition, Maintenance
Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, Closing
The five process groups are Initiating, Planning, Executing, Monitoring and Controlling, and Closing. These are logical groupings of project management activities that recur across the work, not sequential project phases. The other lists describe generic product or system stages, not PMI's process groups.
A sponsor wants the project manager to have clear authority to spend money and assign people before detailed planning begins. Which document provides that authorization and names the project manager?
- The work breakdown structure
- The risk register
- The project charter
- The stakeholder engagement plan
Correct answer: The project charter
The project charter provides the authorization. It is the document that formally authorizes the existence of the project and gives the project manager the authority to apply organizational resources to project activities. The other documents are planning artifacts created after the project is authorized; they do not confer authority.
During initiation, a project manager drafts the charter. Which set of elements is appropriate to include in it?
- Detailed task durations, the full WBS, and the cost baseline
- The complete requirements traceability matrix and acceptance test cases
- The final lessons learned and post-implementation review results
- High-level project purpose, measurable objectives, summary milestones, and the assigned project manager
Correct answer: High-level project purpose, measurable objectives, summary milestones, and the assigned project manager
A charter appropriately includes the high-level purpose or justification, measurable objectives and success criteria, summary milestones, high-level requirements and risks, and the named project manager with their authority level. Detailed durations, the WBS, the cost baseline, and the traceability matrix are produced later during planning, and lessons learned are a closing-phase output.
Stakeholders on a project keep changing their minds about what success looks like. To anchor the work, the project manager points to a single concept from the PMBOK Guide that represents the ultimate worth, importance, or usefulness the project is meant to produce. Which concept is this?
- Velocity
- Value
- Variance
- Float
Correct answer: Value
Value is the concept the project manager should anchor on. The PMBOK Guide Seventh Edition centers project management on delivering value, defined as the worth, importance, or usefulness of an outcome to stakeholders. Velocity, variance, and float are useful metrics or scheduling terms but do not capture the overall purpose of the work.
A project manager is deciding which life cycle fits a new effort. Requirements are well understood and unlikely to change, and the customer wants a fixed scope, schedule, and budget agreed up front. Which development approach best fits?
- An agile (adaptive) approach
- A purely incremental approach with no plan
- A predictive (plan-based) approach
- An extreme-programming approach
Correct answer: A predictive (plan-based) approach
A predictive (plan-based) approach best fits because the scope, schedule, and cost are defined early and change is expected to be limited. Predictive life cycles work well when requirements are stable and well understood. Agile and adaptive approaches are chosen when requirements are uncertain or expected to evolve.
A stakeholder asks the difference between predictive and agile project management in one sentence. Which statement is most accurate?
- Predictive delivers value once at the end while agile never produces a usable product
- Predictive has no documentation while agile produces extensive documentation
- Predictive plans most scope and schedule up front and embraces change rarely; agile delivers in short iterations and welcomes changing requirements
- Predictive is only for software while agile is only for construction
Correct answer: Predictive plans most scope and schedule up front and embraces change rarely; agile delivers in short iterations and welcomes changing requirements
The accurate statement is that predictive approaches plan the bulk of scope and schedule up front and treat change as the exception, while agile delivers value in short iterations and welcomes changing requirements even late in development. Both can apply across industries, both involve documentation appropriate to context, and both ultimately deliver usable outcomes.
A new analyst asks what a project life cycle actually is. Which description is correct?
- The legal contract governing the project's deliverables
- The calculation of earned value over the project's duration
- The list of all stakeholders who influence the project
- The series of phases a project passes through from start to completion
Correct answer: The series of phases a project passes through from start to completion
A project life cycle is the series of phases that a project passes through from its initiation to its closure. It provides the basic framework for managing the project regardless of the specific work involved. The other options describe a stakeholder register, an earned value calculation, and a contract, none of which define the life cycle.
A team is mapping the phases its project will move through. Which sequence represents a typical generic project life cycle?
- Starting the project, organizing and preparing, carrying out the work, and ending the project
- Budgeting, auditing, reporting, and archiving
- Marketing, sales, fulfillment, and support
- Hiring, training, evaluating, and promoting
Correct answer: Starting the project, organizing and preparing, carrying out the work, and ending the project
A typical generic project life cycle moves through starting the project, organizing and preparing, carrying out the work, and ending (closing) the project. These high-level phases describe the flow of any project. The other sequences describe business functions or HR processes, not project phases.
A project manager wants every team member to understand who is accountable for each deliverable versus who merely needs to stay informed. Which tool best clarifies these roles?
- A burndown chart
- A Gantt chart
- A control chart
- A RACI matrix
Correct answer: A RACI matrix
A RACI matrix best clarifies these roles. It is a responsibility assignment matrix that maps people to deliverables across four roles, making accountability and involvement explicit. A Gantt chart shows schedule, a burndown chart shows remaining agile work, and a control chart shows process variation, none of which assign roles.
On a RACI matrix, a team debates how many people should hold the 'A' for a single deliverable. What does the 'A' stand for, and what is the rule?
- Accountable, and exactly one person should be accountable for each deliverable
- Assisting, and several people may assist
- Advising, and the advisor count is unlimited
- Approving, and any manager may approve
Correct answer: Accountable, and exactly one person should be accountable for each deliverable
The 'A' stands for Accountable, and the rule is that exactly one person should be accountable for each deliverable to avoid confusion over ownership. Responsible (R) parties do the work, Consulted (C) parties provide input, and Informed (I) parties are kept up to date. Multiple R, C, and I assignments are fine, but accountability should rest with a single person.
A coordinator is asked what a responsibility assignment matrix (RAM) is used for. Which answer is correct?
- To sequence activities along the critical path
- To calculate the project's net present value
- To link project work or deliverables to the people or groups responsible for them
- To record identified risks and their owners
Correct answer: To link project work or deliverables to the people or groups responsible for them
A responsibility assignment matrix links project work packages or deliverables to the resources responsible for completing them, ensuring each piece of work has clear ownership. A RACI chart is one common form of RAM. The other options describe financial analysis, scheduling, and the risk register, respectively.
A junior team member asks who a stakeholder is on the project. Which definition is most complete?
- Only the executives who approve the budget
- Only the members of the core delivery team
- Only the customer who pays for the project
- Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by the project
Correct answer: Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by the project
A stakeholder is any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project. This deliberately broad definition includes customers, sponsors, team members, regulators, end users, and others. Limiting it to only the customer, team, or executives misses key parties.
A project manager is clarifying two related stakeholder artifacts. One lists the identified stakeholders and information about them; the other documents the strategies and approaches to involve them productively. Which pairing is correct?
- The stakeholder register lists stakeholders; the stakeholder engagement plan documents strategies to involve them
- The stakeholder engagement plan lists stakeholders; the stakeholder register documents strategies
- Both documents list stakeholders with no difference
- The stakeholder register documents strategies; the engagement plan lists stakeholders
Correct answer: The stakeholder register lists stakeholders; the stakeholder engagement plan documents strategies to involve them
The stakeholder register lists the identified stakeholders along with information such as their roles, interests, and influence, while the stakeholder engagement plan documents the strategies and actions needed to engage them effectively. The register is an inventory; the engagement plan is the action plan built from that inventory.
A traditional view describes three competing constraints that a project manager must balance, where changing one usually affects the others. Which set names this 'triple constraint'?
- Stakeholders, resources, and communications
- People, process, and technology
- Scope, schedule (time), and cost
- Quality, risk, and procurement
Correct answer: Scope, schedule (time), and cost
The triple constraint is scope, schedule (time), and cost. These three are interdependent, so a change to one typically forces a trade-off in the others, for example expanding scope usually increases time or cost. Quality is often shown as influenced by the balance among the three but is not itself part of the classic triple constraint.
A sponsor asks the project manager to define 'scope' on the project. Which answer is correct?
- The order in which activities will be performed
- The total amount of money authorized for the project
- The work required, and only that work, to deliver the product, service, or result with its features and functions
- The list of risks that could affect delivery
Correct answer: The work required, and only that work, to deliver the product, service, or result with its features and functions
Scope is the work required, and only that work, to deliver a product, service, or result with the specified features and functions. It defines what is and is not included in the project. The other options describe the budget, the risk register, and the schedule sequence, none of which define scope.
A stakeholder asks what counts as a project deliverable. Which is the best example of a deliverable?
- A unique, verifiable product, result, or capability produced to complete a process or project, such as a tested user manual
- The project manager's authority to assign resources
- The risk appetite of the sponsoring organization
- A weekly status meeting held by the team
Correct answer: A unique, verifiable product, result, or capability produced to complete a process or project, such as a tested user manual
A deliverable is any unique and verifiable product, result, or capability that must be produced to complete a process, phase, or project, such as a completed and tested user manual. A status meeting is an activity, not a deliverable; authority and risk appetite are governance attributes, not produced outputs.
A team lead wants to mark significant points in the schedule that have no duration, such as 'design approved' or 'go-live.' What are these called?
- Work packages
- Milestones
- Lags
- Buffers
Correct answer: Milestones
These are milestones, which are significant points or events in a project that mark progress and have zero duration. They are used to signal completion of major phases or approvals. Work packages are units of work with duration, lags are imposed delays between activities, and buffers are reserves of time.
At the end of a phase, a project manager records what went well, what did not, and recommendations for the future. Where should this knowledge be captured so it can benefit current and future work?
- The project charter
- The triple constraint
- The lessons learned register
- The milestone list
Correct answer: The lessons learned register
This knowledge belongs in the lessons learned register, which is a living document that captures insights gained during the project so they can be applied to current work and future projects. The charter authorizes the project, the triple constraint is a set of competing limits, and the milestone list marks schedule events, none of which capture lessons.
A program is staffing up. The role described holds overall accountability for leading the team and meeting project objectives, while a different role provides funding and champions the project at the executive level. Which pairing matches these descriptions?
- Team member leads to objectives; project manager provides funding
- Sponsor leads to objectives; team member provides executive support
- Sponsor leads to objectives; project manager provides funding
- Project manager leads to objectives; sponsor provides funding and executive support
Correct answer: Project manager leads to objectives; sponsor provides funding and executive support
The project manager is the person assigned to lead the team and is accountable for achieving the project objectives, while the sponsor is the person or group that provides resources and support and champions the project at the executive level. Confusing these roles misassigns who funds versus who delivers.
A team is unsure who owns scope decisions on an agile product effort. Which description of common roles and responsibilities is correct?
- The product owner prioritizes value and owns the backlog; the development team decides how to build the increment
- The development team prioritizes business value and the product owner writes all the code
- The Scrum Master sets the budget and signs contracts
- The sponsor manages the daily task board
Correct answer: The product owner prioritizes value and owns the backlog; the development team decides how to build the increment
On an agile effort the product owner is responsible for maximizing value and owning and ordering the product backlog, while the development team decides how to design and build the increment. The Scrum Master facilitates and removes impediments rather than controlling budget, and the sponsor does not manage the daily board.
A PMBOK Guide Seventh Edition principle states that project teams should continuously evaluate and adjust how they work to match the project's unique context rather than forcing a one-size-fits-all method. Which principle is this?
- Tailoring based on context
- Centralize all decisions
- Eliminate all uncertainty
- Maximize earned value
Correct answer: Tailoring based on context
This is the tailoring principle. The PMBOK Guide Seventh Edition advises teams to design the project's development approach, processes, and governance to fit the specific context, objectives, stakeholders, and complexity. The other options are not principles; eliminating all uncertainty and centralizing all decisions actually contradict adaptive, servant-leadership guidance.
A new project manager is overwhelmed by competing methods. The PMBOK Guide Seventh Edition replaced the older knowledge-area structure with a set of broad areas of focus that describe outcomes teams must manage, such as stakeholders, planning, and delivery. What are these called?
- Project performance domains
- Process groups
- ITTO tables
- Knowledge areas
Correct answer: Project performance domains
These are the project performance domains. The PMBOK Guide Seventh Edition organizes effective project delivery around eight interrelated performance domains, including Stakeholders, Team, Development Approach and Life Cycle, Planning, Project Work, Delivery, Measurement, and Uncertainty. Process groups and knowledge areas were emphasized in earlier editions, and ITTO tables are not a structural framework.
A manager describes a leadership style where the leader's primary aim is to serve the team by removing impediments, providing what the team needs, and enabling them to do their best work. Which style is being described?
- Transactional micromanagement
- Servant leadership
- Laissez-faire neglect
- Command-and-control leadership
Correct answer: Servant leadership
This describes servant leadership, in which the leader focuses on serving the team's needs, removing obstacles, and creating an environment where the team can succeed. It is emphasized in agile and in PMBOK Guide Seventh Edition guidance on leadership. Command-and-control and micromanagement centralize authority, and laissez-faire neglect provides no support.
A project blends a predictive plan for the regulated, well-defined infrastructure work with agile iterations for the evolving customer-facing features. What is this combination called?
- A hybrid project management approach
- A portfolio
- A waterfall approach
- A purely predictive approach
Correct answer: A hybrid project management approach
This is a hybrid approach, which deliberately combines elements of predictive and agile (adaptive) methods within one project to suit different components of the work. Using a plan-based method for stable, regulated work and iterations for evolving features is a textbook hybrid. It is neither purely predictive nor classic waterfall, and a portfolio is a collection of investments.
A team holds a brief, time-boxed meeting each morning where members share what they did, what they will do, and any blockers. What is this event, and what is its main purpose?
- A sprint review, used to demonstrate the product to customers
- A steering committee, used to approve the budget
- A retrospective, used to improve the team's process
- A daily standup, used to synchronize the team and surface impediments
Correct answer: A daily standup, used to synchronize the team and surface impediments
This is a daily standup (daily scrum), a short time-boxed meeting where the team synchronizes its plan for the day and raises impediments so they can be addressed quickly. A sprint review demonstrates the increment to stakeholders, a retrospective focuses on process improvement, and a steering committee handles governance, not daily coordination.
A project manager wants a single place to record identified risks along with their causes, potential impacts, owners, and planned responses. Which document serves this purpose?
- The RACI matrix
- The risk register
- The milestone schedule
- The project charter
Correct answer: The risk register
The risk register serves this purpose. It is a repository that records identified risks together with their descriptions, causes, potential impacts, assigned owners, and planned responses, and it is updated throughout the project. The charter authorizes the project, the milestone schedule tracks key dates, and the RACI matrix assigns roles.
A threat has been identified that would seriously delay a key deliverable. The team decides to change the plan so the threat can no longer occur at all. Which risk response strategy is this?
- Accept
- Transfer
- Exploit
- Avoid
Correct answer: Avoid
Eliminating the threat entirely by changing the plan so it can no longer occur is the avoid strategy. Accept means taking no proactive action and dealing with the risk if it happens, transfer shifts the impact to a third party, and exploit is an opportunity (positive risk) strategy, not a threat response.
A team identifies a positive risk: a new vendor tool could finish a workstream early and free up budget. They want to take action to make sure the opportunity is realized. Which response strategy fits an opportunity they want to ensure happens?
- Avoid
- Mitigate
- Transfer
- Exploit
Correct answer: Exploit
To make sure an opportunity is realized, the exploit strategy fits, because it takes action to ensure the positive risk occurs. Avoid and mitigate are threat strategies (eliminating or reducing a negative risk), and transfer shifts a threat's impact to a third party. Opportunity strategies include exploit, enhance, share, and accept.
A stakeholder asks the project manager to summarize the basic categories of strategies for responding to threats (negative risks). Which list is correct?
- Plan, do, check, act, and standardize
- Escalate, avoid, transfer, mitigate, and accept
- Initiate, plan, execute, monitor, and close
- Responsible, accountable, consulted, and informed
Correct answer: Escalate, avoid, transfer, mitigate, and accept
The strategies for responding to threats are escalate, avoid, transfer, mitigate, and accept. Escalate moves the risk to a higher authority, avoid eliminates it, transfer shifts its impact, mitigate reduces its probability or impact, and accept acknowledges it. The other lists are process groups, a continuous-improvement cycle, and RACI roles.
During execution a critical resource is suddenly unavailable, threatening the schedule. According to value-driven guidance, what should the project team do first?
- Assess the impact and engage the right stakeholders to decide on a response
- Wait for the next scheduled status report before acting
- Hide the issue until it resolves on its own
- Immediately cancel the project
Correct answer: Assess the impact and engage the right stakeholders to decide on a response
The team should assess the impact and engage the appropriate stakeholders to decide on a response. Proactive issue management and stakeholder engagement are core to delivering value and keeping the project on track. Waiting passively, cancelling immediately, or hiding the problem all increase risk and erode stakeholder trust.
A PMBOK Guide Seventh Edition principle states that project teams should recognize, evaluate, and respond to the interactions within and around the project, treating the project as part of a larger whole. Which principle is this?
- Gold plating
- Systems thinking
- Single-point accountability
- Sunk cost focus
Correct answer: Systems thinking
This is the systems thinking principle, which calls for recognizing and responding to the project's interactions with its environment and viewing the project holistically rather than in isolation. Sunk cost focus and gold plating are pitfalls to avoid, and single-point accountability is a RACI concept, not a PMBOK principle.
A project sponsor wants to know how the project's success will ultimately be judged in the PMBOK Guide Seventh Edition mindset. Which statement best reflects current thinking?
- Success is measured by the value and intended outcomes delivered to stakeholders, not merely outputs
- Success is measured solely by staying under budget
- Success is measured only by delivering on the original schedule
- Success is measured by the number of documents produced
Correct answer: Success is measured by the value and intended outcomes delivered to stakeholders, not merely outputs
Current thinking judges success by the value and intended outcomes delivered to stakeholders, not merely by producing outputs or hitting one constraint. The PMBOK Guide Seventh Edition emphasizes outcomes and benefits realization over a narrow focus on schedule, budget, or document count alone.
A team is choosing how to deliver a product whose requirements are highly uncertain and likely to change as users give feedback. Which delivery cadence and life cycle best support this situation?
- A single delivery at the very end of a long predictive plan
- No planning, building features in random order
- A fixed scope locked before any feedback is gathered
- Iterative and incremental delivery in short cycles with frequent feedback
Correct answer: Iterative and incremental delivery in short cycles with frequent feedback
Iterative and incremental delivery in short cycles with frequent feedback best supports high uncertainty, because it lets the team inspect, adapt, and refine requirements as users respond. A single end delivery or a scope locked before any feedback removes the chance to learn and adjust, which is exactly what an adaptive context needs.
A project manager notices the team keeps adding small unrequested features that were not approved, expanding the work without adjusting schedule or budget. What is this phenomenon, and what is the appropriate control?
- Fast tracking, controlled by adding resources
- Progressive elaboration, controlled by ignoring it
- Scope creep, controlled through an integrated change control process
- Resource leveling, controlled by extending the schedule
Correct answer: Scope creep, controlled through an integrated change control process
This is scope creep, the uncontrolled expansion of scope without corresponding adjustments to time, cost, and resources, and it is controlled through a defined change control process so changes are evaluated and approved before being implemented. Fast tracking and resource leveling are scheduling techniques, and progressive elaboration is the legitimate refinement of detail over time.
A team wants to confirm a feature is finished consistently. They agree on a shared checklist of conditions every backlog item must meet before it is considered complete. What is this agreement called?
- The project charter
- The product roadmap
- The definition of done
- The risk register
Correct answer: The definition of done
This is the definition of done, a shared, agreed set of conditions a work item must satisfy to be considered complete, which promotes consistent quality. A product roadmap shows the planned direction over time, the risk register tracks risks, and the charter authorizes the project, none of which define completion criteria for work items.
A stakeholder challenges a project decision by citing the large amount already spent, arguing the project must continue to justify that spending. What concept should the project manager apply to evaluate whether to continue?
- The more money already spent, the more justified continuing becomes
- Continuing is always cheaper than stopping
- Future expected value should drive the decision; already-spent costs are sunk and should not by themselves justify continuing
- The decision should be based only on the original charter
Correct answer: Future expected value should drive the decision; already-spent costs are sunk and should not by themselves justify continuing
The decision should be based on future expected value, because money already spent is a sunk cost that cannot be recovered and should not by itself justify continuing. Treating past spending as a reason to continue is the sunk cost fallacy. The right comparison is the expected future benefits versus future costs of continuing.
A project manager wants the team to operate with honesty, transparency, and care for the organization's resources and the broader environment. Which PMBOK Guide Seventh Edition principle captures this responsible, ethical stewardship?
- Be a diligent, respectful, and caring steward
- Optimize only for the project manager's interests
- Avoid all documentation
- Maximize utilization at any cost
Correct answer: Be a diligent, respectful, and caring steward
This is the stewardship principle, which calls on practitioners to be diligent, respectful, and caring stewards who act with integrity, care, and trustworthiness toward stakeholders, the organization, and society. Maximizing utilization at any cost or optimizing only for self-interest contradicts stewardship.
A project manager is building a team and wants to follow PMBOK Guide Seventh Edition guidance on people. Which principle directly addresses fostering a collaborative, accountable, high-performing project environment?
- Eliminate all stakeholder communication
- Lock the scope and ignore feedback
- Centralize every decision with the sponsor
- Create a collaborative project team environment
Correct answer: Create a collaborative project team environment
The principle is to create a collaborative project team environment, which emphasizes shared accountability, agreements, and a culture that lets the team perform at its best. Eliminating communication, ignoring feedback, or centralizing every decision all undermine collaboration and contradict the team and stakeholder principles.
Two stakeholders strongly disagree about a requirement, and the conflict is stalling progress. According to engagement-focused guidance, what is the best first step for the project manager?
- Engage both stakeholders to understand their needs and seek a value-driven resolution
- Pick one stakeholder's view at random to save time
- Escalate immediately to the CEO before gathering facts
- Remove both stakeholders from the project
Correct answer: Engage both stakeholders to understand their needs and seek a value-driven resolution
The best first step is to engage both stakeholders to understand their underlying needs and work toward a resolution that supports project value. Effective stakeholder engagement is a core principle and performance domain. Choosing at random, escalating prematurely, or removing stakeholders bypasses the engagement that resolves the root disagreement.
A new project manager learns the PMBOK Guide Seventh Edition expects teams to embed quality into processes and deliverables rather than relying only on inspection at the end. Which principle does this reflect?
- Inspect only after delivery to the customer
- Build quality into processes and deliverables
- Measure quality only in financial terms
- Treat quality as optional when behind schedule
Correct answer: Build quality into processes and deliverables
This reflects the quality principle, which calls for building quality into processes and deliverables so defects are prevented rather than caught only by late inspection. Relying solely on end inspection, dropping quality when behind schedule, or measuring quality only financially all run counter to the principle.
A project manager describes that the project's plans, processes, and effort were intentionally scaled to match a small, low-complexity, low-risk effort. Which two PMBOK Guide Seventh Edition concepts are most directly demonstrated?
- Tailoring and navigating complexity
- Earned value and critical path
- Procurement and contract types
- ITTO mapping and process groups
Correct answer: Tailoring and navigating complexity
Scaling plans and processes to fit a small, low-complexity, low-risk effort most directly demonstrates tailoring and navigating complexity. Tailoring adapts the approach to context, and recognizing low complexity informs how much rigor is appropriate. Earned value, critical path, procurement, and ITTO mapping are techniques, not the principles being demonstrated here.
A stakeholder asks why the team produces a working, usable increment of the product each iteration instead of waiting until the end. Which benefit is the strongest justification?
- It eliminates all project risk
- It enables early and frequent value delivery and faster feedback to guide future work
- It guarantees the project will finish under budget
- It removes the need for any planning
Correct answer: It enables early and frequent value delivery and faster feedback to guide future work
The strongest justification is that delivering a usable increment each iteration enables early and frequent value delivery and provides faster feedback that guides subsequent work. It does not guarantee budget outcomes, remove planning, or eliminate risk; rather, it reduces uncertainty by validating value sooner.
A team using an adaptive approach maintains an ordered list of features, enhancements, and fixes that represents everything currently known to be potentially needed for the product. The most valuable items sit at the top. What is this artifact?
- The product backlog
- The change log
- The lessons learned register
- The cost baseline
Correct answer: The product backlog
This is the product backlog, an ordered list of everything currently known to be potentially needed in the product, with the highest-value items prioritized at the top for the team to pull from. The cost baseline tracks budget, the lessons learned register captures insights, and the change log records change requests, none of which serve as the prioritized work list.
A leadership team manages a coordinated group of related projects to deliver shared infrastructure that no single project could produce alone, while a separate executive group selects which of these efforts to fund based on strategic fit and available budget. Which terms correctly describe these two groupings, in that order?
- A deliverable and a baseline
- A portfolio and a program
- A phase and a milestone
- A program and a portfolio
Correct answer: A program and a portfolio
The coordinated group of related projects managed together for benefits not available from managing them individually is a program, and the executive grouping that selects and prioritizes efforts to meet strategic objectives is a portfolio. The difference between a project, program, and portfolio is one of scope and intent: a project produces a unique product, service, or result; a program coordinates related projects for combined benefit; a portfolio groups projects, programs, and operations to achieve strategic goals. Calling the selecting group a program reverses the relationship, since portfolios sit above programs in alignment with organizational strategy.
A new team member asks how a project differs from the organization's ongoing help-desk operations. Which statement best captures what makes work a project?
- A project is temporary and creates a unique product, service, or result, with a definite beginning and end
- A project is any work that repeats on a fixed schedule to sustain the business
- A project is work performed only by full-time employees rather than contractors
- A project is any task that costs more than a set budget threshold
Correct answer: A project is temporary and creates a unique product, service, or result, with a definite beginning and end
A project is a temporary endeavor undertaken to create a unique product, service, or result, with a defined start and finish. Temporary means it has a clear end once objectives are met (or it is terminated), and unique means the outcome differs from routine output. Ongoing help-desk operations are repetitive and sustaining, which is exactly why they are operations rather than a project. Cost thresholds or staffing type do not define whether work is a project.
A predictive project plan groups activities into the five recognized process groups. Which list correctly names all five?
- Sprint Planning, Daily Scrum, Sprint Review, Retrospective, and Backlog
- Defining, Designing, Building, Testing, and Releasing
- Scope, Schedule, Cost, Quality, and Risk
- Initiating, Planning, Executing, Monitoring and Controlling, and Closing
Correct answer: Initiating, Planning, Executing, Monitoring and Controlling, and Closing
The five process groups in project management are Initiating, Planning, Executing, Monitoring and Controlling, and Closing. These groups organize project work logically and are not the same as project phases, which are time-based stages of the work. The agile-ceremony list and the design-build sequence describe other concepts entirely, and scope/schedule/cost/quality/risk are knowledge areas or constraints, not process groups.
A team is selecting a delivery approach. Requirements are stable and well understood, regulatory documentation must be approved before construction begins, and changes late in the project are costly. Which approach is the best fit, and why?
- An adaptive (agile) approach, because requirements will emerge through frequent iterations
- An adaptive (agile) approach, because the customer is unavailable for feedback
- A predictive (plan-based) approach, because scope is defined up front and change is controlled
- A predictive approach, because the team has never worked together before
Correct answer: A predictive (plan-based) approach, because scope is defined up front and change is controlled
A predictive, plan-based approach fits because the scope is stable and well understood, work can be planned in detail up front, and formal change control protects the approved baseline. The core difference between predictive and agile project management is how much is known early: predictive plans the full scope before execution, while agile lets requirements emerge through iterations and frequent feedback. Choosing agile here is wrong precisely because the requirements are not expected to change.
A project manager wants to use the structured sequence of phases that the project passes through from start to completion to organize and govern the work. What is this overall sequence called?
- The triple constraint
- The project life cycle
- The risk register
- The stakeholder register
Correct answer: The project life cycle
The project life cycle is the series of phases a project passes through from initiation to closure, providing a framework for managing and governing the work regardless of delivery approach. A project life cycle may be predictive, adaptive, or hybrid, and its phases (such as starting, organizing, carrying out, and closing the work) give structure to delivery. A risk register, the triple constraint, and a stakeholder register are project tools or constraints, not the overarching sequence of phases.
During planning, a project team marks several zero-duration schedule points that represent significant events, such as the completion of the design phase and the signing of final acceptance. What are these schedule points called?
- Constraints
- Deliverables
- Work packages
- Milestones
Correct answer: Milestones
These are milestones: significant points or events in a project, such as a phase completion or major approval, typically shown with zero duration because they mark a moment rather than work. Project milestones help track progress and communicate key dates to stakeholders. A deliverable is a tangible or intangible output produced, a constraint is a limiting factor, and a work package is the lowest-level component of decomposed scope, none of which are zero-duration schedule events.
A project must deliver a fixed regulatory report by a hard deadline using predictive planning, but the user-facing dashboard tied to it benefits from frequent iteration and feedback, so the team plans the report predictively and builds the dashboard in iterations. What is this combined approach called?
- A portfolio approach
- A hybrid approach
- A purely agile approach
- A purely predictive approach
Correct answer: A hybrid approach
This is a hybrid approach, which blends predictive and adaptive (agile) elements within the same project to fit the nature of each portion of the work. Hybrid lets a team use plan-based methods where scope is stable and iterative methods where requirements emerge, and selecting the right blend is an act of tailoring to context. Labeling it purely predictive or purely agile ignores that both styles are deliberately used together; a portfolio is a grouping of work, not a delivery approach.
After completing a major phase, the team documents what went well, what went poorly, and recommended improvements so future phases and projects can benefit. In which project artifact is this knowledge captured?
- The stakeholder register
- The lessons learned register
- The project charter
- The risk register
Correct answer: The lessons learned register
This knowledge is captured in the lessons learned register, a document used throughout the project to record knowledge gained so it can be applied to current and future work. Recording lessons continuously (not only at closure) supports the principle of building on experience and improving over time. The stakeholder register lists stakeholders, the risk register tracks risks, and the charter authorizes the project, so none of these store lessons learned.
A team identifies a threat that a key vendor may deliver late, and decides to qualify a second vendor in advance so the impact is lessened if the threat occurs. Which risk response strategy does this represent?
- Escalate
- Accept
- Exploit
- Mitigate
Correct answer: Mitigate
Qualifying a backup vendor to reduce the probability or impact of a late delivery is a mitigate strategy, one of the standard responses to a negative risk (threat). A risk response strategy is the planned approach for handling an identified risk; for threats the common options are avoid, transfer, mitigate, escalate, and accept. Accepting would mean taking no proactive action, escalating moves the risk to a higher authority, and exploit applies to positive risks (opportunities), not threats.
A project manager is reporting on a predictive construction project. The budgeted cost of the work that should have been finished by today is 80,000 dollars, the budgeted value of the work actually completed is 70,000 dollars, and the team has spent 75,000 dollars so far. Which figures correspond to planned value, earned value, and actual cost?
- Planned value is 75,000, earned value is 70,000, and actual cost is 80,000
- Planned value is 70,000, earned value is 80,000, and actual cost is 75,000
- Planned value is 80,000, earned value is 70,000, and actual cost is 75,000
- Planned value is 70,000, earned value is 75,000, and actual cost is 80,000
Correct answer: Planned value is 80,000, earned value is 70,000, and actual cost is 75,000
Planned value is 80,000, earned value is 70,000, and actual cost is 75,000. Planned value (PV) is the authorized budget for the work scheduled to be done by a point in time; earned value (EV) is the budgeted value of the work actually completed; and actual cost (AC) is the money actually spent for that completed work. Mapping the dollar figures to the right term is the foundation of every earned value calculation in a predictive project.
On a plan-based project, the earned value is 70,000 dollars and the actual cost to date is 75,000 dollars. What is the cost variance, and what does it tell the project team?
- Cost variance is 5,000, indicating the project is under budget
- Cost variance is -5,000, indicating the project is over budget
- Cost variance is 0.93, indicating the project is over budget
- Cost variance is -5,000, indicating the project is behind schedule
Correct answer: Cost variance is -5,000, indicating the project is over budget
Cost variance is -5,000, indicating the project is over budget. Cost variance is calculated as earned value minus actual cost (70,000 - 75,000 = -5,000); a negative result means the project has spent more than the value of the work delivered, so it is over budget. A positive cost variance would mean under budget, and 0.93 would be the cost performance index ratio, not the variance.
A project manager wants to know whether a predictive project is ahead of or behind schedule. The earned value is 70,000 dollars and the planned value is 80,000 dollars. What is the schedule variance and its meaning?
- Schedule variance is 10,000, meaning the project is ahead of schedule
- Schedule variance is -10,000, meaning the project is behind schedule
- Schedule variance is -10,000, meaning the project is over budget
- Schedule variance is 0.88, meaning the project is behind schedule
Correct answer: Schedule variance is -10,000, meaning the project is behind schedule
Schedule variance is -10,000, meaning the project is behind schedule. Schedule variance is earned value minus planned value (70,000 - 80,000 = -10,000); a negative value shows that less work has been completed than was scheduled, so the project is behind schedule. Schedule variance addresses time, not cost, and a ratio like 0.88 would be the schedule performance index rather than the variance.
A predictive project reports an earned value of 90,000 dollars and an actual cost of 100,000 dollars. The project team should calculate the cost performance index to assess cost efficiency. What is the cost performance index and how should it be interpreted?
- -10,000, meaning the project is over budget
- 0.90, meaning the team is getting 90 cents of value for every dollar spent
- 0.90, meaning the project is behind schedule
- 1.11, meaning the team is getting 1.11 dollars of value for every dollar spent
Correct answer: 0.90, meaning the team is getting 90 cents of value for every dollar spent
The cost performance index is 0.90, meaning the team is getting 90 cents of value for every dollar spent. Cost performance index equals earned value divided by actual cost (90,000 / 100,000 = 0.90); a value below 1.0 signals the project is spending more than the value being earned, which is poor cost efficiency. The figure -10,000 would be the cost variance, and cost performance index measures cost, not schedule.
A project manager computes a schedule performance index of 1.05 for a plan-based project. What does this value indicate about the project's progress?
- The project is ahead of schedule, completing more work than was planned for this point
- The project has consumed 105 percent of its total budget
- The project is over budget by 5 percent
- The project is behind schedule by 5 percent
Correct answer: The project is ahead of schedule, completing more work than was planned for this point
The project is ahead of schedule, completing more work than was planned for this point. Schedule performance index is earned value divided by planned value, so a value above 1.0 means the team has earned more value than was scheduled and is therefore ahead of schedule. A schedule performance index speaks to time efficiency only; budget status is measured by the cost performance index or cost variance.
During monitoring of a predictive project, the team needs an integrated method that combines scope, schedule, and cost data into a single set of measures to objectively assess project performance and forecast outcomes. Which technique does this describe?
- Critical chain method
- Resource leveling
- Rolling wave planning
- Earned value management
Correct answer: Earned value management
Earned value management is the technique that integrates scope, schedule, and cost into a unified set of measures. By comparing planned value, earned value, and actual cost, earned value management gives objective indicators such as cost variance, schedule variance, and the performance indexes, and supports forecasting like estimate at completion. Resource leveling and critical chain address resource and schedule constraints, not integrated performance measurement.
A project team is decomposing a predictive project's total scope. They break major deliverables down until they reach components that can be reliably estimated and assigned to a single owner. What is the lowest-level component of a work breakdown structure called?
- Milestone
- Work package
- Activity
- Control account
Correct answer: Work package
The lowest-level component of a work breakdown structure is the work package. A work package is the point where cost and duration can be reliably estimated and the work can be scheduled, executed, monitored, and controlled. A control account sits above work packages for management integration, an activity is a further breakdown used for scheduling, and a milestone is a zero-duration point, not a deliverable component.
A project manager is preparing to create a work breakdown structure for a new plan-based project. Which approach correctly describes how a work breakdown structure is built?
- List every project activity in chronological order along a timeline with start and finish dates
- Assign each team member a role of responsible, accountable, consulted, or informed for each task
- Decompose the project's deliverables and scope hierarchically into progressively smaller, more manageable components down to the work package level
- Rank all project risks by probability and impact in a prioritized register
Correct answer: Decompose the project's deliverables and scope hierarchically into progressively smaller, more manageable components down to the work package level
A work breakdown structure is created by decomposing the project's deliverables and scope hierarchically into progressively smaller, more manageable components down to the work package level. It is deliverable-oriented, organizing the total scope so that nothing is omitted; the 100 percent rule means the WBS captures all of the work. Listing activities on a timeline describes a Gantt chart or schedule, ranking risks describes a risk register, and the responsible-accountable-consulted-informed scheme describes a RACI chart.
A scheduling analyst determines that a particular activity can be delayed by three days without delaying the project's finish date, but delaying it by more than one day would push the early start of the next activity. What are the total float and free float for this activity, respectively?
- Total float is one day and free float is three days
- Total float and free float are both one day
- Total float is three days and free float is one day
- Total float and free float are both three days
Correct answer: Total float is three days and free float is one day
Total float is three days and free float is one day. Total float is the amount of time an activity can slip without delaying the project's finish date, while free float is the amount it can slip without delaying the early start of any successor activity. Because the activity can move three days without affecting project completion but only one day before affecting the next task, those values map directly to total and free float.
On a predictive project schedule, an activity has a total float of zero. What does this tell the project team about the activity?
- The activity can be delayed indefinitely without affecting the project
- The activity is on the critical path and any delay will delay the project finish date
- The activity has the most resources assigned to it
- The activity has been completed ahead of schedule
Correct answer: The activity is on the critical path and any delay will delay the project finish date
The activity is on the critical path and any delay will delay the project finish date. Float (also called slack) is the amount of time an activity can be delayed without delaying a successor or the project; an activity with zero total float has no scheduling flexibility, which defines a critical path activity. Float is unrelated to how many resources are assigned or whether work finished early.
A project manager needs to determine the minimum time required to complete a predictive project and identify which activities cannot be delayed. Which technique should the project team apply, and what does it identify?
- Parametric estimating, which uses unit rates and historical data to estimate duration
- The critical path method, which identifies the longest sequence of dependent activities and the shortest possible project duration
- The Delphi technique, which gathers anonymous expert estimates
- Resource smoothing, which adjusts activities so resource use stays within set limits
Correct answer: The critical path method, which identifies the longest sequence of dependent activities and the shortest possible project duration
The critical path method identifies the longest sequence of dependent activities and the shortest possible project duration. By performing a forward and backward pass through the schedule network, the team finds the path with zero float; this longest path determines the earliest the project can finish, and its activities cannot slip without delaying the project. Resource smoothing, the Delphi technique, and parametric estimating address resource use, expert input, and estimation, not critical path identification.
A predictive project network has two paths from start to finish: Path A takes 14 days and Path B takes 18 days. What is the critical path and the project's expected duration?
- The critical path is the shorter of the two paths at 14 days
- Path B is the critical path and the project duration is 18 days
- The project duration is 32 days, the sum of both paths
- Path A is the critical path and the project duration is 14 days
Correct answer: Path B is the critical path and the project duration is 18 days
Path B is the critical path and the project duration is 18 days. The critical path is the longest path through the schedule network, because every path must finish for the project to complete; the longest one therefore drives the minimum total duration. The shorter Path A has float, and durations of parallel paths are not added together.
A predictive project's plan calls for displaying scheduled activities as horizontal bars along a calendar timeline so stakeholders can see start dates, finish dates, durations, and overlaps at a glance. Which scheduling artifact is being described?
- A responsibility assignment matrix
- A work breakdown structure
- A control chart
- A Gantt chart
Correct answer: A Gantt chart
A Gantt chart is the artifact described. A Gantt chart, also called a bar chart, plots schedule activities as horizontal bars against a time axis, making start and finish dates, durations, and overlaps easy to read and communicate. A work breakdown structure organizes scope hierarchically rather than against time, a responsibility assignment matrix maps roles to work, and a control chart monitors process quality.
After the project management plan is approved, a project manager refers to the approved scope, schedule, and cost plans as the reference point for measuring project performance. What is this combined approved reference called?
- The project baseline
- The lessons learned register
- The project charter
- The project backlog
Correct answer: The project baseline
The combined approved reference is the project baseline. The performance measurement baseline integrates the approved scope baseline, schedule baseline, and cost baseline, and serves as the benchmark against which actual results are compared, including in earned value analysis. The charter authorizes the project, the backlog is an agile artifact, and the lessons learned register captures knowledge, none of which serve as the performance reference.
A stakeholder on a predictive project submits a request to add a new feature midway through execution. According to plan-based methodology, what should the project team do first?
- Reject the request because the scope baseline has already been approved
- Immediately implement the change to keep the stakeholder satisfied
- Add the feature quietly without updating the schedule or budget
- Submit the request through the formal change control process for evaluation and approval before any work begins
Correct answer: Submit the request through the formal change control process for evaluation and approval before any work begins
The team should submit the request through the formal change control process for evaluation and approval before any work begins. In a predictive, plan-based approach, changes to a baseline must be documented as change requests, assessed for impact on scope, schedule, cost, and risk, and approved (often by a change control board) before implementation. Acting on a change without evaluation, or implementing it informally, leads to scope creep and undermines the integrity of the baselines.
A new team is choosing a delivery approach. Requirements are expected to change frequently as customers see working software, and the sponsor wants usable functionality released early and often rather than at the very end. Which approach best fits this situation?
- A phase-gate approach that forbids any change after initiation
- A purely sequential waterfall lifecycle with locked requirements
- A predictive, plan-based approach with a single delivery at the end
- An agile, adaptive approach with frequent incremental releases
Correct answer: An agile, adaptive approach with frequent incremental releases
An agile, adaptive approach with frequent incremental releases is the best fit. Agile is designed for high uncertainty and changing requirements, delivering working functionality in short cycles so customers can give feedback and the team can adapt. A predictive approach excels when requirements are stable and well understood up front, which is the opposite of this scenario.
Which statement best captures the core difference between a predictive (plan-based) and an agile (adaptive) approach to project work?
- Predictive uses no documentation, while agile relies entirely on detailed documentation
- Predictive delivers in short iterations, while agile delivers everything at the end
- Predictive locks scope, schedule, and cost up front, while agile keeps scope flexible and adapts as the team learns
- Predictive has no project manager, while agile requires two project managers
Correct answer: Predictive locks scope, schedule, and cost up front, while agile keeps scope flexible and adapts as the team learns
The defining difference is that predictive approaches define scope, schedule, and cost in detail at the start and manage change against that baseline, whereas agile approaches fix time and cost but allow scope to flex and evolve through iterations as learning occurs. The other statements reverse the delivery cadence or misstate documentation, which is not the real distinction.
On a Scrum project, a developer finishes a backlog item and asks how the team decides whether it is truly complete and ready to count toward the increment. Which artifact provides this shared, objective standard?
- The sprint goal
- The definition of done
- The product roadmap
- The velocity chart
Correct answer: The definition of done
The definition of done provides the shared, objective standard for when work is complete. It is a checklist of quality criteria (for example, coded, tested, integrated, documented) that every increment must satisfy, ensuring transparency about what 'done' means. The sprint goal states the objective of the sprint but does not define completion criteria for individual items.
A Scrum team holds a recurring time-boxed event in which the team and stakeholders inspect the increment produced during the iteration, gather feedback, and discuss what to do next. Which event is this?
- The daily standup
- The sprint planning event
- The sprint retrospective
- The sprint review
Correct answer: The sprint review
This describes the sprint review, a working session at the end of the sprint where the Scrum Team and stakeholders inspect the increment, gather feedback, and adapt the product backlog as needed. It is distinct from the retrospective, which focuses on improving the team's process rather than the product.
At the end of each iteration, a Scrum team meets privately to inspect how the last iteration went regarding people, interactions, processes, and tools, and to plan improvements. Which event is this?
- The backlog refinement session
- The sprint planning event
- The sprint review
- The sprint retrospective
Correct answer: The sprint retrospective
This is the sprint retrospective, whose purpose is to plan ways to increase quality and effectiveness by inspecting the team's own process and identifying improvements for the next iteration. The sprint review, by contrast, inspects the product increment with stakeholders rather than the team's working methods.
In Scrum, what is a sprint?
- A document that lists all features the product will ever contain
- A meeting where the team estimates the size of backlog items
- A status report sent to executives at the end of the project
- A short, fixed-length time-box during which a usable increment is created
Correct answer: A short, fixed-length time-box during which a usable increment is created
A sprint is a short, fixed-length time-box (commonly one to four weeks) during which the Scrum Team produces a usable, potentially releasable product increment. Sprints have consistent durations to create a predictable rhythm; the other options describe estimation, the product backlog, and reporting, none of which is a sprint.
A team maintains a single, ordered list of everything that might be needed in the product, continuously refined and reprioritized by the product owner. What is this list called?
- The impediment log
- The product backlog
- The definition of done
- The sprint backlog
Correct answer: The product backlog
The product backlog is the single, emergent, ordered list of all work that could improve the product, owned and prioritized by the product owner. The sprint backlog is a different, smaller artifact: the subset of work the team commits to for the current sprint plus a plan to deliver it.
During sprint planning, a Scrum team selects items from the product backlog and creates a plan to deliver them in the upcoming iteration. What is the resulting set of selected items plus the plan called?
- The sprint backlog
- The product roadmap
- The product backlog
- The release plan
Correct answer: The sprint backlog
The result is the sprint backlog: the product backlog items selected for the sprint plus a plan for delivering them and achieving the sprint goal. It is owned by the developers and updated throughout the sprint, whereas the product backlog spans the entire product and is owned by the product owner.
A team wants a relative measure of the effort, complexity, and uncertainty involved in completing a backlog item, rather than an estimate in hours. What technique are they using when they assign values like 1, 2, 3, 5, and 8 to items?
- Net present value
- Story points
- Critical path duration
- Earned value
Correct answer: Story points
They are using story points, a relative unit that captures effort, complexity, and uncertainty for a backlog item rather than a precise time estimate. Teams often use a Fibonacci-like scale because relative sizing is faster and more reliable than absolute hour estimates early on. Earned value and critical path are predictive measures, not agile sizing units.
An agile team adds up the story points of all items it actually completed in the last several iterations to forecast how much it can take on next time. What is this measure called?
- Cumulative flow
- Lead time
- Velocity
- Cycle time
Correct answer: Velocity
This measure is velocity: the total story points completed per iteration, averaged over recent iterations to forecast future capacity. Velocity is a planning aid for the team itself and should not be used to compare teams, since point scales are relative. Lead time and cycle time measure duration, not completed effort.
A stakeholder asks for a simple chart that shows how much work remains in the current sprint, trending toward zero as the sprint ends. Which chart should the team show?
- A burndown chart
- A burnup chart
- A Pareto chart
- A control chart
Correct answer: A burndown chart
A burndown chart is the right answer: it plots remaining work (usually in story points) on the vertical axis against time on the horizontal axis, trending downward toward zero as the sprint progresses. A burnup chart instead tracks work completed against total scope, so it trends upward rather than down.
A product owner wants a chart that shows both the amount of work completed over time and the total scope, so that scope changes are clearly visible as a separate line. Which chart provides this?
- A burndown chart
- A responsibility assignment matrix
- A burnup chart
- A velocity chart
Correct answer: A burnup chart
A burnup chart is correct: it plots completed work as a rising line and shows total scope as a separate line, making added or removed scope visually obvious. A burndown chart only shows remaining work as one descending line, so scope changes are harder to distinguish from progress.
A team visualizes its workflow using columns such as To Do, In Progress, and Done, moving cards across the columns to make the flow of work visible. What is this tool called?
- A kanban board
- A network diagram
- A Gantt chart
- A fishbone diagram
Correct answer: A kanban board
This is a kanban board, a visual tool that maps the stages of a workflow as columns and represents work items as cards that move left to right, making bottlenecks and flow visible to everyone. A Gantt chart shows scheduled task bars over a timeline and is a predictive scheduling tool, not a pull-based flow board.
Which statement best describes the Kanban method as used in agile work management?
- A predictive scheduling technique that calculates float for each activity
- A flow-based method that visualizes work, limits work in progress, and pulls items as capacity frees up
- A time-boxed framework with fixed-length sprints and a scrum master role
- A contract type used to transfer cost risk to a vendor
Correct answer: A flow-based method that visualizes work, limits work in progress, and pulls items as capacity frees up
Kanban is a flow-based method that visualizes work on a board, limits work in progress, and pulls new items only as capacity becomes available, optimizing continuous flow rather than fixed iterations. It does not prescribe sprints or a scrum master; those belong to Scrum. The contract and scheduling options describe unrelated predictive concepts.
A team using a kanban board sets a rule that no more than three items may be in the In Progress column at any time. What is this rule called, and what is its main benefit?
- A work-in-progress limit, which improves flow and exposes bottlenecks
- A sprint goal, which focuses the iteration
- A buffer, which protects the critical chain
- A definition of done, which sets quality criteria
Correct answer: A work-in-progress limit, which improves flow and exposes bottlenecks
This is a work-in-progress (WIP) limit, which caps how many items can be worked on at once. By limiting WIP, the team reduces multitasking, shortens cycle time, and quickly exposes bottlenecks because work piles up visibly before a constrained stage. A definition of done sets quality criteria, not flow limits.
A program manager must explain the practical difference between Scrum and Kanban to a new team. Which contrast is accurate?
- Scrum forbids visual boards, while Kanban forbids backlogs
- Scrum has no roles, while Kanban requires a scrum master and product owner
- Scrum is only for hardware, while Kanban is only for software
- Scrum uses fixed-length sprints with set roles and events, while Kanban uses continuous flow with WIP limits and no required iterations
Correct answer: Scrum uses fixed-length sprints with set roles and events, while Kanban uses continuous flow with WIP limits and no required iterations
The accurate contrast is that Scrum organizes work into fixed-length sprints with defined roles and events, while Kanban manages a continuous flow of work governed by WIP limits without mandated iterations or roles. The other statements invert the roles or invent restrictions that neither framework imposes.
Which set of accountabilities correctly belongs to the Scrum framework?
- Functional manager, change control board, and steering committee
- Release train engineer, architect, and tester only
- Product owner, scrum master, and developers
- Project manager, business analyst, and sponsor
Correct answer: Product owner, scrum master, and developers
The Scrum framework defines three accountabilities: the product owner (maximizes product value and orders the backlog), the scrum master (fosters effectiveness and removes impediments), and the developers (create the increment). Project manager, sponsor, and change control board are predictive or governance roles outside the Scrum framework itself.
A scrum master notices the team is blocked because a vendor has not delivered test data, and team members are frustrated by an unhelpful tool. Which action best reflects the scrum master's role?
- Approve or reject scope changes on behalf of stakeholders
- Remove the impediment by escalating the vendor issue and addressing the tool problem
- Assign tasks to each developer and track their hours
- Take over prioritization of the product backlog
Correct answer: Remove the impediment by escalating the vendor issue and addressing the tool problem
Removing the impediment by escalating the vendor delay and addressing the tool problem is the correct action; a scrum master serves the team by clearing obstacles and coaching, acting as a servant leader rather than a directive manager. Assigning tasks and prioritizing the backlog belong to the developers and product owner respectively.
A delivery approach builds the product in repeated cycles, where each cycle refines and improves the same solution based on feedback before it is considered finished. Which term describes this approach?
- Resource leveling
- Iterative development
- Predictive sequencing
- Fast tracking
Correct answer: Iterative development
This is iterative development: the team repeatedly revisits and refines the solution across cycles, using feedback to improve it until it meets the need. It differs from incremental delivery, which focuses on delivering usable pieces of the whole; iteration emphasizes refining the same work through successive passes.
A team releases the product in usable pieces, delivering a small slice of complete functionality at a time so users can begin getting value before the entire product is finished. Which term describes this?
- Incremental delivery
- Earned value management
- Critical path scheduling
- Scope baselining
Correct answer: Incremental delivery
This is incremental delivery: completed, usable slices of functionality are delivered over time, letting stakeholders realize value early rather than waiting for one final release. While often combined with iterative development, incremental delivery specifically emphasizes shipping working pieces of the whole as they are completed.
A hybrid project uses a predictive plan for the regulated, well-understood compliance components and an agile approach for the customer-facing features that are still evolving. What does this tailoring decision best demonstrate?
- That hybrid approaches are not allowed under current PMI guidance
- That development approach can be tailored to the nature of each part of the work
- That agile and predictive can never be combined on a single project
- That the team should pick one approach and apply it to all work uniformly
Correct answer: That development approach can be tailored to the nature of each part of the work
This demonstrates that the development approach can and should be tailored to the nature of the work, blending predictive and agile methods within one project where each fits best. Current PMI guidance explicitly supports hybrid approaches and tailoring; the claim that the team must apply one approach uniformly contradicts the principle of tailoring.
In an agile context, a leader focuses on supporting the team by removing obstacles, providing resources, and enabling self-organization rather than commanding and controlling. Which leadership style is this?
- Transactional micromanagement
- Directive command-and-control
- Laissez-faire absence
- Servant leadership
Correct answer: Servant leadership
This is servant leadership, the agile mindset in which leaders serve the team by clearing impediments, supplying what the team needs, and fostering self-organization and growth. It contrasts with command-and-control, where a manager directs every task; servant leadership prioritizes enabling the team over directing it.
An agile team meets briefly each day, time-boxed to about fifteen minutes, to synchronize, inspect progress toward the sprint goal, and adapt the plan for the next day. What is this event called?
- The sprint retrospective
- The sprint review
- The daily standup (daily scrum)
- The backlog refinement
Correct answer: The daily standup (daily scrum)
This is the daily standup, also called the daily scrum: a short, time-boxed event for the developers to synchronize work, inspect progress toward the sprint goal, and replan for the coming day. It is not a status meeting for managers; it is for the team to coordinate its own work.
On a kanban board, the team measures the elapsed time from when a work item is pulled into active work until it is completed and ready for delivery. Which flow metric is this?
- Lead time
- Cycle time
- Velocity
- Schedule variance
Correct answer: Cycle time
This is cycle time: the elapsed time from when active work begins on an item until it is finished. Lead time, by contrast, is usually measured from when the item is requested or enters the backlog. Both are flow metrics, but cycle time starts the clock when work actually begins.
A product owner orders the product backlog so the team works on the most valuable items first. Which principle most directly supports this ordering?
- Deliver the highest-value work early to maximize value and gather feedback
- Build the least risky items last to avoid early learning
- Treat every backlog item as equally important regardless of value
- Complete all documentation before any feature work begins
Correct answer: Deliver the highest-value work early to maximize value and gather feedback
Ordering the backlog to deliver the highest-value work early maximizes the value realized and surfaces feedback sooner, a core agile principle. Deferring risky or high-value learning, front-loading all documentation, or treating items as equally important would undermine the value-driven prioritization that backlog ordering is meant to achieve.
During backlog refinement, the product owner and team add detail, estimates, and order to upcoming items so they are ready for future sprints. What is the main goal of this ongoing activity?
- To assign permanent task owners for every item
- To finalize the entire project budget
- To keep upcoming backlog items clear, estimated, and prioritized so sprints can start smoothly
- To replace the need for sprint planning
Correct answer: To keep upcoming backlog items clear, estimated, and prioritized so sprints can start smoothly
The main goal of backlog refinement is to keep upcoming items clear, appropriately sized, and ordered so the team can plan and start sprints efficiently. It is a continuous activity, not a one-time budgeting event, and it complements rather than replaces sprint planning, which still selects the work for each sprint.
A team commits to demonstrating a working, integrated increment at the end of every two-week sprint instead of waiting until the project ends. What primary benefit does this cadence provide?
- It eliminates the need for any testing
- It provides frequent feedback and reduces the risk of building the wrong thing
- It guarantees the project finishes under budget
- It removes the need for a product owner
Correct answer: It provides frequent feedback and reduces the risk of building the wrong thing
Frequent delivery of a working increment provides regular stakeholder feedback and reduces the risk of investing in the wrong features, since course corrections happen early and often. It does not eliminate testing or guarantee budget outcomes, and the product owner remains essential for prioritizing what each increment should contain.
An agile team writes its requirements in the form 'As a (user), I want (capability) so that (benefit).' What is the primary purpose of expressing work this way?
- To calculate the critical path of the project
- To produce a legally binding contract with the customer
- To replace the product backlog entirely
- To capture requirements from the user's perspective and clarify the value delivered
Correct answer: To capture requirements from the user's perspective and clarify the value delivered
Writing requirements as user stories captures them from the user's perspective and makes the intended value explicit, which keeps the team focused on outcomes rather than just outputs. User stories are backlog items, not contracts, and they do not replace the backlog or relate to critical-path calculation.
A user story is marked ready for development only after the team agrees on the conditions that must be true for it to be considered satisfactory. What are these story-level conditions called?
- Earned value baselines
- Acceptance criteria
- The definition of ready's velocity
- Risk thresholds
Correct answer: Acceptance criteria
These are acceptance criteria: the specific conditions a single user story must meet to be accepted as satisfactory. They are story-specific, whereas the definition of done is a broader quality standard applied to every increment. Earned value baselines and risk thresholds are unrelated predictive concepts.
A leadership team wants teams to be authorized to decide among themselves how best to accomplish their work rather than being told exactly how. Which agile characteristic does this describe?
- Self-organizing (self-managing) teams
- A strict functional hierarchy
- A change control board controlling daily work
- Centralized command of all task assignments
Correct answer: Self-organizing (self-managing) teams
This describes self-organizing, self-managing teams, an agile characteristic in which the team itself decides how to turn backlog items into a working increment. It contrasts with a strict hierarchy or centralized assignment of every task; agile pushes those decisions to the people doing the work to improve responsiveness and ownership.
A team conducts a short, time-boxed investigation to answer a technical question and reduce uncertainty before committing to a backlog item. What is this called in agile practice?
- A release burndown
- A milestone
- A retrospective
- A spike
Correct answer: A spike
This is a spike: a time-boxed research or prototyping activity used to gain enough knowledge to estimate or design a risky or unclear item. Unlike a retrospective (process improvement) or a milestone (a schedule marker), a spike exists specifically to reduce technical or functional uncertainty.
An organization adopts the practice of inspecting work and processes at regular intervals and adapting based on what is learned. Which empirical agile pillars does this reflect?
- Transparency, inspection, and adaptation
- Avoid, transfer, and accept
- Initiating, planning, and closing
- Power, interest, and influence
Correct answer: Transparency, inspection, and adaptation
This reflects transparency, inspection, and adaptation, the empirical pillars underlying Scrum and agile generally: make work visible, inspect it frequently, and adapt based on findings. The other options list predictive process groups, risk responses, and stakeholder-analysis dimensions, none of which are the empirical pillars.
A coach explains that agile reduces the cost of large, late corrections by working in small batches. Which lifecycle is described by short cycles that each produce a tested, usable increment and incorporate feedback before the next cycle?
- A phase-gate lifecycle with no feedback loops
- An adaptive (agile) lifecycle
- A pure predictive lifecycle
- A single-pass waterfall lifecycle
Correct answer: An adaptive (agile) lifecycle
This is an adaptive (agile) lifecycle, characterized by short cycles that each deliver a tested increment and feed learning into the next cycle. A predictive or waterfall lifecycle plans extensively up front and delivers later with limited intermediate feedback, which is why large corrections become costly when discovered late.
A team wants a visual tool that shows the quantity of work in each workflow stage over time to spot where items are accumulating and flow is being constrained. Which chart best serves this?
- A net present value chart
- A responsibility assignment matrix
- A stakeholder power/interest grid
- A cumulative flow diagram
Correct answer: A cumulative flow diagram
A cumulative flow diagram is the right tool: it stacks the amount of work in each stage over time, so widening bands reveal where items accumulate and flow is constrained. The other options address responsibility assignment, financial valuation, and stakeholder analysis, none of which visualize workflow flow.
A product owner is uncertain whether to keep refining a feature or release it. Which agile concept guides the choice to release once the increment delivers enough value to be useful, even if not every possible enhancement is included?
- Critical path
- Configuration management
- Cost performance index
- Minimum viable product (MVP)
Correct answer: Minimum viable product (MVP)
This is the minimum viable product (MVP): the smallest releasable version that delivers meaningful value and enables learning from real users. It guides releasing early rather than gold-plating. The other options are predictive scheduling, cost-control, and product-consistency concepts unrelated to deciding when an increment is valuable enough to ship.
A team practices delivering small changes to a shared codebase frequently, with automated builds and tests verifying each change so integration problems surface immediately. Which agile engineering practice is this?
- Earned schedule
- Procurement auditing
- Continuous integration
- Resource smoothing
Correct answer: Continuous integration
This is continuous integration: developers integrate small changes often, and automated builds and tests catch defects quickly, reducing the pain of large, late integrations. Resource smoothing, earned schedule, and procurement auditing are predictive scheduling, performance-measurement, and contract concepts unrelated to code integration.
In an agile environment, the customer or product owner remains continuously available to clarify needs and make decisions throughout the project. Why is this collaboration so important to agile success?
- Because it removes the need for any backlog
- Because it transfers all decision authority to the development team
- Because it lets the team get fast answers and adapt to evolving needs, reducing rework
- Because it guarantees the scope will never change
Correct answer: Because it lets the team get fast answers and adapt to evolving needs, reducing rework
Ongoing customer collaboration lets the team get fast clarification and adapt to evolving needs, which reduces rework and keeps the product aligned with value. It does not remove the backlog or hand all decisions to developers; agile expects scope to change, and close collaboration is precisely how the team manages that change well.
A scaling team must coordinate several Scrum teams building one product. Which approach is specifically intended to coordinate multiple agile teams working on the same product?
- A scaled agile framework such as SAFe or LeSS
- The critical chain method
- Monte Carlo simulation
- A fixed-price incentive contract
Correct answer: A scaled agile framework such as SAFe or LeSS
A scaled agile framework such as SAFe or LeSS is designed to coordinate and align multiple agile teams working on a single product or solution. The critical chain method, fixed-price contracts, and Monte Carlo simulation are predictive scheduling, procurement, and risk-analysis techniques, not approaches for scaling agile across teams.
A team estimates backlog items together using a card-based, relative-sizing technique where each member reveals an estimate simultaneously and the team discusses differences. What is this technique commonly called?
- Planning poker
- Critical path analysis
- Earned value analysis
- Resource leveling
Correct answer: Planning poker
This is planning poker, a collaborative, relative-estimation technique in which team members reveal estimates at the same time, then discuss outliers to reach a shared estimate. Revealing simultaneously reduces anchoring bias. The other options are predictive cost, schedule, and resource techniques, not estimation games.
An agile team measures the percentage of time work items spend actively being worked versus waiting in queues, aiming to increase the proportion of active time. Which flow concept are they trying to improve?
- Cost variance
- Flow efficiency
- Risk appetite
- Schedule baseline
Correct answer: Flow efficiency
They are improving flow efficiency, the ratio of active work time to total time (active plus waiting) for an item. Increasing flow efficiency means reducing time items spend idle in queues, which shortens delivery time. Cost variance, schedule baseline, and risk appetite are unrelated predictive and governance concepts.
A team treats the work it does not finish in one iteration by returning incomplete items to the backlog for reprioritization rather than extending the iteration. Why is keeping the iteration length fixed important in agile?
- It preserves a steady cadence that makes velocity and forecasting reliable
- It eliminates the need for a product owner
- It guarantees that all items will always be completed
- It prevents the backlog from ever changing
Correct answer: It preserves a steady cadence that makes velocity and forecasting reliable
Keeping the iteration length fixed preserves a steady, predictable cadence, which makes velocity meaningful and forecasting more reliable. Extending iterations to fit unfinished work would distort velocity. Fixed length does not guarantee completion of every item, remove the product owner, or freeze the backlog.
A leadership group debates whether agile is appropriate for a project with stable, well-defined requirements, low change, and a need for extensive up-front regulatory documentation. What is the best tailoring conclusion?
- Agile must always be used regardless of context
- Hybrid approaches are prohibited by PMI
- No approach can handle regulated work
- A predictive approach may suit this work better than a fully agile one
Correct answer: A predictive approach may suit this work better than a fully agile one
The best conclusion is that a predictive approach may suit this work better, because stable requirements, low change, and heavy up-front documentation are conditions where plan-based delivery excels. Agile is not mandatory in every context; tailoring means matching the approach to the situation, and hybrid approaches are explicitly supported, not prohibited.
An agile team reaches the end of a sprint with an increment that meets the definition of done but the product owner decides not to release it yet. Which statement is accurate about this increment?
- It must be discarded since it was not released
- It cannot count toward velocity because it was not deployed
- It is potentially releasable, and the decision of when to release belongs to the product owner
- It is invalid because every increment must be released immediately
Correct answer: It is potentially releasable, and the decision of when to release belongs to the product owner
The increment is potentially releasable, meaning it meets the quality bar to be released, but the timing of release is a business decision the product owner makes. Increments need not be deployed immediately, are not discarded for being held, and still count as completed work toward velocity once they meet the definition of done.
A project sponsor asks a team member to explain what business analysis contributes to a project. Which description most accurately captures the purpose of business analysis in a project context?
- The procurement discipline that selects sellers and administers contracts
- The scheduling discipline that sequences activities and calculates the critical path
- The set of activities that elicit, analyze, document, and validate requirements so that the solution delivers business value and meets stakeholder needs
- The financial discipline that tracks earned value against the cost baseline
Correct answer: The set of activities that elicit, analyze, document, and validate requirements so that the solution delivers business value and meets stakeholder needs
Business analysis is the set of activities that elicit, analyze, document, and validate requirements so the resulting solution delivers business value and meets stakeholder needs. It bridges the business problem and the solution, while scheduling, earned value, and procurement are separate project management disciplines that do not define what the solution must do.
On a new project, a stakeholder confuses the work of the business analyst with that of the project manager. Which responsibility belongs primarily to the business analyst rather than the project manager?
- Eliciting, analyzing, and managing the product requirements with stakeholders
- Building the project schedule and managing the critical path
- Approving change requests through integrated change control
- Authorizing the project and committing organizational resources
Correct answer: Eliciting, analyzing, and managing the product requirements with stakeholders
Eliciting, analyzing, and managing product requirements with stakeholders is the core responsibility of the business analyst. Authorizing the project, owning the schedule, and approving changes are project manager (or sponsor) responsibilities; the BA focuses on the product/solution requirements, not project authorization or schedule control.
A team is selecting how to approach requirements work for a complex initiative. What best describes a business analysis framework?
- A government regulation that mandates how requirements must be stored
- A fixed contract template used to procure external vendors
- A software tool that automatically generates the project schedule
- A structured set of techniques and practices for performing business analysis activities such as elicitation, modeling, prioritization, and validation
Correct answer: A structured set of techniques and practices for performing business analysis activities such as elicitation, modeling, prioritization, and validation
A business analysis framework is a structured set of techniques and practices used to perform business analysis activities such as elicitation, modeling, prioritization, and validation. It guides how the analyst works rather than being a contract template, a regulation, or a scheduling tool.
A stakeholder writes, 'The company needs to reduce average order-processing time to remain competitive.' How should the business analyst classify this statement?
- A functional requirement
- A business requirement
- A transition requirement
- A nonfunctional quality attribute
Correct answer: A business requirement
This is a business requirement because it expresses a high-level goal and the value the organization seeks, not a specific system behavior. Functional requirements describe what the solution must do in detail; this statement instead explains why the work matters and the desired future state.
A team needs to document exactly what a new system must do, such as 'the system shall send a confirmation email when an order is submitted.' Which requirement type does this represent?
- Stakeholder need statement
- Business requirement
- Functional requirement
- Transition requirement
Correct answer: Functional requirement
A statement describing a specific behavior the solution must perform, such as sending a confirmation email on order submission, is a functional requirement. It is far more granular than a business requirement, which states the high-level objective rather than the detailed behavior.
During solution design, a stakeholder states the system 'must respond to a search query in under two seconds.' How should the business analyst classify this requirement?
- A stakeholder requirement
- A functional requirement
- A business requirement
- A nonfunctional requirement
Correct answer: A nonfunctional requirement
A response-time constraint such as 'under two seconds' is a nonfunctional requirement because it describes a quality attribute or performance characteristic rather than a discrete function the system performs. Functional requirements describe what the system does; nonfunctional requirements describe how well it does it.
A business analyst is preparing to gather requirements from stakeholders. What does requirements elicitation mean?
- The act of approving the final scope baseline
- The process of compressing the project schedule
- The act of formally signing off on completed deliverables
- The activity of drawing out information, needs, and expectations from stakeholders and other sources
Correct answer: The activity of drawing out information, needs, and expectations from stakeholders and other sources
Requirements elicitation is the activity of drawing out information, needs, and expectations from stakeholders and other sources. It is an active discovery process, distinct from approving scope, compressing the schedule, or formally accepting deliverables.
A business analyst wants to observe how warehouse staff actually perform a task before designing a new system. Which elicitation technique best fits this need?
- Prototyping
- Document analysis
- Brainstorming
- Job shadowing or observation
Correct answer: Job shadowing or observation
Observation, also called job shadowing, is the elicitation technique of watching stakeholders perform their work in their real environment. It uncovers actual behavior and tacit needs that interviews may miss, whereas document analysis, brainstorming, and prototyping draw on existing materials, group ideation, or mock-ups rather than direct observation.
A business analyst needs requirements quickly from many stakeholders who must reach shared agreement in one session. Which elicitation technique is most appropriate?
- One-on-one interviews conducted over several weeks
- An anonymous survey
- A facilitated workshop
- Solitary document analysis
Correct answer: A facilitated workshop
A facilitated workshop brings many stakeholders together in a structured session to elicit, refine, and reach consensus on requirements quickly. Sequential interviews, solitary document analysis, and anonymous surveys lack the real-time, collaborative consensus-building that a facilitated workshop provides.
A business analyst hands stakeholders an early mock-up of screens so they can react and refine their requirements through feedback. Which elicitation technique is being used?
- Document analysis
- Focus group
- Reverse engineering
- Prototyping
Correct answer: Prototyping
Prototyping presents an early, often low-fidelity model of the solution so stakeholders can react and clarify their needs. It is especially useful when requirements are uncertain, unlike document analysis or focus groups, which do not give stakeholders a tangible model to evaluate.
After several elicitation sessions, a stakeholder asks the business analyst what 'requirements management' encompasses. Which answer is most accurate?
- Only the act of writing requirements in a document
- The process of estimating activity durations
- The ongoing activities of organizing, tracing, prioritizing, maintaining, and controlling changes to requirements throughout the project
- Only the approval of the project charter
Correct answer: The ongoing activities of organizing, tracing, prioritizing, maintaining, and controlling changes to requirements throughout the project
Requirements management is the ongoing discipline of organizing, tracing, prioritizing, maintaining, and controlling changes to requirements throughout the project. It is broader than simply documenting requirements once and is unrelated to chartering the project or estimating durations.
A business analyst wants to ensure every requirement can be tracked from its origin through design, build, and testing. Which tool is designed for this purpose?
- A risk register
- A requirements traceability matrix
- A responsibility assignment matrix
- A stakeholder engagement assessment matrix
Correct answer: A requirements traceability matrix
A requirements traceability matrix links each requirement to its source and forward to design, build, and test artifacts so coverage can be tracked. A responsibility assignment matrix maps people to tasks, a risk register tracks risks, and an engagement matrix tracks stakeholder attitudes, none of which trace requirements.
An auditor asks how the team can prove that every approved requirement was actually built and tested. What does a requirements traceability matrix primarily provide here?
- An estimate of the project budget at completion
- A calculation of schedule variance
- Bidirectional linkage showing each requirement maps to deliverables and tests, confirming full coverage
- A ranking of stakeholders by power and interest
Correct answer: Bidirectional linkage showing each requirement maps to deliverables and tests, confirming full coverage
A requirements traceability matrix provides bidirectional linkage showing that each requirement maps to deliverables and tests, confirming complete coverage with no gaps or orphaned work. It is evidence of coverage, not a schedule, stakeholder, or budget tool.
A team must decide which requirements to deliver first when time and budget are limited. What is the goal of requirements prioritization?
- To assign team members to activities
- To finalize the project charter
- To rank requirements by factors such as business value, risk, cost, and dependency so the most important are addressed first
- To eliminate the need for stakeholder input
Correct answer: To rank requirements by factors such as business value, risk, cost, and dependency so the most important are addressed first
Requirements prioritization ranks requirements by factors such as business value, risk, cost, and dependencies so the most important ones are addressed first. It does not remove stakeholder involvement, charter the project, or staff activities; it sequences delivery of value.
A product owner sorts backlog items into 'Must have,' 'Should have,' 'Could have,' and 'Won't have this time.' Which prioritization technique is being used?
- Critical path method
- Monte Carlo simulation
- RACI charting
- MoSCoW
Correct answer: MoSCoW
Sorting items into Must, Should, Could, and Won't-have categories is the MoSCoW prioritization technique. Monte Carlo simulation models uncertainty, RACI clarifies roles, and the critical path method analyzes schedule, so none of those prioritize requirements by importance.
To prioritize a long backlog, a team scores each item by dividing the value it delivers by the effort to build it and works the highest scores first. Which prioritization approach is this?
- Resource leveling
- Three-point estimating
- Decomposition
- Value-versus-effort scoring
Correct answer: Value-versus-effort scoring
Scoring items by value relative to effort and working the highest ratios first is a value-versus-effort prioritization approach used to maximize early return. Three-point estimating, resource leveling, and decomposition address estimation, resource demand, and scope breakdown, not prioritization by value.
An agile team writes work items in the format 'As a frequent shopper, I want to save my payment details so that checkout is faster.' What is this artifact called?
- A statement of work
- A business case
- A use case specification
- A user story
Correct answer: A user story
The 'As a [role], I want [goal] so that [benefit]' format is a user story, a short statement of need from the user's perspective. A use case specification, business case, and statement of work are more formal and detailed documents serving different purposes.
A product owner adds acceptance criteria to a user story. What is the primary purpose of these acceptance criteria?
- To estimate the project's total cost
- To set the contract type for procurement
- To define the conditions the story must satisfy to be considered complete and correct
- To assign the story to a specific developer
Correct answer: To define the conditions the story must satisfy to be considered complete and correct
Acceptance criteria define the specific conditions a user story must satisfy to be considered complete and correct, giving the team a shared, testable definition of done for that story. They are not cost estimates, work assignments, or procurement terms.
A stakeholder asks for a high-level, time-oriented view of how the product will evolve and what major capabilities will be delivered over upcoming releases. Which artifact meets this need?
- A risk register
- A requirements traceability matrix
- A product roadmap
- A work breakdown structure dictionary
Correct answer: A product roadmap
A product roadmap is a high-level, time-oriented visual that communicates how the product will evolve and the major capabilities planned across upcoming releases. A traceability matrix tracks requirement coverage, a risk register tracks risks, and a WBS dictionary details scope work, none of which convey the product vision over time.
A team debates the difference between the product roadmap and the product backlog. Which statement is accurate?
- The roadmap is owned by the scrum master and the backlog by the sponsor
- The roadmap and backlog are identical artifacts with different names
- The roadmap communicates strategic direction and major milestones over time, while the backlog is the ordered, detailed list of work to be done
- The roadmap lists every detailed task while the backlog shows only strategic themes
Correct answer: The roadmap communicates strategic direction and major milestones over time, while the backlog is the ordered, detailed list of work to be done
The product roadmap communicates strategic direction and major milestones over time, while the product backlog is the ordered, detailed list of work the team will actually do. The roadmap is higher-level and longer-horizon; the backlog is granular and continually refined, and the product owner owns the backlog.
A stakeholder asks who is accountable for maximizing the value of the product and managing the backlog on an agile project. Which role fits?
- The product owner
- The project sponsor's delegate for procurement
- The scrum master
- The functional manager
Correct answer: The product owner
The product owner is accountable for maximizing product value and for managing and ordering the product backlog so the team works on the most valuable items first. The scrum master facilitates the process, while functional managers and procurement delegates do not own product value or the backlog.
A new team member asks how the product owner differs from the business analyst. Which distinction is most accurate in a typical agile setting?
- The product owner is accountable for prioritizing value and deciding what gets built, while the business analyst often elicits and details the requirements that support those decisions
- They are always the same person with no difference
- The product owner writes the code and the business analyst tests it
- The business analyst sets the budget and the product owner sets the schedule
Correct answer: The product owner is accountable for prioritizing value and deciding what gets built, while the business analyst often elicits and details the requirements that support those decisions
The product owner is accountable for prioritizing value and deciding what gets built, while the business analyst often elicits, analyzes, and details the underlying requirements that inform those decisions. The two roles can overlap but are not identical, and neither is defined by budgeting, scheduling, coding, or testing.
After a solution has been deployed, a business analyst measures whether it actually delivered the intended business benefits. What is this activity called?
- Scope decomposition
- Solution evaluation
- Requirements elicitation
- Stakeholder identification
Correct answer: Solution evaluation
Solution evaluation is the business analysis activity of assessing whether a deployed or proposed solution delivers the intended business value and meets needs. It happens after or alongside delivery, unlike elicitation, stakeholder identification, or scope decomposition, which occur earlier.
During solution evaluation, a business analyst finds the solution works as built but is not delivering the expected business value. What should the analyst recommend first?
- Analyze the performance gap and its causes, then recommend adjustments to close the gap and realize value
- Immediately cancel the entire program
- Ignore the finding because the solution meets functional requirements
- Reassign the project manager
Correct answer: Analyze the performance gap and its causes, then recommend adjustments to close the gap and realize value
When a solution works but does not deliver expected value, the analyst should analyze the performance gap and its causes, then recommend adjustments to close it. Meeting functional requirements is not the same as delivering value, so neither ignoring the gap nor abruptly canceling or reassigning is the appropriate first step.
A business analyst must verify a set of requirements before sharing them with developers. What is the goal of requirements verification?
- To compress the project schedule
- To confirm the requirements are well-formed, clear, consistent, and meet quality standards
- To select the contract type
- To confirm the requirements deliver the desired business value to stakeholders
Correct answer: To confirm the requirements are well-formed, clear, consistent, and meet quality standards
Requirements verification confirms that requirements are well-formed, clear, consistent, complete, and meet quality standards, essentially asking 'did we write them right.' This differs from validation, which asks whether the requirements deliver the desired business value, and is unrelated to scheduling or procurement.
A stakeholder reviews documented requirements and asks whether they truly reflect the business need and will deliver value. Which business analysis activity addresses this question?
- Requirements decomposition
- Requirements validation
- Requirements verification
- Requirements baselining
Correct answer: Requirements validation
Requirements validation confirms that the requirements actually reflect the business need and will deliver the intended value, asking 'did we write the right requirements.' Verification instead checks quality and correctness of form, while decomposition and baselining concern breaking down and freezing requirements.
A business analyst is asked to identify everyone who has a process owner, process manager, product manager, or product owner role on the initiative. Why does the analyst distinguish these roles?
- Because role names determine the project budget
- Because the role names set the contract type
- Because each role has different authority, interests, and responsibilities that affect how requirements are elicited and decided
- Because only one of them is allowed to attend project meetings
Correct answer: Because each role has different authority, interests, and responsibilities that affect how requirements are elicited and decided
Distinguishing roles such as process owner, process manager, product manager, and product owner matters because each carries different authority, interests, and responsibilities that shape how requirements are elicited, prioritized, and decided. The distinction is about engagement and decision rights, not meeting attendance, budget, or contract type.
A business analyst needs to model the steps, decisions, and flow of an existing business process to find improvement opportunities. Which technique is most appropriate?
- Process modeling (such as a process flow diagram)
- Earned value analysis
- Reserve analysis
- Resource leveling
Correct answer: Process modeling (such as a process flow diagram)
Process modeling, such as a process flow diagram, visually represents the steps, decisions, and flow of a business process so the team can analyze and improve it. Earned value analysis, resource leveling, and reserve analysis address cost/schedule performance, resources, and contingency, not process structure.
A business analyst maps the interactions between users (actors) and a system to capture the goals each user wants to accomplish. Which modeling technique is being used?
- Variance analysis
- Critical path analysis
- Cost-benefit analysis
- Use case modeling
Correct answer: Use case modeling
Use case modeling captures the interactions between actors and a system and the goals users want to accomplish, making it a requirements analysis and modeling technique. Cost-benefit, critical path, and variance analyses serve financial and schedule purposes rather than modeling user-system interactions.
A team must decide whether a delivered increment is acceptable. The product owner checks it against agreed acceptance criteria. This activity is best described as:
- Acceptance (solution acceptance) of the requirement or increment
- Resource smoothing
- Procurement administration
- Decomposition of scope
Correct answer: Acceptance (solution acceptance) of the requirement or increment
Checking a delivered increment against agreed acceptance criteria to decide if it is acceptable is solution/requirement acceptance. It validates that what was built satisfies the defined criteria, unlike resource smoothing, decomposition, or procurement administration, which serve unrelated purposes.
A business analyst is documenting the current state and the desired future state to determine what must change. Which technique compares the two to reveal the work needed?
- Critical chain method
- Gap analysis
- Monte Carlo simulation
- Earned value management
Correct answer: Gap analysis
Gap analysis compares the current state with the desired future state to reveal the differences and the work needed to close them. Earned value management measures performance, Monte Carlo models uncertainty, and the critical chain method manages schedule buffers, none of which compare current and future states.
Before a project is approved, a business analyst documents the business problem, options considered, costs, benefits, and recommended approach. Which artifact is this?
- A user story
- A business case
- A sprint backlog
- A requirements traceability matrix
Correct answer: A business case
A business case documents the business problem or opportunity, the options considered, the costs and benefits, and a recommended approach to justify the investment. A user story, traceability matrix, and sprint backlog are downstream artifacts and do not provide the pre-project justification a business case does.
A business analyst wants to confirm a backlog item is small, clear, and ready before the team commits to it. Which set of qualities is commonly used to evaluate a good user story?
- The five process groups
- INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- SMART goals for the project schedule
- The triple constraint of scope, time, and cost
Correct answer: INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable)
The INVEST criteria, Independent, Negotiable, Valuable, Estimable, Small, and Testable, are used to judge whether a user story is well-formed and ready. SMART goals, the triple constraint, and the process groups are general project management concepts and are not story-quality checks.
A business analyst is determining which stakeholders to involve in requirements work and how. Which activity supports this?
- Stakeholder analysis to assess interest, influence, and impact on requirements
- Calculating the schedule performance index
- Performing reserve analysis
- Administering the procurement contract
Correct answer: Stakeholder analysis to assess interest, influence, and impact on requirements
Stakeholder analysis assesses each stakeholder's interest, influence, and impact so the analyst can plan how to involve them in eliciting and deciding requirements. Schedule indices, reserve analysis, and contract administration address performance, contingency, and procurement, not requirements stakeholder planning.
During elicitation, a business analyst reviews existing manuals, regulations, and system documentation to extract requirements. Which technique is this?
- Observation
- Document analysis
- Brainstorming
- Prototyping
Correct answer: Document analysis
Document analysis is the elicitation technique of reviewing existing materials such as manuals, regulations, and system documentation to extract requirements and current-state information. Brainstorming, observation, and prototyping rely on group ideation, watching work, or building mock-ups rather than studying documents.
A business analyst notices two requirements conflict with each other. What is the most appropriate next step?
- Facilitate resolution with the relevant stakeholders to reconcile the conflict and update the requirements
- Implement both as written and let developers decide
- Escalate immediately to terminate the project
- Discard both requirements without discussion
Correct answer: Facilitate resolution with the relevant stakeholders to reconcile the conflict and update the requirements
When requirements conflict, the analyst should facilitate resolution with the relevant stakeholders to reconcile the difference and update the requirements accordingly. Discarding both, implementing both blindly, or escalating to terminate the project all fail to address the underlying disagreement.
A team is grouping related user stories that together deliver a larger capability too big for one iteration. What is this larger grouping called?
- A task
- A milestone
- An epic
- A spike
Correct answer: An epic
An epic is a large body of work that groups related user stories delivering a bigger capability and is too large to complete in a single iteration. A spike is a time-boxed investigation, a task is a small unit of work, and a milestone marks a schedule point, none of which describe a large grouping of stories.
A business analyst wants stakeholders to confirm priorities by assigning a fixed number of points across competing requirements. Which prioritization technique fits?
- The hundred-dollar (or fixed-point allocation) method
- Three-point estimating
- Decomposition
- Resource leveling
Correct answer: The hundred-dollar (or fixed-point allocation) method
The hundred-dollar method, a fixed-point allocation technique, has stakeholders distribute a set number of points or dollars across requirements to reveal relative priority. Resource leveling, decomposition, and three-point estimating serve resourcing, scope breakdown, and estimation purposes rather than prioritization.
A stakeholder asks for a clear, single sentence on the difference between requirements verification and requirements validation. Which statement is correct?
- Verification checks that requirements are well-formed and correct; validation checks that they deliver the right business value
- Verification checks that requirements are built into the product; validation checks the budget
- Verification and validation are different words for the same activity
- Verification confirms stakeholder authority; validation confirms the schedule
Correct answer: Verification checks that requirements are well-formed and correct; validation checks that they deliver the right business value
Verification checks that requirements are well-formed and correct (did we write them right), while validation checks that they deliver the right business value (did we write the right requirements). The two are distinct quality activities and are unrelated to budget, authority, or schedule.
A business analyst is asked to keep an approved set of requirements stable while still allowing controlled updates. What practice supports this?
- Baselining the requirements and managing changes through a defined change process
- Fast tracking the schedule
- Performing a Monte Carlo simulation
- Crashing the critical path
Correct answer: Baselining the requirements and managing changes through a defined change process
Baselining the approved requirements and routing later updates through a defined change process keeps requirements stable while still allowing controlled changes. Fast tracking, crashing, and Monte Carlo simulation address schedule compression and risk modeling, not requirements stability.
A business analyst must capture business rules that constrain how the organization operates, such as 'orders over a set amount require manager approval.' How are such statements best categorized?
- A risk response
- A procurement term
- Business rules within the requirements
- The project schedule
Correct answer: Business rules within the requirements
Statements that constrain how the organization operates, like requiring manager approval over a threshold, are business rules captured within the requirements. They define operating constraints the solution must honor and are not schedule items, risk responses, or procurement terms.
A team transitions from an old system to a new one and must temporarily migrate data and train users so operations can switch over. Requirements describing these one-time switchover needs are called:
- Nonfunctional requirements
- Business requirements
- Functional requirements
- Transition requirements
Correct answer: Transition requirements
Requirements describing the temporary capabilities needed to move from the current state to the future state, such as data migration and user training for cutover, are transition requirements. They are short-lived and distinct from functional, nonfunctional, and high-level business requirements.
A business analyst wants to elicit honest input from many geographically dispersed stakeholders while avoiding the influence of dominant voices. Which technique is most suitable?
- Direct observation of one site
- A single in-person workshop
- Prototyping with one user
- A survey or questionnaire
Correct answer: A survey or questionnaire
A survey or questionnaire reaches many dispersed stakeholders efficiently and allows independent, less-influenced responses than a group setting. A single workshop, observing one site, or prototyping with one user would not capture broad, independent input across a dispersed group.
A business analyst evaluating a proposed solution wants to confirm it aligns with the original business objectives before recommending deployment. Which activity does this represent?
- Procurement source selection
- Assessing solution alignment as part of solution evaluation
- Resource leveling
- Schedule crashing
Correct answer: Assessing solution alignment as part of solution evaluation
Confirming that a proposed solution aligns with the original business objectives before deployment is part of solution evaluation, which assesses value and fit. Resource leveling, schedule crashing, and source selection address resources, schedule, and vendor choice, not solution-to-objective alignment.
A stakeholder asks the business analyst to keep the requirements traceability matrix updated as the project changes. What benefit does maintaining traceability provide when a requirement changes?
- It automatically shortens the schedule
- It sets the project budget
- It removes the need for stakeholder approval of the change
- It shows which design, build, and test items are affected so the impact of the change can be assessed
Correct answer: It shows which design, build, and test items are affected so the impact of the change can be assessed
Maintaining traceability shows which design, build, and test items are linked to a changed requirement, enabling a clear impact assessment before acting. It does not shorten the schedule, replace stakeholder approval, or set the budget; its value is impact analysis and coverage assurance.
A project sponsor asks the team to explain what business analysis actually contributes to a project. Which statement BEST describes the role of business analysis in project management?
- It is the set of activities that elicits, analyzes, documents, and manages requirements so the solution delivers business value
- It is the quality-assurance function responsible for inspecting deliverables before handoff
- It is the financial control function that tracks earned value and forecasts the budget at completion
- It is the process of sequencing activities and building the project schedule network diagram
Correct answer: It is the set of activities that elicits, analyzes, documents, and manages requirements so the solution delivers business value
Business analysis is the set of activities that elicits, analyzes, documents, validates, and manages requirements so the resulting solution delivers business value. It connects stakeholder needs to the product the project builds, ensuring the team builds the right thing. Tracking earned value, scheduling, and inspecting deliverables are distinct project management or quality functions, not the core purpose of business analysis.
On a new project, a team member is unclear what the business analyst is responsible for versus the project manager. Which responsibility belongs to the business analyst?
- Approving change requests on behalf of the change control board
- Authorizing the project charter and committing organizational funding
- Assigning team members to activities and managing the project schedule
- Eliciting and analyzing stakeholder needs and translating them into clear, agreed requirements
Correct answer: Eliciting and analyzing stakeholder needs and translating them into clear, agreed requirements
The business analyst elicits and analyzes stakeholder needs and translates them into clear, agreed-upon requirements that guide the solution. Authorizing the charter and funding is the sponsor's role, approving changes is governed by change control, and scheduling and resource assignment belong to the project manager. The analyst is the bridge between stakeholders and the solution.
A business analyst is preparing to gather requirements for a new customer-portal solution. Which activity BEST defines requirements elicitation?
- Testing the finished solution against its acceptance criteria
- Storing approved requirements in a version-controlled repository for the project archive
- Drawing requirements from stakeholders and other sources through techniques such as interviews, workshops, and observation
- Formally obtaining sponsor sign-off that the requirements baseline is complete
Correct answer: Drawing requirements from stakeholders and other sources through techniques such as interviews, workshops, and observation
Requirements elicitation is the activity of drawing out requirements from stakeholders and other sources using techniques such as interviews, facilitated workshops, observation, surveys, and document analysis. It is about discovering needs, not storing, approving, or testing them. Archiving, sign-off, and acceptance testing happen at other points in the requirements life cycle.
A business analyst wants to gather requirements directly from a group of stakeholders quickly while resolving conflicting views in real time. Which elicitation technique is BEST suited to this goal?
- One-way distribution of a written survey
- Reviewing historical lessons-learned reports
- Document analysis of existing system manuals
- Facilitated requirements workshop
Correct answer: Facilitated requirements workshop
A facilitated requirements workshop brings stakeholders together so they can contribute, debate, and resolve conflicting views collaboratively and quickly. Document analysis and lessons-learned reviews draw from existing records rather than live stakeholder input, and a one-way survey lacks the real-time interaction needed to reconcile conflicts. Workshops are a core elicitation technique for building shared agreement fast.
A stakeholder asks the business analyst to clarify the difference between a business requirement and a functional requirement. Which statement is correct?
- A business requirement is written by developers, while a functional requirement is written by the sponsor
- A business requirement applies only to agile projects, while a functional requirement applies only to predictive projects
- A business requirement states a high-level need or goal of the organization, while a functional requirement describes a specific behavior the solution must perform
- A business requirement describes the technical environment, while a functional requirement describes the budget
Correct answer: A business requirement states a high-level need or goal of the organization, while a functional requirement describes a specific behavior the solution must perform
A business requirement states a high-level need, goal, or objective of the organization, while a functional requirement describes a specific behavior or function the solution must perform to meet that need. Business requirements answer why the project exists; functional requirements answer what the product must do. The other statements confuse requirement types with environment, budget, authorship, or delivery approach.
A business analyst organizes requirements from the broad organizational need down to specific solution behaviors. Which sequence reflects the correct requirements hierarchy?
- Stakeholder requirements lead to business requirements, which lead to solution requirements
- Functional requirements lead to business requirements, which lead to transition requirements
- Solution requirements lead to business requirements, which lead to stakeholder requirements
- Business requirements lead to stakeholder requirements, which lead to solution requirements (functional and non-functional)
Correct answer: Business requirements lead to stakeholder requirements, which lead to solution requirements (functional and non-functional)
Requirements flow from business requirements (the organization's high-level needs) to stakeholder requirements (the needs of specific stakeholder groups) to solution requirements, which are split into functional and non-functional. This top-down pyramid keeps every detailed requirement traceable back to a real business need. Reversing the order would mean building details before knowing why they are needed.
During analysis, a business analyst documents that the system 'must encrypt all data at rest and respond within two seconds under peak load.' How are these requirements BEST classified?
- Business requirements
- Non-functional requirements
- Stakeholder requirements
- Transition requirements
Correct answer: Non-functional requirements
Encryption standards and response-time limits are non-functional requirements because they describe qualities, constraints, and environmental conditions the solution must satisfy rather than a specific behavior it performs. Functional requirements describe what the system does; non-functional requirements describe how well it must do it (security, performance, reliability). Business and stakeholder requirements sit higher in the hierarchy and state needs, not technical qualities.
A team is moving from an old order-entry system to a new one and documents the temporary data conversion and user-training capabilities needed to switch over. How are these requirements classified?
- Transition requirements
- Functional requirements
- Non-functional requirements
- Business requirements
Correct answer: Transition requirements
Transition requirements describe the temporary capabilities (such as data conversion, parallel running, and user training) needed to move from the current state to the future state, and they are no longer needed once the change is complete. Functional and non-functional requirements describe the ongoing solution itself, and business requirements state the high-level organizational need. Transition requirements exist only to enable the changeover.
A business analyst must decide which of fifty competing requirements to deliver first within a fixed timebox. Which technique BEST helps prioritize the requirements?
- A work breakdown structure of project deliverables
- A network diagram showing the critical path
- A responsibility assignment matrix
- MoSCoW prioritization (Must have, Should have, Could have, Won't have)
Correct answer: MoSCoW prioritization (Must have, Should have, Could have, Won't have)
MoSCoW prioritization sorts requirements into Must have, Should have, Could have, and Won't have (this time), helping the team focus on the highest-value items within a fixed timebox. A work breakdown structure decomposes scope, a network diagram sequences activities, and a responsibility matrix assigns roles, none of which rank requirements by priority. MoSCoW is a core requirements-prioritization method.
A product team wants to prioritize the backlog by comparing how much value each item delivers against how much effort it takes. Which approach reflects this prioritization principle?
- Ranking items by relative business value versus the cost or effort to deliver them
- Ranking items by which team member proposed them
- Ranking items by the order in which stakeholders submitted them
- Ranking items alphabetically by feature name
Correct answer: Ranking items by relative business value versus the cost or effort to deliver them
Effective requirements prioritization ranks items by the business value they deliver weighed against the cost or effort to build them, so the team maximizes value delivered early. Alphabetical order, submission order, and proposer identity ignore value and effort entirely. Value-versus-effort thinking underlies methods like MoSCoW and value-based backlog ordering.
A stakeholder wants assurance that every requirement is being built and tested and can be traced back to a business need. Which tool provides this?
- A stakeholder register
- A risk register
- A requirements traceability matrix
- A Gantt chart
Correct answer: A requirements traceability matrix
A requirements traceability matrix links each requirement to its source (the business need) and forward to design, build, and test artifacts, providing assurance that nothing is lost and everything maps to a real need. A Gantt chart shows schedule, a stakeholder register lists people, and a risk register tracks threats and opportunities. Traceability is the matrix's distinctive purpose.
A business analyst explains that a particular document connects each requirement bidirectionally to its origin and to the deliverables that satisfy it. What is this document?
- Project charter
- Business case
- Lessons-learned register
- Requirements traceability matrix
Correct answer: Requirements traceability matrix
The requirements traceability matrix connects each requirement bidirectionally, tracing it backward to its origin (such as a business objective) and forward to the deliverables, test cases, and design that satisfy it. The business case justifies the project, the charter authorizes it, and the lessons-learned register captures knowledge, none of which provide requirement-to-deliverable traceability. The matrix is the dedicated traceability artifact.
An agile team captures a requirement as: 'As a returning customer, I want to save my payment method so that checkout is faster.' What kind of artifact is this?
- A work package
- A user story
- A non-functional requirement
- A risk statement
Correct answer: A user story
This is a user story, a short description of a feature told from the user's perspective using the format 'As a [role], I want [capability], so that [benefit].' It captures who needs something, what they need, and why. A non-functional requirement describes a quality constraint, a risk statement describes uncertainty, and a work package is a unit of schedulable work in a WBS.
A product owner is writing user stories and wants each one to be small, independent, and testable. Which set of conditions defines when a user story is complete?
- The cost baseline
- Acceptance criteria
- The communications plan
- The critical path
Correct answer: Acceptance criteria
Acceptance criteria are the conditions a user story must satisfy to be considered done and accepted by the customer, making the story testable and unambiguous. They turn the story's intent into verifiable pass/fail statements. The critical path, cost baseline, and communications plan address scheduling, budget, and information flow rather than defining when a story is complete.
On an agile project, a team member asks who is responsible for maximizing the value of the product and ordering the backlog. Which role holds this accountability?
- The scrum master
- The functional manager
- The product owner
- The project sponsor
Correct answer: The product owner
The product owner is accountable for maximizing the value of the product and for managing and ordering the product backlog so the team works on the highest-value items first. The scrum master serves the team and removes impediments, the sponsor funds and champions the effort, and the functional manager oversees resources. Backlog ownership and value maximization are uniquely the product owner's job.
A product owner is deciding how to spend a sprint. Which action is MOST consistent with the product owner's responsibilities?
- Approving timesheets and conducting performance reviews
- Reprioritizing the product backlog so the team builds the highest-value items next
- Estimating individual tasks and committing the team to a fixed scope
- Facilitating the daily standup and shielding the team from interruptions
Correct answer: Reprioritizing the product backlog so the team builds the highest-value items next
Reprioritizing the product backlog to ensure the team builds the highest-value items next is a core product owner responsibility, since the role owns backlog ordering and value delivery. Task estimation and commitment belong to the development team, facilitating standups and removing impediments belong to the scrum master, and administrative HR duties belong to managers. The product owner focuses on what and why, not how.
A stakeholder asks the product owner for a high-level visual of the product's planned direction, major features, and the sequence of releases over time. What artifact answers this need?
- A responsibility assignment matrix
- A burndown chart
- A product roadmap
- A product backlog
Correct answer: A product roadmap
A product roadmap is a high-level, time-oriented visual showing the product's direction, major features or themes, and the planned sequence of releases over time. The product backlog is the detailed, ordered list of work; a burndown chart tracks remaining work within an iteration; and a responsibility matrix assigns roles. The roadmap communicates strategy and intent, not granular tasks.
A team wants to distinguish the product roadmap from the product backlog. Which statement is accurate?
- The roadmap is used only in predictive projects, while the backlog is used only in agile projects
- The roadmap shows the strategic direction and release sequence, while the backlog is the detailed, prioritized list of work items
- The roadmap is owned by developers, while the backlog is owned by the sponsor
- The roadmap lists individual user stories, while the backlog shows quarterly themes
Correct answer: The roadmap shows the strategic direction and release sequence, while the backlog is the detailed, prioritized list of work items
The product roadmap conveys strategic direction and the planned sequence of releases over time, while the product backlog is the detailed, prioritized list of features, stories, and other work items the team will deliver. The roadmap is the high-level 'where we're going'; the backlog is the actionable 'what we'll build next.' Both are typically owned by the product owner.
After a solution has been delivered, the organization wants to determine whether it actually meets the business need and delivers the expected value. Which business analysis activity addresses this?
- Requirements elicitation
- Backlog refinement
- Solution evaluation
- Stakeholder identification
Correct answer: Solution evaluation
Solution evaluation assesses how well a delivered solution meets the business need and the value it actually delivers, identifying gaps and recommending improvements or further investment. Elicitation gathers requirements before building, backlog refinement clarifies upcoming work, and stakeholder identification finds affected parties. Evaluation is the activity focused on realized value after delivery.
A business analyst measures a newly launched solution against its objectives and finds it delivers only part of the intended value. Within business analysis, what is the PRIMARY purpose of this assessment?
- To authorize the next phase by signing the project charter
- To determine whether the solution is delivering business value and what adjustments are needed
- To calculate the schedule performance index for the remaining work
- To assign accountability for the project's individual deliverables
Correct answer: To determine whether the solution is delivering business value and what adjustments are needed
The primary purpose of solution evaluation is to determine whether the solution is delivering the intended business value and what adjustments, enhancements, or decisions (continue, replace, retire) are needed. It is value-focused, not schedule-, accountability-, or authorization-focused. Calculating SPI, assigning deliverable ownership, and signing charters belong to other processes.
A business analyst defines the ongoing activities of planning, tracing, prioritizing, approving, and maintaining requirements throughout the project. What is this collective effort called?
- Schedule management
- Procurement management
- Risk management
- Requirements management
Correct answer: Requirements management
Requirements management is the ongoing effort of planning, tracing, prioritizing, approving, communicating, and maintaining requirements (including handling changes to them) throughout the project life cycle. It keeps requirements current and traceable as the project evolves. Risk, procurement, and schedule management address uncertainty, contracts, and timing rather than requirements.
A team is choosing among several structured methods for performing business analysis on a new initiative. What is the BEST description of a business analysis framework?
- A fixed contract template used to procure external vendors
- A structured set of practices, techniques, and knowledge areas that guide how business analysis is performed
- A staffing chart showing the project's reporting relationships
- A financial model used to forecast project cash flow
Correct answer: A structured set of practices, techniques, and knowledge areas that guide how business analysis is performed
A business analysis framework is a structured set of practices, techniques, and knowledge areas (such as needs assessment, elicitation, analysis, traceability, and solution evaluation) that guide how business analysis work is performed consistently. It provides the methods and vocabulary analysts use to deliver value-aligned requirements. Contract templates, cash-flow models, and staffing charts serve procurement, finance, and organization rather than guiding analysis itself.

To find us again, just search “Career Employer CAPM”

By Career EmployerUpdated Jun 7, 2026

CAPM Question of the DayNew daily

1 of 330+ free questions — a new one every day

In the context of project management, 'scope creep' refers to:

Pick an answer to see the explanation

Click Start Test above to launch a full-length CAPM practice test weighted exactly like the real exam, or drill a single domain — Project Management Fundamentals & Core Concepts, Predictive Plan-Based Methodologies, Agile Frameworks/Methodologies, or Business Analysis Frameworks. Every question includes a clear explanation so you learn the reasoning, not just the answer.

The CAPM — officially the Certified Associate in Project Management — is the entry-level project management certification from the Project Management Institute (PMI), administered through Pearson VUE at test centers and via online proctoring.^[2] These free CAPM practice questions and test prep mirror the current Examination Content Outline (ECO) so you practice the way the real exam is built.^[1] To reinforce each domain, pair these with our free study guide, flashcards.

CAPM at a Glance

CAPM Exam at a glance
Detail	CAPM Exam
Questions	150 (135 scored + 15 unscored pretest)
Question type	Multiple choice, drag-and-drop, and animations/comic strips
Time limit	3 hours (180 minutes)
Result	Pass / Fail (no scaled score reported)
Administered by	Pearson VUE (test center or online proctoring)
Eligibility	Secondary degree (high school diploma, associate degree, or global equivalent) + 23 contact hours of project management education
Cost	$225 PMI members /$ 300 non-members
Recertification	15 PDUs every 3-year CCR cycle

What Is on the CAPM Exam?

The CAPM exam covers four domains: Project Management Fundamentals & Core Concepts (36%), Business Analysis Frameworks (27%), Agile Frameworks/Methodologies (20%), and Predictive, Plan-Based Methodologies (17%), per PMI’s Examination Content Outline (ECO).^[1]

Project Management Fundamentals is the largest domain, but Business Analysis and Agile together account for nearly half the exam. Our full practice test is weighted to match:

CAPM weighting by domain (current ECO)

Project Management Fundamentals & Core Concepts36% · ≈54 Qs

Business Analysis Frameworks27% · ≈41 Qs

Agile Frameworks/Methodologies20% · ≈30 Qs

Predictive, Plan-Based Methodologies17% · ≈25 Qs

Practice Questions by Domain

Use Start Test for a full weighted CAPM simulation, or open the hub and pick a single domain to drill your weak area. After each full exam, your results show a per-domain breakdown so you know exactly where to focus — most candidates need the most reps on the Business Analysis and Agile domains.

What Are the Requirements to Take the CAPM?

To take the CAPM exam, you need a secondary degree — a high school diploma, an associate degree, or the global equivalent — plus 23 contact hours of project management education completed by the time you take the exam.^[3] The 23 hours are commonly satisfied by PMI’s own Project Management Basics course or any equivalent qualifying course. Unlike the PMP, the CAPM requires no prior work experience leading projects.

How Do You Register for the CAPM Exam?

You register for the CAPM exam at pmi.org by submitting an application documenting your secondary degree and 23 contact hours of project management education.^[3] After PMI reviews and accepts the application (and you pay the exam fee of $225 for members or $300 for non-members), you receive a 1-year eligibility window in which you may take the exam up to three times. Schedule and sit the exam through Pearson VUE at a test center or via online proctoring.

What Is the Passing Score for the CAPM?

There is no numeric passing score for the CAPM — PMI reports the exam as pass or fail and does not publish a percentage cutoff.^[2] Of the 150 questions, only 135 are scored; 15 are unscored pretest items used to validate future questions.

Your result is determined by a psychometric analysis of performance across the scored questions against PMI’s established standard, with proficiency feedback (Above Target, Target, Below Target, Needs Improvement) provided by domain.

How Hard Is the CAPM? (Pass Rate)

PMI does not publish an official CAPM pass rate. The exam is criterion-referenced, so results reflect mastery against a fixed standard rather than a curve.^[2]

The current version is broader than many candidates expect: it spans predictive (plan-based), agile, and business analysis frameworks, with Business Analysis alone at 27%. The toughest areas tend to be the agile and business analysis domains for candidates from a traditional waterfall background.

135

Scored questions

of 150 total

180 min

Exam time limit

3-hour appointment

36%

Fundamentals domain

largest section

The takeaway: drill until you’re consistently scoring above target on full-length practice — especially Business Analysis and Agile — before you book your exam date.

What to Expect on Exam Day

Arrive at your Pearson VUE test center at least 15 minutes early to check in — bring a valid, unexpired government-issued photo ID whose name matches your PMI application.^[3]

You’ll store phones and personal items in a locker; no notes are allowed, but you’re given an erasable note board and an on-screen calculator. A short tutorial precedes the exam, then you have 3 hours to answer 150 questions delivered as multiple choice, drag-and-drop, and animations/comic strips.

If you test via online proctoring, expect a similar room and ID scan. PMI processes your results, with pass/fail status typically shown at the test center and the official report posted to your account afterward. Having simulated the full timing with practice tests makes that clock feel routine.

How to Use This CAPM Practice Test

Recreate exam conditions. Take the full test timed, with no notes.^[1]
Diagnose, then drill. Use a full CAPM simulation to find weak domains, then drill them.
Prioritize Business Analysis + Agile. They’re the biggest score-movers.
Learn the why. Read every explanation — understanding beats memorizing.
Answer everything. There’s no guessing penalty, so never leave a question blank.

Why Get CAPM Certified?

The CAPM is the most widely recognized entry-level project management credential, often required (or strongly preferred) by employers and a strong stepping stone toward the PMP.^[2] These free CAPM practice tests are the most efficient way to get there.

Conclusion

Passing the CAPM comes down to broad coverage across project management fundamentals, predictive and agile methodologies, and business analysis. Use this free CAPM practice test to find your weak domains, drill them to mastery, and pair it with our free study guide, flashcards to walk in confident on test day.

CAPM Practice Test FAQ

The CAPM has 150 questions (135 scored plus 15 unscored pretest items) delivered as multiple choice, drag-and-drop, and animations/comic strips. You have 3 hours (180 minutes) to complete it.

References

1.PMI. “Certified Associate in Project Management (CAPM) Examination Content Outline.” pmi.org. ↑
2.PMI. “CAPM Certification — Certified Associate in Project Management.” pmi.org. ↑
3.PMI. “CAPM Handbook (Eligibility, Application, and Exam Policies).” pmi.org. ↑
4.PMI. “Continuing Certification Requirements (CCR) Handbook.” pmi.org. ↑
5.PMI. “How to Maintain Your PMI Certification.” pmi.org. ↑

Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

All Posts

Career Employer’s Editorial Process

Here at Career Employer, we focus a lot on providing factually accurate information that is always up to date. We strive to provide correct information using strict editorial processes, article editing, and fact-checking for all of the information found on our website. We only utilize trustworthy and relevant resources. To find out more, make sure to read our full editorial process page here.