Try 150 free CAPM questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length CAPM practice exam includes 150 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 150-question full-length practice format for CAPM preparation. Always confirm final exam-day timing, appointment rules, and candidate instructions directly with PMI before your scheduled exam.
Set a 180-minute timer and answer the 150 questions before reading explanations. Track misses by content area: project fundamentals, predictive planning, agile/adaptive delivery, or business analysis.
Use this page as a diagnostic run, not as the only measure of readiness. The most useful result is not just the percentage score; it is the pattern behind the misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your broad readiness may be close. Review explanations, confirm timing, and avoid over-repeating recognized items. | |
| Strong score but repeated misses in one content area | The total score may hide a domain weakness. Drill that content area before another full-length run. | |
| Many fundamentals misses | Review project roles, life cycles, governance, stakeholders, risk, quality, and core terminology. | |
| Many predictive misses | Focus on scope, schedule, cost, change control, baselines, quality, and communication planning. | |
| Many agile or business-analysis misses | Review backlog refinement, stakeholder needs, requirements, acceptance criteria, and iterative delivery decisions. |
Use this worksheet immediately after the run, before you read too many explanations.
| Field | Record |
|---|---|
| Overall score | ___ / 150 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss content area | Fundamentals / Predictive / Agile / Business Analysis |
| Most expensive mistake type | Misread prompt / confused artifact / wrong delivery approach / ignored stakeholder need / missed acceptance signal / other: ___ |
| Next focused page | Fundamentals / Predictive / Agile / Business Analysis / another full mixed set |
For concept review before or after this set, use the CAPM guide on PMExams.com.
This static page is useful for one full diagnostic pass. PM Mastery is the better place for repeated practice because it gives you varied attempts and progress history instead of one page you can memorize.
| Need after this diagnostic | Use PM Mastery for… |
|---|---|
| New mixed attempts | Timed mocks and mixed sets that reduce answer-recognition bias. |
| Content-area repair | Focused fundamentals, predictive, agile, and business-analysis drills. |
| Explanation review | Item-level explanations that help you classify mistake patterns. |
| Progress tracking | A single web/mobile account with practice history across sessions. |
| Final readiness checks | Varied timed attempts after weak areas have been repaired. |
For the cleanest diagnostic result, answer the questions under timed conditions before reading the explanations.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-50 | 60 minutes | Build a steady rhythm and mark uncertain foundational items. |
| Questions 51-100 | 120 minutes cumulative | Watch for switching costs between predictive, agile, and business-analysis decisions. |
| Questions 101-150 | 180 minutes cumulative | Finish with enough time to resolve marked items deliberately. |
If you retake this free diagnostic, treat the second attempt as a reasoning check, not as a fresh score. Some stems and answers will be familiar, so the percentage can overstate readiness.
For readiness decisions, give more weight to varied timed attempts in PM Mastery than to repeating one static page. Use this page to diagnose; use the app to build durable speed, coverage, and mixed CAPM judgment.
| Item | Detail |
|---|---|
| Issuer | PMI |
| Exam route | CAPM |
| Official exam name | PMI Certified Associate in Project Management (CAPM) |
| Full-length set on this page | 150 questions |
| Exam time | 180 minutes |
| Topic areas represented | 4 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Project Management Fundamentals and Core Concepts | 36% | 54 |
| Predictive, Plan-Based Methodologies | 17% | 26 |
| Agile Frameworks/Methodologies | 20% | 30 |
| Business Analysis Frameworks | 27% | 40 |
Topic: Business Analysis Frameworks
A business analyst is supporting a hybrid project delivering a new customer self-service portal. The project manager asks whether the next increment is ready to be delivered to operations.
You have access to the requirements traceability matrix (RTM) for the release scope and the product backlog with item statuses.
Which TWO actions best determine whether the increment is ready for delivery? (Select TWO)
Correct answers: D, F
What this tests: Business Analysis Frameworks
Explanation: Delivery readiness is evidenced by completion and acceptance of the release scope. The RTM provides requirement-to-solution-to-verification traceability, while the product backlog shows whether the release items meet acceptance criteria and are in a Done/Accepted state. Using these two artifacts directly supports an objective go/no-go decision for the increment.
To determine whether an increment is ready for delivery, focus on objective evidence that the agreed release scope is complete and accepted. The RTM supports this by showing that each release requirement is traced to a delivered component and to verification/validation results (for example, test execution and business acceptance). The product backlog supports this by showing that the items planned for the release are in a completed state (such as Done/Accepted) and meet their acceptance criteria and the team’s definition of done.
If either artifact shows missing traceability, incomplete verification, or unaccepted backlog items, the increment is not ready to deliver—even if stakeholders are eager to proceed.
An increment is ready only when release-scope requirements are implemented, verified, and accepted as shown in the RTM.
Backlog status plus acceptance criteria/DoD evidence shows whether the intended scope for the increment is complete.
Topic: Business Analysis Frameworks
A company is launching a hybrid project to replace a legacy customer service portal. The sponsor says, “We can’t afford to build features that don’t deliver value.”
As the project’s business analysis support, which TWO actions best demonstrate how business analysis supports value delivery on this project? (Select TWO)
Correct answers: A, B
What this tests: Business Analysis Frameworks
Explanation: Business analysis is the work of identifying needs and recommending solutions that deliver value to stakeholders. On this project, value delivery is strengthened by clarifying what stakeholders truly need, prioritizing it by business value, and ensuring the delivered features can be validated against defined criteria with end-to-end traceability.
Business analysis supports value delivery by bridging business needs and solution delivery: it helps stakeholders articulate the problem/opportunity, defines and refines requirements, and provides mechanisms to confirm the solution actually meets those requirements. In a hybrid portal replacement, a BA increases value by ensuring the team builds the right things (prioritized requirements tied to objectives) and builds them right (requirements can be validated through acceptance criteria and traced from origin to delivered outcomes). Practical BA outputs often include refined and prioritized requirements (or user stories), acceptance criteria, and a requirements traceability approach so changes and testing stay aligned to stakeholder needs. The key takeaway is that BA work targets solution value and fitness for use, not project authorization, budgeting, or schedule ownership.
Business analysis focuses on understanding stakeholder needs and translating them into prioritized requirements that drive value.
Traceability and clear acceptance criteria help verify the delivered solution meets requirements and intended benefits.
Topic: Agile Frameworks/Methodologies
A Scrum team is preparing to start a sprint. During backlog refinement, a user story says: “As a customer, I want to save items for later so I can purchase them in a future visit.” Team members disagree on what features are included (e.g., where the list appears, limits, and what happens when an item is out of stock).
Which TWO actions best use acceptance criteria to clarify what “done” means for this backlog item? (Select TWO.)
Correct answers: E, F
What this tests: Agile Frameworks/Methodologies
Explanation: Acceptance criteria describe the specific, testable conditions that must be true for a backlog item to be accepted. By writing them clearly and confirming shared understanding with the product owner before starting, the team aligns on scope and expected behavior. This clarifies what “done” means for that item beyond the generic Definition of Done.
Acceptance criteria are item-specific, observable conditions of satisfaction that clarify the expected behavior and boundaries of a backlog item (for example, what is included/excluded and how it will be validated). In the scenario, ambiguity exists about where the saved list appears, limits, and edge cases, so the team should capture those expectations as testable statements and align on them before sprint execution.
Good acceptance criteria are typically:
A key distinction is that acceptance criteria define “done for this item,” while the Definition of Done defines “done for all items” (quality/process standards).
Acceptance criteria define objective, verifiable conditions that must be met for the item to be accepted as done.
Agreement on acceptance criteria up front creates a shared understanding of “done” and reduces rework during the sprint.
Topic: Predictive, Plan-Based Methodologies
A company is running a predictive project with an approved scope and schedule baseline. Halfway through planning, leadership announces a reorganization from a projectized structure (dedicated, full-time project team reporting to the project manager) to a functional structure where team members report back to their department managers.
What is the most likely near-term impact on the project manager’s ability to execute the plan?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: Changing from a projectized to a functional structure reduces the project manager’s authority over people and work assignments. In the near term, this most directly affects how planned work is staffed and prioritized. The project manager will need to coordinate and negotiate with functional managers to secure resources needed to meet the schedule baseline.
Organizational structure influences how predictive projects are staffed and controlled because it determines the project manager’s authority and the availability of resources. In a projectized organization, resources are typically dedicated to the project and report to the project manager, enabling faster assignments and decisions aligned to the plan. When the organization shifts to a functional structure, team members report to functional managers, and the project manager’s authority over staffing and day-to-day priorities is reduced.
Near-term, this usually shows up as:
The most immediate consequence is resource negotiation rather than an automatic improvement in control or elimination of change.
In a functional structure, the project manager typically has less authority and must coordinate resource assignment through functional managers.
Topic: Business Analysis Frameworks
A hybrid project team is building an internal dashboard. The business sponsor tells the business analyst, “We need the dashboard to show customer churn monthly,” while a developer says, “We can calculate churn using the event timestamp.” In a recent demo, business stakeholders expected churn by billing month, but the technical team reported it by calendar month, causing conflicting results.
Before the team changes any requirements or starts rework, what should the business analyst verify FIRST to prevent further misinterpretation between business and technical teams?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: The immediate issue is that “monthly churn” is being interpreted differently by business and technical team members. The first step is to clarify and document the operational definition (e.g., billing month vs calendar month and which timestamps drive the calculation). Once the definition is agreed, requirements, acceptance criteria, and implementation can be aligned to it.
When business and technical teams disagree on results, the most efficient way to prevent ongoing misinterpretation is to clarify the meaning of the term that drives the calculation and decisions. Here, “monthly churn” can legitimately be computed using different time boundaries (billing month vs calendar month) and different date fields (billing period, invoice date, event timestamp). The business analyst should first facilitate agreement on a single operational definition and capture it in requirements and acceptance criteria so both the report logic and stakeholder expectations match.
A practical approach is to confirm:
Other actions may be useful later, but they do not resolve the ambiguity that is currently causing conflicting interpretations.
A shared definition aligns business intent and technical implementation and is the root cause of the mismatch described.
Topic: Project Management Fundamentals and Core Concepts
You are a project coordinator preparing the weekly status report for a predictive project. The sponsor privately asks you to “keep it green” until next month’s steering committee.
Exhibit: Draft weekly status excerpt
Week ending: March 1
Schedule status: Green
Milestone M2 (prototype demo): Planned Feb 28 / Actual Not completed
Issue log ISS-17: Test environment unstable; demo delayed ~2 weeks
Customer update planned: March 3 (per communications plan)
What is the most ethical and professional next action?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Ethics and professionalism in stakeholder communication require honesty, accuracy, and transparency in reporting project status. The exhibit shows a missed milestone and an open issue driving a likely two-week delay, so reporting “Green” would be misleading. The appropriate action is to correct the status and communicate the impact through the agreed communications approach.
Professional project reporting means providing truthful, complete, and timely information so stakeholders can make informed decisions. In the exhibit, the milestone is not completed and an issue is already logged with an estimated two-week delay, which contradicts a “Green” schedule status. The ethical response is to align the status report with the facts, ensure the issue and its impacts are visible, and follow the communications plan for the planned customer update.
Misrepresenting status or hiding known issues undermines trust and can cause harm by delaying corrective action; if pressured, raise the concern through appropriate project leadership channels rather than altering facts.
Ethical reporting requires accurate, timely status and transparent communication using the agreed channels.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project delivers a new customer self-service portal. The team has released all planned features on schedule, but three months after launch the call center volume and handling time have not decreased. The business sponsor says the project “delivered outputs, not value.” When asked how features were selected, the project team explains they prioritized stakeholder requests but did not document expected benefits, success measures, or how deliverables would drive those outcomes.
What is the most likely underlying cause of the problem?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The symptoms show successful delivery of features, but no measurable business improvement. That gap typically occurs when benefits were not planned: intended outcomes, metrics, and the logic connecting deliverables to those outcomes were never defined or managed. Benefit planning makes “value” explicit and allows the team to validate that planned deliverables actually enable the desired business results.
Benefit planning clarifies what value the project is expected to create and how project deliverables will enable that value. In the scenario, the team optimized for requested features (outputs) but did not define the target outcomes (e.g., reduced call volume) or how each deliverable contributes to those outcomes, so success can’t be designed for or validated.
A practical benefit-planning approach is to:
When deliverables are not explicitly tied to intended outcomes and measures, the project can be “on time/on scope” while still failing to deliver value.
Without defined benefits and measures tied to deliverables, the project can deliver features that do not realize intended value.
Topic: Project Management Fundamentals and Core Concepts
A project is starting in a matrix organization, and several stakeholders are unclear about what the project sponsor does versus what the project team does.
Which TWO actions are typically the responsibility of the project sponsor (rather than the project team)? (Select TWO)
Correct answers: A, C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The project sponsor is the senior role that authorizes the project and provides organizational support. This includes approving the charter (and funding) and removing major organizational obstacles the team cannot address. The project team focuses on planning and executing the work to produce the deliverables.
Project sponsors and project teams have different accountability levels. In the scenario, sponsor responsibilities are governance and organizational enablement: they authorize the project to begin (commonly by approving the charter and funding) and use their authority to resolve escalated, cross-functional issues that exceed the team’s control.
The project team’s responsibilities are delivery-focused, such as:
A practical way to contrast the roles is: sponsors “enable and authorize,” while teams “plan and build” within the approved direction.
The sponsor provides organizational authorization and commits funding by approving the charter.
The sponsor uses organizational influence to remove high-level impediments the team cannot resolve.
Topic: Project Management Fundamentals and Core Concepts
You are developing the schedule management plan for a predictive project with fixed reporting dates to the sponsor. The team asks what this plan is used for before building the detailed project schedule.
Which TWO statements best describe the purpose of the schedule management plan and how it guides schedule development and control? (Select TWO)
Correct answers: B, C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The schedule management plan is a component of the project management plan that defines how the schedule will be developed, monitored, and controlled. It provides the rules, standards, and processes (such as methodology, reporting, thresholds, and change control) that guide building the schedule and managing variance against the schedule baseline.
The schedule management plan sets expectations and decision rules for schedule work across the project. Before the team creates the detailed schedule, this plan defines the scheduling approach (for example, scheduling method and tool, units of measure, level of accuracy, and reporting formats) so the schedule is built consistently. It also defines how schedule performance will be controlled (for example, variance thresholds, status and forecasting cadence, and how changes to the schedule baseline are reviewed and approved via integrated change control).
Key takeaway: the plan describes the “how” of scheduling and control; the detailed schedule contains the specific activities and dates.
A schedule management plan establishes the standards and approach the team will use to create and communicate the schedule.
It explains how schedule performance is monitored and how the schedule baseline will be controlled through change control.
Topic: Business Analysis Frameworks
You are gathering requirements for a hybrid project to improve a handheld picking app used by about 300 warehouse associates across 8 warehouses in three time zones. Associates work rotating shifts and cannot leave the floor for long meetings. The sponsor needs input within two weeks and wants both (1) an accurate picture of the real picking workflow and pain points and (2) feedback from a broad set of users across locations.
Which TWO elicitation techniques are most appropriate?
Correct answers: B, C
What this tests: Business Analysis Frameworks
Explanation: Observation is best for understanding how work is actually performed on the warehouse floor, including exceptions and workarounds. A survey is well-suited to rapidly reach a large, distributed user base across sites and shifts and to standardize how feedback is collected within the two-week constraint.
Elicitation technique selection depends on what you need to learn and the constraints on access to stakeholders. In this scenario, you need both an accurate view of real operational work and broad input from many users who have limited availability.
Interviews and workshops can be valuable for deep exploration and alignment, but they become impractical when stakeholder availability is highly constrained and the population is large.
Observation captures the real workflow and workarounds in the actual environment with minimal disruption.
A survey quickly gathers consistent feedback from many distributed users within a short time window.
Topic: Business Analysis Frameworks
During UAT planning for a new online returns feature, the business analyst documents end-to-end test scenarios and the specific outcomes that must be observed (including pass/fail conditions) for the business to accept the feature. What is this information called?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: The described UAT planning content is acceptance criteria: the explicit conditions and expected results used to determine whether a feature is acceptable to the business. By stating pass/fail outcomes for scenarios, the team creates a clear basis for user acceptance decisions. This supports consistent validation during UAT.
Acceptance criteria are the measurable conditions a deliverable must satisfy to be accepted by stakeholders. In UAT planning, they are often written alongside scenarios to state the expected results (what must happen for the test to pass) so users can objectively confirm the solution meets the requirement. This reduces ambiguity, aligns expectations, and provides a clear standard for accepting or rejecting the delivered feature. An RTM, by contrast, is used to map requirements to design, tests, and deliverables to ensure coverage, not to define pass/fail outcomes.
Acceptance criteria define the expected results and conditions that must be met for stakeholders to accept the deliverable.
Topic: Project Management Fundamentals and Core Concepts
A project coordinator is supporting a project manager on a hybrid project that has recently missed a milestone. The team is frustrated by unclear priorities, and stakeholders are asking for tighter control of dates and deliverables.
Which TWO actions best show when leadership and management are each needed?
Correct answers: B, E
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Leadership focuses on people and direction—creating alignment, trust, and commitment when the team is disengaged or unclear on purpose. Management focuses on process and control—updating plans and coordinating changes to meet agreed objectives. In this scenario, both are needed: re-align the team and restore delivery predictability through controlled planning updates.
Leadership and management are complementary. Leadership is most needed when the challenge is about people: morale, conflict, lack of clarity, or willingness to follow a direction. It emphasizes vision, alignment, and empowerment so the team can perform.
Management is most needed when the challenge is about execution control: coordinating work, updating plans, maintaining baselines, and ensuring changes are evaluated and approved before commitments are made.
Here, team frustration and unclear priorities call for a leadership action to re-establish shared goals and engagement, while stakeholder pressure for predictability calls for a management action to update plans only through approved change control. The key takeaway is matching the approach to whether the problem is primarily people/alignment or process/control.
This is leadership: creating clarity and motivation so people commit to the work.
This is management: maintaining control through planning, baselines, and formal change control.
Topic: Business Analysis Frameworks
A hybrid project is delivering a new customer portal. In a review meeting, stakeholders agree the next release must include the feature “Self-service account access.” The business analyst documents the requirement “Users can reset their password,” but in UAT stakeholders still dispute whether the delivered screen is “done.”
Which artifact/content should the business analyst add next to best communicate what will be accepted?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: The dispute is about what “done” means in UAT, so the missing information is the specific, testable conditions for acceptance. Features describe a broad capability, and requirements describe what the solution must do. Acceptance criteria make the requirement verifiable by stating the conditions the stakeholders will use to accept the result.
Features, requirements, and acceptance criteria operate at different levels of detail. A feature is a high-level product capability (useful for roadmaps and stakeholder alignment). A requirement states a needed condition or capability the solution must satisfy (useful for defining what must be built). Acceptance criteria are the specific, testable conditions that must be met for the requirement to be accepted (useful for UAT and reducing “done” ambiguity).
In this scenario, the feature and requirement already exist, but stakeholders still argue during UAT, which signals missing acceptance criteria. Adding clear acceptance criteria (often attached to a user story or requirement) aligns expectations and enables objective verification.
Acceptance criteria define the measurable conditions used to verify and accept the delivered requirement.
Topic: Business Analysis Frameworks
During user acceptance testing for a new internal expense app, users find a gap: submitted claims can be edited after approval, which violates the agreed acceptance criteria that approved claims must be locked.
As the project’s business analyst, which action SHOULD AVOID when deciding next steps for this validation defect?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: When a defect or gap is found during validation, the next steps focus on documenting it, assessing impact, and getting the right stakeholders to decide how to address it. Altering the validation approach to make the current product “pass” undermines acceptance criteria and can lead to incorrect sign-off and downstream rework.
Validation checks whether the delivered product meets agreed requirements and acceptance criteria. If a defect or gap is discovered (for example, approved claims are not locked), the appropriate response is to capture it, assess impacts (scope, risk, schedule), and route it through the team’s decision mechanism (change control in predictive/hybrid, or backlog refinement/prioritization in agile). Requirements documentation and traceability (such as an RTM) should be updated to reflect the decision and ensure the item is tracked to implementation and retest.
Key takeaway: manage the gap with transparency and stakeholder decisions, not by redefining tests to match an incorrect build.
Changing validation criteria to fit the product masks the defect instead of managing the gap through analysis and stakeholder decision-making.
Topic: Project Management Fundamentals and Core Concepts
You are starting a small hybrid project to implement a new customer support platform. The sponsor wants a selection that is transparent and auditable. Constraints: go-live in 8 weeks, implementation budget capped at $60,000, and the platform must integrate with the existing CRM.
Three vendor solutions are short-listed. As the project practitioner, what is the BEST next action to select among the alternatives?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A weighted decision matrix is designed to compare multiple alternatives using agreed evaluation criteria and weights. It produces a documented, repeatable rationale that supports an auditable selection. This fits the need for transparency while ensuring constraints like schedule, budget, and CRM integration are explicitly considered.
A decision matrix (weighted scoring model) helps a team select among alternatives by translating selection needs into criteria, assigning relative importance, and scoring each option consistently. In this scenario, the sponsor requires a transparent and auditable decision, and the project has clear constraints (8-week go-live, $60,000 cap, CRM integration).
A practical approach is:
This provides an objective comparison and a clear decision record versus choosing based on a single factor or personal preference.
A weighted scoring model compares options against agreed criteria and constraints in a transparent, defensible way.
Topic: Project Management Fundamentals and Core Concepts
A project team is planning a hybrid project to implement a new customer portal. The product owner maintains a prioritized list of features, and requirements are still being refined, but the sponsor asks the project manager for a stable schedule and cost forecast.
In planning meetings, the project manager builds the WBS by listing features as work packages and says, “Any time the feature list changes, the project scope changes, so we must re-plan the whole project.” The team already has a change control approach for approved changes.
What is the most likely underlying cause of the planning instability?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Product scope describes the features and functions of the product, while project scope describes the work required to deliver the product. In the scenario, the WBS is built from features and the project is repeatedly re-planned whenever the feature list evolves. This indicates a scope-type mix-up that directly destabilizes planning.
Product scope is the set of product features, functions, and characteristics (often expressed as requirements, user stories, or a product backlog). Project scope is the work the project team will perform to deliver the agreed product outcomes (often expressed through a scope statement, WBS, and work packages).
In this scenario, the project manager uses features as WBS work packages and assumes that any refinement or reprioritization of features automatically means the project scope has changed. That confuses what is being built (product scope) with how the team will build and deliver it (project scope). The fix is to define project scope as deliverable-oriented work (with appropriate planning levels for a hybrid approach) while managing product scope evolution through requirements/backlog refinement and formal change control when changes affect approved baselines.
Using features as work packages blurs product scope and project scope, making planning unstable as requirements evolve.
Topic: Project Management Fundamentals and Core Concepts
On a hybrid project, the sponsor says they are “always surprised” by schedule slippage, and the steering committee complains that different people are quoting different status numbers. The project manager insists they have been “communicating constantly” by emailing a detailed status report to everyone.
Excerpt from the communications management plan:
This week, the portal still shows a dashboard from three weeks ago, and a critical risk was added to the risk register but not mentioned until the meeting.
What is the most likely underlying cause of the communication problem?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The communications management plan already defines who needs what information, in which format, and through which channel. The symptoms (outdated portal dashboard and uncommunicated urgent risk) indicate the project manager is bypassing the agreed mechanisms and using a one-size-fits-all email instead.
A communications management plan is used to deliver the right message to the right audience using the agreed channel, format, and timing (push, pull, interactive). In this scenario, the plan calls for a 1-page executive dashboard posted to the portal before steering meetings, daily team coordination via chat/task board, and urgent risks/issues via a direct call followed by notification through the agreed channel. The portal is outdated and an urgent risk was not escalated as specified, which points to noncompliance with the plan—not simply “too much email.”
The key diagnostic clue is the mismatch between the plan’s required channels/formats and what was actually used.
The plan specifies different channels/formats by audience, but updates and urgent items are not being communicated that way.
Topic: Business Analysis Frameworks
A project is using an agile approach for product development. During release planning, the product owner decides to move a “Self-service password reset” feature to a later release due to low value compared to higher-risk security work. Several stakeholders ask the business analyst to explain the new priority order and the reason behind it.
Which action should the business analyst AVOID?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: Prioritization decisions in agile are communicated through shared, living artifacts so stakeholders can see the current order and the rationale. Relying only on verbal communication creates ambiguity and quickly becomes outdated. Updating the backlog and related planning artifacts supports transparency and consistent understanding.
In agile and hybrid environments, prioritization is expected to be transparent, frequently updated, and communicated through information radiators and planning artifacts. The primary artifact for priority is the product backlog (order reflects priority), often complemented by a product roadmap/release plan to show timing. When stakeholders ask “why,” the rationale should be captured where people can reliably find it, such as brief notes on backlog items and/or a decision log tied to the items.
If a prioritization change is only communicated verbally and not reflected in shared artifacts, different stakeholder groups may act on different versions of the priority, and the reasoning is lost for future trade-off discussions. The key takeaway is to communicate priority and rationale using accessible artifacts that match the delivery approach.
It communicates a prioritization decision without capturing it in an appropriate, visible artifact stakeholders can refer to later.
Topic: Project Management Fundamentals and Core Concepts
A project sponsor asks the project coordinator to change the weekly status report from “amber” to “green” because the steering committee is sensitive to negative updates. The latest data shows a vendor delay will likely push a key milestone by two weeks, and the impact analysis is documented.
Which response best reflects ethical and professional stakeholder communication and reporting?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Ethical and professional reporting emphasizes honesty, accuracy, and transparency, even when the message is unfavorable. Since documented data indicates a likely schedule slip, the most appropriate action is to communicate the true status and the expected impacts, along with the assumptions and risks, so leaders can decide on next steps.
Ethics and professionalism in stakeholder communication mean providing truthful, timely, and objective information that supports decision-making. In this scenario, the sponsor is requesting misrepresentation of project performance, which undermines trust and can lead to poor governance decisions.
A professional response is to:
Protect confidential information while being transparent about performance; transparency does not require disclosing sensitive contractual details.
Ethical reporting requires honest, accurate, and complete information so stakeholders can make informed decisions.
Topic: Business Analysis Frameworks
You are a business analyst on a hybrid project to build a new self-service customer portal. In early requirements workshops, stakeholders agree on the goal but disagree on navigation labels and which fields must be collected on the registration screen. The product owner wants feedback within 5 business days, and the development team is not available to build anything yet. Several stakeholders have also said they “will know it when they see it.”
What is the BEST next action to validate and refine stakeholder expectations?
Best answer: B
What this tests: Business Analysis Frameworks
Explanation: When stakeholders cannot clearly articulate expectations and need rapid alignment, a prototype or wireframe is an effective elicitation technique. Low-fidelity wireframes allow the team to validate assumptions about labels, layout, and required fields quickly and cheaply. This fits the 5-day timeline and avoids waiting for development capacity.
Prototypes and wireframes help validate and refine expectations by turning ambiguous, abstract requirements into something stakeholders can react to. In this scenario, the key constraints are limited time (5 business days), disagreement about UI details, and no development availability. A low-fidelity wireframe (paper sketch or simple mockup) is fast to produce and is specifically suited to aligning stakeholders on navigation, screen content, and terminology.
A practical next step is:
This reduces rework later and creates a shared understanding before detailed solution design or build begins.
Low-fidelity wireframes quickly make assumptions visible and enable fast feedback without needing development effort.
Topic: Business Analysis Frameworks
A project team is building a customer onboarding feature for a financial app that will be released in the EU. The compliance manager states that GDPR and local KYC regulations must be reflected in the project’s requirements work products before the next release is approved.
Which artifact best validates that the regulatory requirements have been integrated into the requirements work products and are ready for verification?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: The strongest validation is evidence that each regulation has been translated into specific, testable requirements work products. A requirements traceability matrix (RTM) explicitly connects regulatory sources to requirements and their acceptance criteria, enabling coverage checks and auditability before release approval.
To integrate compliance or regulatory requirements into requirements work products, you need verifiable coverage from the regulatory source through to what the team will build and how it will be accepted. An RTM is designed for this purpose because it documents trace links such as: regulation clause → requirement/user story → acceptance criteria and (often) test cases. This makes it possible to validate readiness by checking for gaps (untraced regulations), duplicates, and unverified items before a release gate.
Key takeaway: activity evidence (meetings held) or delivery pace evidence (burndown/velocity) does not prove regulatory coverage in the requirements themselves.
An RTM provides objective evidence that each regulatory obligation is mapped to specific requirements and acceptance criteria for verification.
Topic: Project Management Fundamentals and Core Concepts
You are reviewing how effective the project’s weekly status meeting has been.
Exhibit: Meeting minutes excerpt (Weekly Status, Feb 12)
Purpose: “Weekly status”
Agenda: (not provided)
Pre-read: Not sent
Invitees: 14; Attended: 7
Planned duration: 60 min; Actual: 75 min
Decisions: None recorded
Action items: “Update schedule” (Owner: TBD); “Confirm vendor date” (Owner: TBD)
Parking lot: 5 topics (no owners)
Based on the exhibit, what is the best evaluation of this meeting’s effectiveness?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Effective meetings show evidence of preparation (agenda and pre-reads), active facilitation (timeboxing and focus), and outcomes (decisions and actionable next steps). The minutes show no agenda or pre-work, ran over time, and produced no recorded decisions or assigned action items, indicating low meeting effectiveness.
Meeting effectiveness is evaluated by whether the meeting was prepared for, well facilitated, and produced useful outcomes. In the exhibit, the meeting lacks basic preparation signals (no agenda, no pre-read), facilitation signals are weak (ran 15 minutes over and left a large parking lot), and outcomes are not captured (no decisions recorded and action items/parking-lot items have no owners). Even if useful discussion occurred, the absence of clear decisions and accountable next steps makes it hard to turn conversation into project progress.
Key takeaway: attendance count alone is not the primary indicator—prepared inputs and documented, owned outputs are.
The exhibit shows missing agenda/pre-work and a lack of captured decisions and accountable follow-up, which are core indicators of an ineffective meeting.
Topic: Agile Frameworks/Methodologies
A Scrum team is in a 2-week sprint. On day 2, a developer moves a critical user story task to Blocked on the task board because the team cannot obtain required API credentials from an external security group, and the sprint goal depends on this integration. What is the best next action to remove the impediment?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: In agile, blockers that stop progress toward the current sprint goal must be identified early and acted on immediately. An external dependency like security credentials is a classic impediment that the Scrum Master helps remove by coordinating and escalating as needed. This minimizes lost time and keeps the team focused on delivering the sprint outcome.
The core concept is rapid impediment identification and removal to protect flow and the sprint goal. When a task is marked blocked due to an external dependency, the best next action is to surface it right away (typically in or immediately after the Daily Scrum) and have the Scrum Master take ownership of removing it by coordinating with the external group. While the team may re-sequence other work temporarily, the decisive action is prompt escalation/coordination to restore access so the blocked work can continue. Treating an active blocker as a future risk or a later process discussion delays resolution and increases the chance of missing the sprint goal.
A current sprint-blocking external dependency should be surfaced immediately and owned for removal by the Scrum Master through direct coordination/escalation.
Topic: Project Management Fundamentals and Core Concepts
You are planning a hybrid project to implement a new HR information system. Midway through planning, the HR Director is identified as a key stakeholder because they can approve policy changes needed for rollout and they have strong concerns about user adoption.
As the project manager, which TWO actions best use the stakeholder register to document this stakeholder’s influence, interests, and engagement needs? (Select TWO)
Correct answers: B, D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The stakeholder register is the primary place to document who the stakeholder is and what matters for managing them, including their influence/interest and their engagement needs. Capturing influence and interests supports prioritization, while recording current/desired engagement and communication preferences supports an appropriate engagement approach.
A stakeholder register is created and updated as stakeholders are identified. For each stakeholder, it documents information the team uses to plan and tailor engagement, such as the stakeholder’s role, influence/power, interests, and how they need to be engaged.
In this scenario, the HR Director has decision influence (policy approval) and clear concerns (adoption). The stakeholder register should therefore be updated to include:
Other artifacts may be updated later, but they do not replace documenting stakeholder attributes and engagement needs in the stakeholder register.
A stakeholder register is used to document stakeholder influence and interests so the team can plan appropriate engagement.
The stakeholder register commonly includes engagement needs such as current/desired engagement and preferred communication methods.
Topic: Project Management Fundamentals and Core Concepts
A project is in the middle of delivery, and the sponsor is concerned because recent status reports show the team is behind the approved schedule. The project manager needs to determine what is causing the variance and decide whether corrective action is required.
Which type of activities best fits the purpose needed right now?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The situation is about understanding a performance variance and deciding what to do about it. That aligns with monitoring and controlling, whose purpose is to measure actual results against the plan/baselines and implement corrective or preventive actions as needed to keep the project on track.
Project work is organized into broad activity groups with different purposes. Here, the sponsor’s concern is a schedule variance, so the immediate need is to measure performance, analyze the variance, and determine appropriate actions.
Monitoring and controlling activities:
By contrast, initiating authorizes the project and sets high-level direction, planning establishes the baselines and the approach, executing performs the work to produce deliverables, and closing formalizes acceptance and transitions/archives the work. The key discriminator is the need to evaluate and respond to variance, not to create or deliver new work.
Monitoring and controlling focuses on measuring performance against the plan and taking corrective or preventive actions when variances occur.
Topic: Agile Frameworks/Methodologies
An agile software team is two sprints into a product enhancement effort. Stakeholders say progress updates are inconsistent: different team members report different completion percentages, and work that is “almost done” often carries over.
As the project practitioner supporting the team, which TWO actions best improve progress communication through information radiators and transparent working agreements? (Select TWO.)
Correct answers: E, F
What this tests: Agile Frameworks/Methodologies
Explanation: Information radiators provide a single, visible source of truth about current work and progress, reducing reliance on subjective “percent complete.” Transparent working agreements align the team on how work is tracked and when something is truly finished, so reported progress is consistent and trustworthy.
In adaptive projects, progress is best communicated by making work and flow visible and by aligning on simple team norms for using those visuals. An information radiator (physical or digital) such as a sprint/task board plus a burnup or cumulative flow view lets anyone see what is in progress, what is done, and trends without needing separate status translation. A transparent working agreement complements this by setting shared rules like how often the board is updated, what columns mean, and what criteria must be met to move work to “Done” (often captured as a Definition of Done). Together, these controls reduce inconsistent reporting and “almost done” work that keeps carrying over. Formal, document-heavy reporting or extra approvals can add overhead without improving transparency.
An accessible, frequently updated radiator (e.g., task board and burnup/cumulative flow) makes progress transparent to everyone.
A clear working agreement (including a shared Definition of Done and update cadence) reduces conflicting status interpretations.
Topic: Predictive, Plan-Based Methodologies
A project team is choosing an approach for delivering a new payroll reporting module. The sponsor states that requirements are well understood and unlikely to change, similar modules were delivered before, and the organization needs detailed cost and schedule commitments up front.
Which approach should the team NOT choose for this project?
Best answer: C
What this tests: Predictive, Plan-Based Methodologies
Explanation: The scenario describes stable requirements, low expected change, and a need for upfront schedule and cost commitments. Those conditions favor a predictive, plan-based approach where scope is baselined and plans are managed through controlled change. An approach designed around frequent reprioritization is mismatched to these constraints.
Predictive, plan-based approaches are most suitable when requirements are well understood, technology and delivery methods are familiar, and stakeholders want early commitments for scope, schedule, and cost. In these conditions, the team can define scope, build a WBS, develop a baseline plan, and manage deviations through formal change control.
An agile approach is typically selected when requirements are expected to evolve and value is maximized by frequent reprioritization based on feedback. When change is low and the sponsor needs firm commitments early, choosing an approach that assumes ongoing reprioritization creates unnecessary churn and reduces the benefit of baselining and control.
An approach optimized for frequent change and ongoing reprioritization is a poor fit when requirements are stable and firm upfront commitments are needed.
Topic: Project Management Fundamentals and Core Concepts
A project manager is leading a hybrid project to upgrade an internal billing system. Midway through execution, Sales and Finance disagree about a requested scope change that would add new approval steps and extend the planned go-live by 4 weeks. The project charter states the project manager can approve minor changes, but this request affects multiple departments and the business case. What is the best use of a steering committee/governance body in this situation?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A steering committee (governance body) provides oversight and makes high-impact decisions that cut across functions and affect the business case. When a change creates major impacts or stakeholder conflict that the project manager is not empowered to resolve, the issue should be escalated for a governance decision. Here, the request changes scope and delays the go-live, so governance is needed.
A steering committee or governance body exists to provide oversight, ensure alignment to organizational strategy, and make or sponsor decisions the project team cannot make on its own (for example, major scope/schedule/budget changes, trade-offs that affect benefits, or conflicts between senior stakeholders). Escalation is needed when an issue or change is outside the project manager’s delegated authority, creates cross-functional conflict, or would alter the business case or key commitments. In this scenario, the change impacts multiple departments and extends the planned go-live, so the appropriate next step is to escalate to governance for a decision and direction on priorities and trade-offs. Logging the issue or trying to “work it out” informally may be useful inputs, but it does not replace an authorized governance decision.
A governance body exists to resolve escalated cross-functional decisions that exceed the project manager’s authority and impact scope, schedule, and benefits.
Topic: Business Analysis Frameworks
A company is developing a new self-service customer portal. After a pilot release, users provide feedback every week and the sponsor expects priorities to change frequently to maximize business value. The delivery team works in 2-week iterations.
Which business analysis approach or artifact best supports value delivery in this situation?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: Business analysis focuses on eliciting, analyzing, and managing needs and requirements so the solution delivers intended value. In a fast-changing environment, the most effective way to do that is to frequently re-evaluate and reprioritize requirements based on value, while keeping acceptance criteria clear so each iteration can be validated against stakeholder needs.
Business analysis is the work of understanding stakeholder needs and defining/managing requirements so the delivered solution produces the desired outcomes and benefits. In the scenario, the single decisive factor is frequent change in priorities driven by ongoing user feedback. A continuously refined, value-ordered product backlog allows the team to adapt requirements quickly and select the highest-value work for each iteration, while acceptance criteria make the intended value testable and support fast validation.
Key BA value-delivery actions here include:
A more rigid, upfront baselining approach would slow learning and reduce responsiveness to value shifts.
With frequent change, ongoing backlog refinement and value-based prioritization keep requirements aligned to the highest-value outcomes each iteration.
Topic: Agile Frameworks/Methodologies
A Scrum team is planning a 2-week iteration. Their average historical velocity is 40 story points. For the upcoming iteration, two team members will be on planned leave, reducing capacity by about 25%.
The product owner still asks the team to commit to 40 story points for this iteration. If the team agrees and does not reduce iteration scope, what is the most likely near-term impact?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: Iteration scope should be based on the team’s capacity and their historical velocity. With reduced capacity, committing to the prior average (40 points) overcommits the team. The most immediate consequence is that some items will not be completed within the iteration and will need to be returned to the backlog or replanned.
In agile iteration planning, the team forecasts how much work to take on by combining capacity (how much time/availability they have this iteration) with empirical data (historical velocity). A 25% capacity reduction makes a 40-point commitment unrealistic relative to past performance.
When a team overcommits, the most likely near-term impact is:
Longer-term effects (like changing a roadmap or release date) might happen later, but the immediate consequence shows up first as incomplete iteration scope.
Committing above capacity and historical velocity most often results in incomplete stories and spillover at iteration end.
Topic: Agile Frameworks/Methodologies
A Scrum team delivers a potentially shippable increment every two weeks and demonstrates it to business stakeholders. The product roadmap states a Q3 goal: “Reduce call-center volume by 20% by enabling self-service returns.” After three sprints, stakeholders complain that delivered features feel “random” and they cannot tell how the work supports the roadmap goal.
Which underlying issue is the most likely root cause?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: Release planning connects roadmap intent to what will be delivered and when by setting release goals, selecting and sequencing backlog items, and forecasting increments. If that bridge is missing, the team can still produce working increments each sprint, but stakeholders will not see a clear line from delivered functionality to the roadmap outcome.
Release planning is the adaptive planning layer that links higher-level roadmap goals (themes/outcomes) to what is expected to be delivered in a release (a set of increments) and how success will be evaluated. In the scenario, the team is producing potentially shippable increments and showing them regularly, yet stakeholders can’t see how the work supports the “self-service returns” outcome. That points to a planning gap: the roadmap goal was not converted into a clear release objective, a prioritized set of slices that incrementally enable self-service returns, and a delivery forecast that makes the connection visible.
Key takeaway: sprint execution can be healthy while the product still lacks a coherent release plan tied to roadmap outcomes.
Without release goals and a forecast of increments tied to the roadmap outcome, sprints can deliver value but still feel unconnected to the stated objective.
Topic: Project Management Fundamentals and Core Concepts
A project coordinator is asked to capture key information about newly identified stakeholders, including their roles, level of influence, interests/expectations, and any specific communication or engagement needs. Which artifact should the coordinator update to document this information?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The stakeholder register is the primary artifact for documenting who the stakeholders are and what matters about them for managing engagement. It commonly includes stakeholder roles, influence/power, interests and expectations, and information needed to tailor communication and involvement.
The stakeholder register is created and updated as stakeholders are identified and analyzed. It is the central place to document stakeholder attributes that drive how you plan and execute stakeholder engagement, such as their role, influence or power, interests/expectations, and preferred communication or engagement needs.
This information supports later planning (for example, deciding what to communicate, how often, and how to involve each stakeholder) and helps keep the project team aligned as stakeholder information changes. The communications management plan may reference stakeholder needs, but it is the plan for how communications will be conducted—not the register used to capture stakeholder details.
The stakeholder register is used to record stakeholder identification details, influence, interests, and engagement/communication needs.
Topic: Project Management Fundamentals and Core Concepts
During a hybrid project, the project manager discovers that recent integration testing failed and the team will likely miss the next milestone. Before the governance review, the sponsor asks the project manager to report the milestone as “on track” and to share the failures only after the meeting “to avoid alarm.” Which PMI Code of Ethics and Professional Conduct value most directly applies to how the project manager should respond?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: This situation centers on whether to communicate accurate project information versus intentionally misleading stakeholders. The PMI value of honesty requires truthful, timely, and accurate reporting, especially in governance communications. The project manager should not agree to conceal known negative status to “avoid alarm.”
The core issue is a request to distort project reporting to influence stakeholder perception during a governance review. Under the PMI Code of Ethics and Professional Conduct, honesty means understanding the truth and acting in a truthful manner, including providing accurate information and not engaging in deceptive conduct. In practice, that implies reporting the real test results and milestone risk (with appropriate context and a recovery plan) rather than knowingly stating the work is “on track.”
A useful way to map the values is:
Key takeaway: when asked to misstate facts about project performance, the primary ethical value at stake is honest communication.
The request is to knowingly misrepresent project status, which conflicts with being truthful and providing accurate information.
Topic: Project Management Fundamentals and Core Concepts
A PMO is advising two teams on which life cycle approach to use.
Which TWO recommendations best fit these projects?
Correct answers: B, D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Predictive approaches fit work with stable, well-understood requirements and a need for upfront planning and formal control. Adaptive (agile) approaches fit work with significant uncertainty where value is best delivered in short iterations using frequent stakeholder feedback. The two projects described align strongly to those conditions, respectively.
Choosing between predictive, adaptive, and hybrid life cycles depends mainly on requirement stability and how the team should manage change.
Project 1 is driven by a regulation with defined requirements, a fixed-price vendor arrangement, and end-of-project sign-off; that environment favors a predictive approach with planned scope, schedule, and controlled changes. Project 2 is a new product with unclear features and expected weekly reprioritization based on user feedback; that environment favors an adaptive (agile) approach that delivers an MVP quickly and learns through iterations.
Hybrid is most appropriate when part of the work is predictable (e.g., fixed compliance components) while another part needs adaptive discovery; that mixed condition is not what is being emphasized for either project here.
Project 1 has stable, well-defined requirements and benefits from upfront planning and controlled change.
Project 2 has high uncertainty and needs iterative delivery with frequent feedback and reprioritization.
Topic: Business Analysis Frameworks
A product team is using an agile approach. Several user stories are too vague, and developers are interpreting the desired screen behavior differently. A UX designer has a clickable prototype of the flow and can walk the team through it. Which practice best matches collaborating with UX/design to clarify requirements and acceptance criteria?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: In agile environments, requirements are often clarified iteratively through collaboration and lightweight visuals. A UX prototype makes expected user interactions concrete, helping the team ask the right questions and turn ambiguous needs into testable acceptance criteria for user stories. This directly supports shared understanding before implementation.
Clarifying requirements with UX/design in an agile context commonly uses visual models such as wireframes or clickable prototypes. A facilitated prototype review (design walkthrough) helps stakeholders and the delivery team confirm intended user behavior, identify missing scenarios (errors, edge cases, content states), and convert what is learned into explicit, testable acceptance criteria tied to the relevant user stories.
In practice, the team uses the prototype to:
This creates a shared understanding faster than heavy documentation and reduces rework caused by differing interpretations.
Reviewing a UX prototype with the team helps elicit details and translate them into clear acceptance criteria for each story.
Topic: Predictive, Plan-Based Methodologies
You are managing a predictive project. A supplier informs you that a required component shipment will arrive late, which may impact a near-term testing milestone. You review the issue log entry below.
ID: ISS-009
Issue: Supplier shipment delayed by 5 business days
Priority: High
Owner: (blank)
Status: Open
Resolution criteria: (blank)
Target resolution date: April 18
Notes: Supplier provided updated ETA of April 16
What is the best next action to update the issue log so it can be effectively tracked and closed?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: The exhibit shows missing fields that prevent effective control: the issue has no accountable owner and no objective criteria to confirm when it is resolved. Updating the issue log with an assigned owner and measurable resolution criteria enables active follow-up, status tracking, and a clear basis for closure. This is the most direct improvement supported by the artifact.
An issue log is a control artifact used to track current problems through to closure. For an entry to be actionable, it should include (at minimum) clear ownership (who is responsible for driving resolution) and resolution/closure criteria (what must be true to mark it resolved). In the exhibit, the priority and status are present, and a target date and updated ETA are noted, but the owner and resolution criteria are blank.
A good update would be:
Key takeaway: without an owner and closure criteria, “Open” issues tend to stagnate and cannot be closed consistently.
An issue log must clearly identify ownership and objective closure criteria to track status and confirm resolution.
Topic: Project Management Fundamentals and Core Concepts
You are assigned to launch a new mobile app. The sponsor says, “Please create the plan by Friday so we can align everyone.” You are unsure whether the sponsor means a project management plan or a product management plan.
What should you ask for FIRST before deciding what plan to produce?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The immediate gap is the meaning of “the plan.” A project management plan governs how the project will be executed and controlled, while a product management plan focuses on product direction (vision, roadmap, releases, and lifecycle). Clarifying which of these the sponsor expects determines what content and artifacts you should prepare.
Before gathering details like resources or budget, you must confirm what “plan” refers to because the two plans serve different purposes. A project management plan is the integrated, approved set of subsidiary plans and baselines used to guide project execution and control (e.g., scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement). A product management plan focuses on managing the product over time—product vision, target customers, value proposition, roadmap/release strategy, and lifecycle decisions.
In this scenario, the sponsor’s request is ambiguous, so the first step is to clarify whether the need is project-delivery governance or product-direction planning. Once clarified, you can request the appropriate inputs (e.g., charter/scope for the project plan, or product vision/roadmap inputs for the product plan).
This clarifies whether you need an integrated project management plan (project delivery) or a product management plan (product direction and lifecycle).
Topic: Predictive, Plan-Based Methodologies
A predictive IT infrastructure upgrade is in month 2 of execution. The scope and schedule baselines were approved last month, and work packages are already assigned to teams in three time zones. This week, two teams duplicated configuration work because they were using different versions of the task assignments. The sponsor wants work to continue without changing the baselines, and a status report is due in two days.
What is the best next action for the project manager?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: During executing in a predictive project, the project manager focuses on directing and managing the work, coordinating people, and carrying out the communications approach. Here, the immediate problem is misalignment across distributed teams, while baselines must remain unchanged. A focused coordination touchpoint using the existing channels is the quickest way to get everyone working from the same current assignments.
Executing in a predictive project is where the team performs the work defined in the project management plan and the project manager coordinates people and resources to produce deliverables. A key executing activity is managing communications and stakeholder engagement so everyone uses the same information and understands current work assignments.
In this scenario, the baselines are already approved and the sponsor explicitly does not want replanning. The best next move is to quickly realign the distributed teams by using the established communication approach (for example, a coordination meeting and a single source for current assignments), then continue directing work against the plan.
Rebaselining, changing planning artifacts, or closing activities do not address the immediate execution coordination issue.
This is an executing activity that aligns the team and applies the existing communications plan to prevent further duplicated work.
Topic: Agile Frameworks/Methodologies
During the Daily Scrum, a developer says, “My work on the highest-priority story is blocked due to an access issue.” The team has not provided any additional details yet.
As the agile practitioner facilitating the meeting, what should you ask FIRST to help remove the impediment?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: In agile, impediments are removed fastest when they are made specific and actionable. Before deciding what to do, you need to know exactly what access is missing and who has authority to provide it. That information enables immediate follow-up outside the Daily Scrum to restore flow on the blocked work.
A blocker statement like “access issue” is too vague to act on. The best first step is to ask a clarifying question that turns the impediment into a concrete, solvable problem by identifying (1) what is needed and (2) the person or group that can provide it. With that, the facilitator (often the Scrum Master or agile practitioner) can coordinate the right conversation after the Daily Scrum, track it as an impediment, and help the team resume work quickly.
A time- or process-focused response (like extending the iteration or running a workshop) can be appropriate later, but it doesn’t remove today’s impediment without first understanding the specific missing access and the granting path.
This clarifies the exact blocker and the decision-maker needed so you can take an immediate, targeted action.
Topic: Business Analysis Frameworks
You are the business analyst on a hybrid project delivering a new customer self-service portal. The product owner asks you to create a 12-month product roadmap for executives.
You draft a one-page roadmap that lists 18 requested features with target months, but executives say, “This looks like a release calendar—we can’t tell what business outcomes it supports.”
What is the best next step?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: Executives are missing the strategic “why” behind the work. A product roadmap typically summarizes direction using themes and goals, then shows what will be delivered as features across a defined time horizon (for example, Now/Next/Later or quarterly). Adding these components makes the roadmap outcome-focused rather than a list of dated items.
A product roadmap is a high-level view of product direction over time. When stakeholders say a roadmap “looks like a release calendar,” it usually means the roadmap is missing the strategic layer that explains why the work matters.
A typical roadmap includes:
In this scenario, the next step is to add themes and goals and then organize the feature list into those categories across a 12-month horizon, so executives can see the connection between planned work and outcomes. Detailed sprint planning or formal change control would be premature for creating an executive-level roadmap.
A roadmap should connect features to higher-level themes/goals and show when work is expected via time horizons.
Topic: Business Analysis Frameworks
A business analyst facilitates a requirements workshop for a predictive project delivering a new payroll system. After evaluating impacts, the group decides to replace two low-value reporting requirements with one consolidated report. The sponsor asks the BA to ensure the decision is clearly communicated and formally agreed to before design continues.
Which concept best matches what the BA should do next?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: Because the project is predictive and design work is about to proceed, the requirements decision needs formal approval. Requirements sign-off (approval of the updated requirements baseline) is the mechanism used to confirm agreement and authorize using the updated requirements for subsequent planning and design. This directly communicates the decision and documents stakeholder acceptance.
In plan-based (predictive) work, requirements are typically reviewed, approved, and then treated as a baseline for downstream activities like design, build, and test. When stakeholders make a requirements decision that changes what will be delivered, the BA should ensure the updated requirements are communicated and then obtain the required approval (often called requirements sign-off) according to the project’s governance. This provides clear authorization to proceed using the updated requirements and reduces rework caused by later disputes.
Key takeaway: tracing and tracking tools support requirements management, but they do not replace explicit approval when governance calls for it.
Sign-off is the approval step used to confirm stakeholders accept requirements decisions before downstream work proceeds.
Topic: Predictive, Plan-Based Methodologies
A project manager wants the best schedule evidence for which activities must be monitored most closely to validate that the planned completion date will be met (i.e., the critical path). The team provides this activity list (durations in days):
Which path is the critical path?
Best answer: C
What this tests: Predictive, Plan-Based Methodologies
Explanation: In critical path method (CPM), the critical path is the longest-duration path through the network, which has zero total float and drives the project finish date. Summing each start-to-finish path shows that the path through B, D, and G is longest at 10 days. Therefore, it is the path that best validates the planned completion date.
CPM identifies the sequence of activities that determines the earliest possible project completion date. To find the critical path in a simple network, list each complete path from Start to Finish and add the activity durations on each path; the longest path is critical (it has the least scheduling flexibility/typically zero total float).
Here, the three complete paths into the final activity G are:
Because G cannot start until C, D, and F are all complete, the longest predecessor chain (through D) drives when G can start and when the project can finish.
This path is longest at 10 days (2 + 6 + 2), so it determines the earliest project finish.
Topic: Predictive, Plan-Based Methodologies
A predictive project has this activity network (durations in workdays):
| Activity | Predecessor(s) | Duration |
|---|---|---|
| A | Start | 3 |
| B | Start | 2 |
| C | A | 4 |
| D | B | 6 |
| E | C and D | 2 |
A vendor issue increases activity C from 4 to 7 days. No other durations or dependencies change.
What is the most likely near-term impact on the schedule?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: Using critical path method, compute the total duration of each path to the finish. Before the change, B–D–E is longest at 10 days, giving the A–C branch 1 day of float at the merge into E. Extending C by 3 days uses that float and pushes the merge, delaying the finish by 2 days and shifting the critical path.
Critical path method identifies the longest path through the network (zero total float). Here, E cannot start until both C and D are complete, so the longer of the two branches into E determines the project finish.
So the near-term impact is a 2-day slip (12 − 10), and the controlling (critical) path shifts to A–C–E because that branch now drives E’s start.
Increasing C by 3 days consumes 1 day of float and adds 2 days to the project, making A–C–E the longest path.
Topic: Project Management Fundamentals and Core Concepts
A project team is investigating recurring defects in a new customer portal. They reviewed the last 200 defect tickets and grouped them into causes with counts:
The project manager wants to apply a Pareto approach to focus improvement efforts. What is the best next step?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A Pareto approach uses measured data to identify the small number of causes responsible for the majority of the impact. Since the team already has defect counts by cause, the next step is to visualize and rank them to select the highest-leverage causes. This allows the team to focus corrective actions where they will reduce the most defects first.
Pareto analysis applies the 80/20 idea: a few causes typically create most of the problems. In this scenario, the team has already categorized defects and counted how often each cause occurs, which is the prerequisite input.
The best next step is to:
Once the top causes are selected, the team can perform deeper root-cause analysis and plan corrective actions for those items before moving to lower-impact categories.
A Pareto chart ranks causes by frequency and highlights the “vital few” that account for most defects to target first.
Topic: Business Analysis Frameworks
A project team is creating a high-level product roadmap for a new customer portal. The sponsor wants the roadmap to communicate direction to stakeholders without locking the team into detailed delivery commitments.
Which item should the team NOT include as a typical product roadmap component?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: A product roadmap is a high-level view that communicates product direction over time. Typical components include themes, goals, major features/capabilities, and time horizons. A detailed sprint-by-sprint task schedule is too granular and implies fixed commitments that a roadmap is not meant to convey.
Product roadmaps are business analysis artifacts used to align stakeholders on where a product is headed and why, over a set of time horizons. They usually emphasize intent and priorities (themes and goals) and summarize what is planned at a capability or feature level, mapped to broad timeframes (for example, now/next/later or quarterly horizons). Sprint-by-sprint task schedules are delivery-level planning artifacts used by the team to manage execution inside iterations; including them in a roadmap reduces flexibility and can mislead stakeholders into thinking the plan is fixed.
Key takeaway: keep roadmaps outcome- and capability-focused, not task-level.
Roadmaps stay high-level; sprint-level task schedules belong in iteration plans, not the product roadmap.
Topic: Business Analysis Frameworks
During user acceptance testing of a new internal HR portal, a stakeholder reports that the “employee profile” page is missing fields they expected. The team believes they built what was originally requested, but the stakeholder insists it is a defect and wants it fixed immediately.
Before deciding whether to treat this as a defect fix or a change request, what should the project team verify FIRST?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: When a gap is found during validation, the first step is to compare the delivered outcome to the approved requirement and its acceptance criteria. This determines whether the item is a nonconformance (defect) against agreed expectations or a new expectation that should be handled through change control/backlog refinement. Without that baseline, “fix it now” is an assumption.
In requirements validation, defects and gaps are evaluated against what was agreed to be acceptable. Verifying the approved requirement and its acceptance criteria provides the reference point to decide the next step: if the solution fails agreed acceptance criteria, it is a defect to correct; if the stakeholder’s expectation is not in the approved requirement/criteria, it is likely a change/new requirement that needs formal evaluation and prioritization.
A practical sequence is:
Sponsor preference, root cause, and contingency become relevant after the team confirms what “correct” means for this requirement.
Acceptance criteria and the approved requirement establish whether there is a true defect or a new/changed expectation.
Topic: Predictive, Plan-Based Methodologies
In a predictive (plan-based) project, which activity is typically performed during project or phase closing?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: Closing activities focus on formally completing the work and documenting completion. A key action is obtaining documented acceptance from the customer or sponsor that deliverables meet requirements, which supports final transition, record archiving, and administrative closure.
In predictive projects, closing a project or phase is about formally completing the work and confirming that nothing remains open from an administrative standpoint. A core closing activity is to obtain formal acceptance of the completed deliverables from the customer/sponsor, because it provides documented confirmation that the project or phase outcomes meet agreed requirements.
Other common closing activities include closing procurements, transitioning/handover of the product or service, releasing project resources, capturing final lessons learned, and archiving project records. The key idea is formal completion and documentation, not creating or refining plans.
Closing includes confirming work is accepted and formally documenting that acceptance.
Topic: Predictive, Plan-Based Methodologies
A project scheduler creates the following activity network (all durations in days). Assume finish date is driven only by logical dependencies (no resource constraints).
| Activity | Duration | Predecessor(s) |
|---|---|---|
| A | 2 | None |
| B | 4 | A |
| C | 3 | A |
| D | 5 | B |
| E | 2 | C |
| F | 1 | D, E |
Which statement is INCORRECT?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: Using the critical path method, you compare the total durations of all complete paths from start to finish. The longest path is A-B-D-F at 12 days, so it drives the project finish date. Activities on the shorter A-C-E-F path have float and typically do not change the finish when shortened or delayed within that float.
Critical path method (CPM) identifies the project duration as the length of the longest path through the network. Here there are two start-to-finish paths:
Because 12 is longer, A-B-D-F is the critical path and its activities (A, B, D, F) have zero total float. The other path is 4 days shorter (\(12-8=4\)), so activities C and E have up to 4 days of float (subject to the merge at F). Therefore, shortening E by 1 day does not reduce the overall 12-day project duration.
E is on the shorter path, so reducing it does not change the 12-day critical path duration.
Topic: Project Management Fundamentals and Core Concepts
You are a project coordinator for a hybrid project. Weekly 45-minute status meetings are repeatedly running over time, and action items are often unclear afterward. In the last two meetings, key attendees joined late because the agenda was sent only 10 minutes before the meeting, and discussions drifted into problem-solving topics that were not timeboxed.
The sponsor asks you to improve meeting effectiveness starting next week, but you cannot increase meeting length or add another recurring meeting. What is the BEST next action?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Meeting effectiveness is evaluated by preparation, facilitation, and outcomes. A timeboxed agenda sent with sufficient lead time increases participant readiness and helps the facilitator keep the discussion on track. Defining expected outputs (decisions, actions, owners, due dates) directly addresses the recurring problem of unclear action items without changing meeting length.
An effective meeting produces clear outcomes (decisions and actionable next steps), and that requires both preparation and facilitation. In the scenario, late agenda distribution undermines preparation, and untimeboxed problem-solving causes the meeting to drift and run long, which then reduces clarity of actions at the end.
The best next action is to improve the meeting design within the fixed constraints by:
Options that add time, add another recurring meeting, or focus on punitive escalation do not directly fix meeting structure and violate stated constraints or miss the root causes.
Earlier preparation with defined outcomes and timeboxes improves readiness and facilitation while fitting the fixed 45-minute constraint.
Topic: Agile Frameworks/Methodologies
A project sponsor asks you to provide a detailed Gantt chart to track progress on a new customer-facing mobile app. The delivery team says they plan to work “iteratively,” but the organization has used predictive schedules in the past.
Before deciding whether to build a Gantt chart or use adaptive tracking artifacts, what should you verify first?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: Adaptive tracking differs from predictive tracking because plans are refined each iteration as the backlog changes, rather than tracking against a fixed, detailed schedule baseline. If the work will be run in timeboxed iterations with a product backlog, progress is typically tracked with agile artifacts such as a release plan/product roadmap and burnup/burndown charts instead of a Gantt chart.
The key distinction is what you are tracking against. Predictive tracking compares actual progress to a detailed, approved schedule baseline (often visualized in a Gantt chart with task dates and dependencies). Adaptive (agile) tracking assumes scope is progressively elaborated and reprioritized, so detailed long-range task scheduling is less stable.
Before choosing artifacts, first confirm the delivery approach and planning cadence (for example, timeboxed iterations managed through a product backlog). If it is adaptive, you would typically communicate plan and progress using:
If the work is actually being managed predictively, then a Gantt-based schedule baseline and critical path analysis become appropriate.
Tracking depends first on whether the project uses adaptive iterations and backlog-based planning instead of a predictive schedule baseline.
Topic: Project Management Fundamentals and Core Concepts
A predictive project is in execution, and scope, schedule, and cost baselines have been approved. A functional manager messages the project manager: “Can you add an automated weekly performance dashboard before go-live? It should be quick.”
The project manager wants to follow integrated change control. What should the project manager obtain or confirm first before deciding whether to proceed?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Integrated change control requires changes to be formally captured and routed through the defined change control system before work begins. The first need is a documented change request with sufficient information to analyze impacts to scope, schedule, cost, risks, and quality. Only after that information is available can the request be evaluated and approved or rejected.
Integrated change control is the process used to manage changes to project documents and, especially, to approved baselines. In this scenario, a request arrives informally and the impact is unknown, so the project manager’s first step is to ensure the change is formally documented (entered into the change control system/change log) with enough detail and justification to enable impact analysis. That impact information is then used to support evaluation by the appropriate authority (often a change control board) and, if approved, to update relevant plans and baselines and communicate the decision. The key takeaway is: document and analyze the change before committing resources or updating baselines.
Integrated change control starts by formally capturing the change request so impacts can be analyzed and reviewed by the appropriate decision authority.
Topic: Project Management Fundamentals and Core Concepts
During project planning, the team identifies a potential problem: a key supplier might deliver a component late, which would delay testing. The project manager wants to document this in the risk register.
Which entry best matches what should be recorded in a risk register?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A risk register is used to document identified risks during planning in a consistent, actionable format. A complete entry includes a clear risk statement (cause-event-effect), the assessed probability and impact, a named risk owner, and a planned risk response strategy or action.
The risk register is the primary artifact for capturing and tracking risks throughout the project, starting in planning. A useful entry is more than a vague concern; it should be specific enough to manage.
A complete risk register entry typically includes:
Statements about something that has already happened belong in the issue log, and proposed changes to approved baselines belong in a change request or change log. The key takeaway is to record risks in a structured way that supports ownership and response planning.
A risk register entry includes a risk statement plus probability/impact, an owner, and a planned response.
Topic: Business Analysis Frameworks
A project team is building an e-commerce mobile app. One key dependency is integrating with a third-party payment gateway company that is not part of your organization.
When updating the stakeholder register, which entry BEST represents an external stakeholder and that stakeholder’s typical needs?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: External stakeholders sit outside the performing organization and often rely on formal agreements that define what will be delivered and how performance will be measured. In an integration dependency with a third-party provider, their needs are typically documented as interface requirements and service expectations (for example, SLAs) to manage obligations and acceptance.
Internal stakeholders (such as sponsors, functional managers, and team leads) are part of the organization doing or funding the work, so their needs commonly focus on strategy alignment, resourcing, priorities, and operational readiness. External stakeholders are outside the organization (customers, vendors/suppliers, partners, regulators) and often need clear definition of deliverables and obligations.
In this scenario, the payment gateway company is a third party that your app must integrate with, so the most typical needs to capture are:
The key discriminator is whether the stakeholder is inside or outside the performing organization and the kind of needs that usually follow from that relationship.
An external stakeholder is outside the organization and typically needs clear contractual/technical expectations such as interface specs and service levels.
Topic: Predictive, Plan-Based Methodologies
A project team is executing a predictive project. The sponsor wants a monthly update that clearly shows how the project is performing against the approved schedule and cost baselines and highlights any significant deviations.
Which artifact should the project manager use?
Best answer: B
What this tests: Predictive, Plan-Based Methodologies
Explanation: A variance report is a monitoring and controlling artifact that compares current performance to the approved baselines (for example, schedule and cost) and calls out significant deviations. Because the sponsor specifically wants visibility into performance against baselines and where the project is off-plan, the report focused on variances is the best fit.
In predictive projects, monitoring and controlling focuses on measuring actual performance and comparing it to the approved baselines so the team can identify variances and decide whether corrective action or a formal change request is needed. A variance report is designed for exactly this purpose: it summarizes where results differ from the plan (such as being ahead/behind schedule or under/over budget) and typically includes the magnitude and drivers of those deviations.
Artifacts like the charter, stakeholder register, and lessons learned register are important, but they do not provide a baseline-to-actual comparison for ongoing control. Key takeaway: when the main need is to highlight deviations from the approved plan, use a variance report rather than a general-purpose planning or documentation artifact.
It compares actual results to the baselines and highlights deviations for control actions.
Topic: Agile Frameworks/Methodologies
A product is being delivered by three Scrum teams that share components. During iteration planning, the product owner notices several high-priority backlog items require work from another team (e.g., API changes needed before a UI story can be completed). The teams have frequent reprioritization and want a lightweight way to identify and manage cross-team dependencies for the next 1–2 iterations.
Which tool or artifact is the best fit?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: The key discriminator is the need to coordinate and sequence work across multiple teams with shared components. A cross-team dependency board (or dependency map) visualizes which backlog items rely on other items/teams and helps teams negotiate ordering, handoffs, and integration timing for near-term iterations. This directly supports identifying and managing dependencies as priorities change.
In agile delivery with multiple teams, hidden dependencies are a common cause of blocked work and mid-iteration churn. A cross-team dependency board (dependency map) is designed to surface and manage these relationships by showing which backlog items depend on other items and which team owns each piece.
A practical way to use it for the next 1–2 iterations is:
Other common agile artifacts track progress, quality standards, or longer-term direction, but they do not explicitly manage cross-team dependency relationships.
It makes inter-team backlog item dependencies explicit and trackable so sequencing and coordination can be planned before work starts.
Topic: Project Management Fundamentals and Core Concepts
During schedule planning for a predictive project, the draft schedule includes an entry named “Requirements sign-off” with assigned resources and a 5-day duration. The sponsor asks for a clear view of the work needed to reach sign-off and when it will happen. What should the project manager do NEXT?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A milestone is a significant point in the schedule and typically has zero duration; it is not where work is performed. The work to reach that point should be captured as activities/tasks with estimated durations and logical relationships. Once that network exists, the milestone date can be forecast and communicated clearly.
The issue is that an item labeled as a milestone is being treated like an activity by assigning resources and giving it a duration. In a predictive schedule, you represent work as activities (tasks) that take time, expressed as task durations (e.g., 2 days, 5 days). A milestone is an event or achievement (such as “Requirements approved”) and is usually modeled as zero duration.
The best next step is to:
A due date is a target/constraint on when something must finish; it does not replace defining the work.
A milestone marks a significant event (no work/duration), so the work must be represented as activities with durations that logically lead to the milestone date.
Topic: Project Management Fundamentals and Core Concepts
A project manager notices a new business analyst is struggling to write clear acceptance criteria for user stories. Instead of giving the answers, the project manager meets one-on-one, asks probing questions, shares a simple template, and encourages the analyst to propose their own criteria for review.
Which leadership behavior is the project manager primarily demonstrating?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: This is coaching because the project manager is developing the team member’s skills and confidence through guided discovery and supportive feedback. Coaching focuses on enabling others to solve problems themselves, not on running a group session, trading concessions, or persuading stakeholders.
Coaching is a leadership behavior focused on developing a person’s capability and performance. In the scenario, the project manager uses a one-on-one conversation, probing questions, and a simple template to help the analyst learn how to write acceptance criteria and arrive at their own solution.
Coaching commonly looks like:
By contrast, facilitating is primarily about guiding a group to reach an outcome, negotiating is about reaching agreement through trade-offs, and influencing is about persuading others to support a decision or direction.
The project manager builds capability through guidance and questions rather than directing the solution.
Topic: Project Management Fundamentals and Core Concepts
A hybrid CRM implementation project has a stakeholder engagement plan that includes a weekly detailed email status to all stakeholders and a monthly steering committee meeting. After two weeks, several regional Sales Managers report that the email is too long to read, and they are worried about late surprises in sales-process changes. They ask for a way to see upcoming changes earlier and give input.
Constraints: no new collaboration tools can be purchased, and the Sales Managers can only commit to a 30-minute session every two weeks.
Which action best optimizes stakeholder engagement while meeting the constraints?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Effective stakeholder engagement includes actively seeking feedback and adjusting engagement methods to maintain buy-in. A short, recurring demo/Q&A gives Sales Managers early visibility into changes and creates a practical way to capture input. Updating the engagement approach ensures the plan reflects what is working and what is not, within the stated constraints.
Stakeholder engagement is executed by following the plan, monitoring stakeholder responses, and then tailoring the approach based on what stakeholders say and how they behave. In this scenario, Sales Managers are signaling that the current one-way communication is not effective (too long, not timely for change impact) and they need earlier, interactive visibility.
A biweekly, 30-minute demo/Q&A uses existing tools, fits their availability, and adds two-way communication so concerns can be identified and addressed early. The project should then update the stakeholder engagement/communications approach (and capture outcomes such as decisions, actions, and newly identified needs) so future engagement is intentional and consistent. The key takeaway is to adapt engagement tactics based on feedback while respecting constraints, rather than simply increasing volume or relying on authority.
It adds a two-way, time-boxed feedback loop that matches stakeholder availability and adapts the planned engagement strategy.
Topic: Business Analysis Frameworks
A business analyst is helping a product owner create a product roadmap for a new customer self-service portal. Executives asked for a one-page view that shows, at a high level, what is expected to be delivered and roughly when.
Which TWO items are typical components to include on the product roadmap? Select TWO.
Correct answers: B, E
What this tests: Business Analysis Frameworks
Explanation: A product roadmap is a high-level communication artifact that summarizes planned product deliverables over time. It commonly includes a view of major features/initiatives and the time horizons or release windows in which they are expected to be delivered, without going into execution-level detail.
Product roadmaps are used to align stakeholders by showing the intended direction of the product and the planned delivery of value over time. Because the executives want a one-page, high-level view of “what” and “when,” the roadmap should highlight major deliverables (often expressed as initiatives, epics, or key features) and a time horizon (such as Now/Next/Later, quarters, or release windows). Roadmaps intentionally avoid detailed planning artifacts; those belong in plans and backlogs used by delivery teams.
Key takeaway: a roadmap is strategic and time-phased, not a detailed execution or tracking log.
A roadmap typically summarizes planned deliverables at a feature/initiative level rather than detailed requirements.
Roadmaps communicate direction over time using time horizons or release windows for planned work.
Topic: Agile Frameworks/Methodologies
A Scrum team tracks work using a sprint burndown chart and reviews average velocity (story points completed per sprint) during sprint reviews. Midway through the current 2-week sprint, the product owner asks the team to add a new user story estimated at 8 story points to the sprint backlog, and the team agrees.
What is the most likely near-term impact on the team’s tracking?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: A sprint burndown shows remaining work over time, so when scope is added mid-sprint the remaining-work value increases right away and the chart reflects an upward movement. Velocity is a historical measure based on work actually completed in a sprint, so it does not change immediately when new work is merely added.
In adaptive projects, two basic tracking concepts are:
Because the team added an 8-point story to the sprint backlog, the total remaining work increased immediately. That change shows up right away on the sprint burndown as an upward step (or a less-steep downward trend), which can reduce confidence in meeting the sprint goal unless scope, capacity, or priorities are adjusted. Velocity is only known after the sprint ends because it is calculated from what the team actually finishes, and it is most useful when scope changes are controlled so trends remain comparable.
Adding story points mid-sprint increases remaining work, which immediately raises the burndown’s remaining-work line.
Topic: Project Management Fundamentals and Core Concepts
A project team is planning a hybrid project to configure and deploy a new CRM system. The charter identifies the product as “a CRM that supports lead tracking and standard reports.” During planning, the sponsor adds a new expectation: “The CRM must integrate with the marketing platform to automatically score leads.”
Which response best reflects the difference between product scope and project scope for planning purposes?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The new integration and lead scoring capability describes what the CRM must do, which is product scope. Once the product scope is clarified/updated, the team must plan the additional work required to deliver it (project scope) by updating the WBS and the related estimates.
Product scope describes the features and functions of the deliverable (the CRM capabilities), while project scope describes the work needed to produce those deliverables (the tasks and work packages the team will perform). In the scenario, “integrate with the marketing platform to automatically score leads” is a new product capability, so it belongs in the requirements (or product backlog in hybrid/agile components). After product scope is updated, planning artifacts that describe the work—such as the WBS, activity list, and cost/schedule estimates—must be revised to reflect the added integration design, build/configuration, testing, and deployment work. The key takeaway is that product scope drives project scope during planning: changes to what is being built typically require changes to the work plan.
The requested integration is a product feature (product scope) that then drives additional work to plan and estimate (project scope).
Topic: Agile Frameworks/Methodologies
A product team uses an adaptive approach with 2-week iterations. The organization requires security and privacy compliance evidence, but the team wants to avoid adding heavy documentation and late audits.
Which practice best integrates governance and compliance into adaptive delivery with minimal overhead?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: In adaptive delivery, governance and compliance are best handled by making them part of normal delivery work rather than separate gates. Defining compliance needs as backlog items/acceptance criteria and including them in the Definition of Done ensures each increment is compliant and produces evidence continuously. This integrates control while keeping overhead low and feedback frequent.
Adaptive delivery can meet governance and compliance by treating them as built-in quality, not as a separate end-of-project activity. The team translates compliance needs (for example, security/privacy controls and required evidence) into backlog items and/or acceptance criteria, and then includes the necessary checks and evidence in the Definition of Done so every completed item produces a compliant increment.
This typically looks like:
A separate compliance phase or frequent external sign-offs increases delays and rework, which is the opposite of lightweight, iterative control.
Embedding compliance criteria in backlog items and the Definition of Done makes compliance a routine part of each iteration and increment.
Topic: Agile Frameworks/Methodologies
A scrum team uses a task board to manage work in progress (WIP). Mid-sprint, the team notices several items are waiting for review.
Exhibit: Task board (excerpt)
WIP limits: Dev=3, Review=2, Test=2
To Do: US-18, US-21
Dev: US-12, US-14, US-17
Review:US-12, US-14, US-17
Test: (empty)
Done: US-09
What is the best next action to manage WIP and restore flow?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: The task board shows Review has 3 items against a WIP limit of 2, indicating a bottleneck that is blocking flow to Test. In agile, the team manages WIP by focusing on finishing work already in progress before starting new work. Swarming to clear the constrained column restores flow and reduces multitasking.
A task board visualizes where work is accumulating and makes WIP problems visible. In the exhibit, Dev is at its WIP limit (3), but Review is over its WIP limit (3 items vs. limit of 2), while Test is empty; this signals that Review is the constraint preventing work from flowing downstream.
The appropriate WIP-based response is to:
Raising WIP limits or skipping process steps may hide the bottleneck and increase cycle time rather than improving flow.
Review exceeds its WIP limit, so the team should stop pulling new work and collaborate to remove the review bottleneck.
Topic: Project Management Fundamentals and Core Concepts
A retail company approves several pieces of work for the next year:
The first three efforts are intended to jointly improve the end-to-end customer experience and deliver business benefits that are not achievable if they are managed separately. Leadership also wants to decide which investments (including these) get funding based on strategic objectives.
Which TWO statements correctly describe how this work should be organized and related? (Select TWO)
Correct answers: B, D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A program groups related projects and activities to coordinate dependencies and deliver benefits that are greater than managing each effort alone. A portfolio groups work to optimize strategic value and investment decisions and can include projects and programs that are not directly related to each other. In the scenario, customer-experience work fits a program, while leadership’s funding/prioritization need fits a portfolio.
A project is a temporary effort that creates a unique product, service, or result. A program is a group of related projects (and possibly additional program work) managed in a coordinated way to achieve benefits and control that would not be available if the components were managed separately—this matches the app, CRM upgrade, and training aimed at a shared customer-experience benefit. A portfolio is a collection of projects, programs, and other work grouped to achieve strategic objectives; components in a portfolio do not need to be directly related, and the focus is prioritization and investment decisions. Key takeaway: use programs for coordinated benefits across related components, and portfolios for strategy-driven selection and prioritization across all investments.
A program coordinates related projects and activities to deliver benefits not available if managed individually.
A portfolio is a collection of components managed to achieve strategic objectives and prioritize investments, whether or not they are related.
Topic: Project Management Fundamentals and Core Concepts
A project team agreed on several risk responses during planning (for example, “qualify a backup supplier” and “schedule a security review early”). Two months into execution, the project has repeated disruptions from the same risks. In a weekly status meeting, the project manager cannot tell which risk responses have been completed or who is driving them.
An excerpt of the risk register shows several risks with response strategies listed, but the Owner field is blank and there is no column for response status or target dates.
What is the most likely underlying cause of the problem?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The key clue is that the register lists response strategies but has no owners or response-tracking fields, and the PM cannot report response completion. That points to a breakdown in risk monitoring and control, where the risk register is not being updated and responses are not being tracked to closure. Assigning owners and tracking status is essential to executing planned risk responses.
In a risk management approach, the risk register is a living document used not only to record risks but also to monitor response implementation. The scenario shows responses were planned, yet the team cannot confirm execution because ownership and tracking information is missing.
To track responses effectively, the team typically:
When these tracking mechanisms are absent, responses tend to become “agreement only,” leading to repeated risk impacts and no visibility into what has been done.
Without assigned risk owners and response status tracking, planned responses are not executed or monitored, so the same risks keep recurring.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project is deploying a new customer support portal. Development has completed final fixes, but the operations manager says they will only take ownership after confirming that support processes (runbooks, monitoring, access, and on-call training) are in place. The project manager needs one artifact to verify readiness for handover and obtain operational acceptance.
Which artifact is the best fit?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Operational acceptance depends on the receiving organization being ready to support and run the solution, not just that requirements were built or tested. An operational readiness checklist (often part of a transition plan) is used to confirm items like support procedures, monitoring, access, training, and ownership. Getting operations sign-off demonstrates readiness for handover.
Transition planning focuses on ensuring the deliverable can be successfully operated after the project ends. In this scenario, the decisive factor is the operations manager’s condition for acceptance: readiness of ongoing support capabilities (runbooks, monitoring, access, and training). An operational readiness checklist is designed to verify those handover prerequisites and capture formal sign-off from the receiving operations team.
A typical readiness checklist confirms, for example:
Testing and requirements artifacts can support the transition, but they do not, by themselves, demonstrate operational readiness to take over.
It directly verifies handover readiness items required for operational acceptance before transition.
Topic: Predictive, Plan-Based Methodologies
A project sponsor asks, “Are we on track?” You receive an earned value summary but it does not state the reporting cut-off or baseline version.
Exhibit: Earned value summary
| Metric | Amount (USD) |
|---|---|
| PV | $200,000 |
| EV | $180,000 |
| AC | $210,000 |
What should you verify/obtain FIRST before deciding whether performance is on track?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: To judge whether EVM performance is on track, you must ensure PV, EV, and AC are comparable. That requires knowing the status date (reporting cut-off) and confirming the measures are calculated against the current approved baseline. Without that context, any CPI/SPI interpretation could be misleading.
Earned value metrics are time-phased and baseline-dependent. PV represents planned value as of a specific status date from the approved performance measurement baseline; EV and AC must be measured for the same cut-off. If the report’s status date is unclear or the baseline version is outdated (for example, not updated for approved changes), the PV/EV/AC relationship may not reflect true schedule/cost performance.
Before concluding whether the project is “on track,” first confirm:
Only after that should you interpret indices such as SPI and CPI to assess performance.
EVM indices are only meaningful when PV, EV, and AC are measured to the same status date against the approved baseline.
Topic: Agile Frameworks/Methodologies
A software team using Extreme Programming writes automated unit tests before writing the production code, then codes only enough to pass the tests and refactors. Which XP practice is being described?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: The described sequence—write tests first, implement minimal code to pass them, then refactor—matches test-driven development. In XP, TDD is used to build quality in by guiding design with fast, automated feedback. The other options describe different collaboration, integration, or inspection activities.
In Extreme Programming (XP), test-driven development (TDD) is a development practice where tests are created before the code that fulfills them. The team then writes the simplest code to pass the tests and refactors to improve design while keeping tests green. This tight feedback loop helps prevent defects and supports frequent change.
A common TDD cycle is:
The key identifier in the scenario is the explicit “tests first” behavior; that is unique to TDD versus other XP practices like pairing or integrating frequently.
TDD requires writing automated tests first, then implementing code to make the tests pass and refactoring.
Topic: Business Analysis Frameworks
In a project with ongoing product development, which statement best describes the purpose of a product roadmap?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: A product roadmap is a high-level, time-oriented communication tool that shows where the product is going and why. It helps align stakeholders by expressing direction and priorities across upcoming time horizons (for example, near-, mid-, and longer-term). It is not meant to be a detailed requirements list or a short-term team execution plan.
A product roadmap is a high-level plan that communicates the product vision, direction, and evolving priorities across time. Its main purpose is alignment: it helps stakeholders understand what outcomes or themes are planned next, what comes later, and how the product is expected to evolve, without committing to detailed scope at the task level. Roadmaps are often organized by time horizons (now/next/later or by quarters) and may show themes, goals, major features, or releases. Because it is a strategic communication artifact, it supports decisions about sequencing and investment and sets expectations about direction while allowing details to change as learning occurs.
Key takeaway: a roadmap is broader and more time-phased than a backlog, sprint plan, or acceptance criteria.
A product roadmap provides a time-phased view of where the product is headed to align stakeholders on direction and priorities.
Topic: Agile Frameworks/Methodologies
A cross-functional Scrum team is halfway through a 2-week sprint. A high-priority user story is coded but still needs testing and a short user-guide update to meet the Definition of Done. The tester is busy on another story, and the technical writer is unsure what changed.
Which action should the team NOT take to coordinate handoffs and collaboration to finish the work in the sprint?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: In an adaptive project, the team collaborates daily to complete work to the Definition of Done within the iteration. Coordinating handoffs means making dependencies visible and re-planning together so testing and documentation happen in time, not as later phases. Deferring remaining work to the next sprint undermines finishing the story as a usable increment.
Agile teams finish work by collaborating across specialties and managing handoffs inside the iteration. When a story needs contributions from testing and documentation, the team should make the remaining tasks and dependencies visible (task board), quickly align on sequence and availability (short sync), and re-balance work (swarming/pairing) so the story can meet acceptance criteria and the Definition of Done.
Treating testing and documentation as separate follow-on work in a later sprint creates an “over-the-wall” handoff and often results in partially done stories, reduced transparency, and less reliable sprint outcomes.
Deferring the remaining cross-functional work creates a mini-waterfall handoff and risks delivering an incomplete increment this sprint.
Topic: Project Management Fundamentals and Core Concepts
During a hybrid project, the team tracks supplier lead-time risk in the risk register. Risk R-07 (“primary vendor delivery delay”) has an agreed response: “activate pre-qualified backup supplier” with the procurement lead as the risk owner.
Today the vendor confirms a 2-week slip and the delay will impact an upcoming milestone unless action is taken. What is the best next step?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: When a risk event occurs, the risk register must be updated to reflect the trigger, current status, and actions taken. The project team then executes the pre-planned response and tracks response actions and effectiveness (including any residual or secondary risks) so stakeholders have accurate, current risk information.
The risk register is a living artifact used to monitor risks and control risk responses throughout the project. When a defined risk trigger occurs (the vendor confirms the slip), the project should record the change in risk status and proceed with the planned response, assigning/confirming ownership and tracking response actions and outcomes.
Practically, that means:
A change request or escalation may be appropriate later if the planned response cannot keep objectives within acceptable limits.
Once a risk triggers, you update the risk register and track implementation/effectiveness of the planned response.
Topic: Project Management Fundamentals and Core Concepts
You are the project coordinator on a hybrid CRM implementation. The sponsor asks you to “report 95% complete” to the steering committee even though several features have not yet been accepted by the customer service director.
To communicate professionally and ethically, which evidence best validates progress for the status report?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Ethical stakeholder reporting is truthful, transparent, and based on verified information rather than pressure or optimism. A signed acceptance record demonstrates that the customer has validated completed work against agreed criteria, making it the most reliable basis for reporting progress and readiness.
Professional, ethical communication requires that status reports reflect accurate, verifiable information and do not mislead stakeholders with inflated or ambiguous claims. In this scenario, “percent complete” should be grounded in evidence that the customer has accepted the delivered functionality, not in activity levels or informal statements.
Acceptance documentation (such as signed UAT results or an approved deliverable acceptance record) provides traceable proof that:
Activity outputs and vanity measures can be useful for internal tracking, but they do not ethically justify claiming completion when acceptance has not occurred. The key takeaway is to report progress using objective acceptance/validation evidence.
Formal acceptance records provide objective, verifiable status aligned to agreed acceptance criteria.
Topic: Business Analysis Frameworks
A product team uses quarterly releases and maintains a product roadmap with three candidate releases. Marketing wants a demo-ready set of features for an industry event in 10 weeks, and Legal requires specific controls in production by the end of Q3. Stakeholders are asking you to recommend how to sequence the releases, but the roadmap only shows high-level epics.
What should you verify or obtain first before deciding the release sequence?
Best answer: B
What this tests: Business Analysis Frameworks
Explanation: Release sequencing requires balancing fixed business deadlines with what the team can actually deliver. Since only high-level epics are shown, the most critical missing input is the team’s forecast capacity (availability and velocity) for the upcoming release windows. With that constraint known, you can then size/select minimum scope that fits each deadline and sequence accordingly.
When you sequence releases on a roadmap, you are making a feasibility decision: what can be delivered by each business deadline given real delivery capacity. In the scenario, deadlines are known (event in 10 weeks and end-of-Q3 compliance), but the roadmap only has high-level epics and does not state whether the team has the capacity to deliver any proposed scope in those windows.
Start by obtaining a capacity forecast for the relevant release windows (e.g., team availability, shared-resource constraints, and recent velocity/throughput). Then you can translate epics into a minimum releasable scope per deadline and sequence releases to fit within those capacity limits. The key takeaway is that sequencing without capacity data risks committing to dates that the team cannot meet.
You need realistic capacity data to determine what scope can fit into each timeboxed release while meeting the fixed dates.
Topic: Business Analysis Frameworks
During a backlog refinement session for a hybrid project, a stakeholder says, “The dashboard needs to load quickly.” The business analyst practices active listening by paraphrasing the need and asks clarifying questions (for example, target load time, peak users, and what “dashboard” includes) and then confirms the wording with the group.
What is the most likely near-term impact of this approach?
Best answer: B
What this tests: Business Analysis Frameworks
Explanation: Active listening and clarifying questions reduce ambiguity by turning subjective language into specific, verifiable statements. In the near term, the team can immediately capture a shared understanding (including measurable acceptance criteria) and proceed with planning and refinement based on the same interpretation.
The core concept is reducing requirements ambiguity through active listening (paraphrasing, reflecting, confirming) and clarifying questions (making vague terms specific and measurable). In the scenario, “loads quickly” is subjective; by asking about target seconds, conditions (peak load), and scope (which screens/data), the analyst helps stakeholders converge on one interpretation.
This typically produces near-term outcomes such as:
The key takeaway is that these techniques create shared understanding now; downstream benefits may follow, but they are not the most immediate impact.
Paraphrasing and clarifying questions convert a vague need into shared, measurable requirements right away.
Topic: Project Management Fundamentals and Core Concepts
A software company is launching a new customer portal. The project team will deliver the initial release in 4 months, while the product manager owns the longer-term evolution of the portal over multiple releases.
Which statement is INCORRECT when distinguishing the project management plan from the product management plan?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A project management plan is the integrated plan for managing project work—how the team will execute, monitor/control, and close the project, including relevant baselines. A product management plan is oriented to the product’s longer-term direction, such as vision, roadmap, and release strategy across multiple releases. Therefore, assigning day-to-day project control to the product management plan is a mismatch.
The project management plan is the primary artifact used to manage the temporary endeavor (the project). It explains how the work will be performed and controlled, typically integrating subsidiary plans (e.g., scope, schedule, cost, quality, resources, communications, risks, procurement, stakeholder engagement) and establishing baselines for the approved project scope and targets.
A product management plan is oriented to managing the product over its life, emphasizing product direction and value delivery, such as:
In the scenario, the 4-month effort to deliver the initial release is governed by the project management plan, while the multi-release evolution belongs to product planning. Key takeaway: product plans guide “what/why over time,” while project plans govern “how the project work gets done and controlled.”
Day-to-day management and control of project work is defined in the project management plan, not the product management plan.
Topic: Agile Frameworks/Methodologies
A Scrum team is starting a 2-week sprint. During Sprint Planning, they select several product backlog items to deliver, but they decide not to create a separate sprint backlog and will track all selected work only in the product backlog.
What is the most likely near-term impact of this decision?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: The sprint backlog is the adaptive artifact that represents the team’s selected work for the sprint (often decomposed into tasks) and is used to manage and track execution. Keeping everything only in the product backlog reduces transparency and makes it harder to manage the sprint at a day-to-day level. The most immediate consequence is confusion and weaker tracking of sprint progress.
In Scrum, the product backlog is the ordered list of all desired work for the product over time, while the sprint backlog is the set of items selected for the current sprint along with the plan to deliver them. If the team skips the sprint backlog and tracks selected work only in the product backlog, the near-term effect is reduced clarity about what is in-scope for the sprint and weaker day-to-day control of execution.
Practically, a sprint backlog supports:
The key takeaway is that mixing sprint execution tracking into the product backlog undermines short-cycle transparency and control.
Without a sprint backlog, the team loses a clear, focused view of the selected work and the tasks needed to complete it in the current sprint.
Topic: Project Management Fundamentals and Core Concepts
A project team is building an internal reporting dashboard. In a requirements workshop, the sponsor says, “Make the dashboard more intuitive,” and the team has delivered the wrong layout before due to vague feedback. As the project practitioner, which action should you NOT take if your goal is to use active listening and clarifying questions to reduce ambiguity and rework?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Active listening reduces ambiguity by reflecting back what was heard and testing understanding with targeted questions. When stakeholders use subjective language, the practitioner should elicit concrete examples, users, and success criteria, then confirm shared understanding. Moving forward based on an assumption does the opposite and commonly causes rework.
Active listening is used to confirm understanding and uncover hidden assumptions before the team commits to work. When a stakeholder uses vague or subjective wording (like “intuitive”), the practitioner should clarify by paraphrasing, asking open and specific follow-up questions, and confirming agreement on what will be delivered.
Practical ways to do this include:
Assuming the meaning based on prior work or personal interpretation bypasses shared understanding and is a common driver of defects and rework.
Proceeding based on an assumption skips clarification, increasing ambiguity and the risk of rework.
Topic: Agile Frameworks/Methodologies
A project sponsor asks a new CAPM to recommend when an adaptive (agile) approach is appropriate. Which situation is NOT a good fit for using an adaptive approach as the primary delivery method?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: Adaptive approaches are most suitable when requirements and priorities are expected to evolve and the team can learn through rapid feedback on incremental deliveries. A situation that requires stable, fully defined requirements and early baselining for compliance aligns better with a predictive approach that emphasizes upfront planning and control.
Adaptive (agile) approaches are a strong fit when there is high uncertainty and the team needs to discover the best solution through short cycles, frequent stakeholder collaboration, and rapid feedback. They assume requirements and priorities may evolve, so work is planned just-in-time and delivered incrementally to validate value early.
When requirements are stable, fully known, and must be approved and baselined early (often for governance or compliance), the project benefits from predictive planning with controlled changes rather than continuous scope evolution. The key takeaway is to match the approach to the level of uncertainty and the need for fast learning and reprioritization.
Adaptive approaches work best with evolving requirements and fast feedback, not when scope must be fixed and approved upfront.
Topic: Predictive, Plan-Based Methodologies
A project manager is preparing a monthly earned value report for a predictive project. The sponsor asks whether the project is spending more or less than planned for the work completed so far.
| Metric | Value |
|---|---|
| EV (earned value) | $80,000 |
| AC (actual cost) | $90,000 |
| PV (planned value) | $85,000 |
What should the project manager report?
Best answer: C
What this tests: Predictive, Plan-Based Methodologies
Explanation: Cost variance (CV) measures cost performance by comparing earned value to actual cost for the work performed. Using the provided data, CV is negative because actual cost is greater than earned value. A negative CV indicates the project is spending more than planned (over budget) for the completed work.
Cost variance (CV) is an earned value management measure that shows whether the project is over or under budget for the work performed to date. It is calculated as the difference between the value of completed work and what it actually cost:
CV = EV - ACCV > 0 is under budget; CV < 0 is over budgetIn this scenario, the project has earned $80,000 of value but spent $90,000 to achieve it, so the variance is negative and indicates overspending relative to plan for the work completed. A common confusion is mixing cost variance with schedule variance or cost efficiency indices.
Cost variance is calculated as EV − AC, and a negative CV indicates over budget for the work performed.
Topic: Predictive, Plan-Based Methodologies
A predictive software project is in Executing, and the scope and schedule baselines have been approved. A key stakeholder requests adding a new reporting feature, and the project manager estimates it will add 2 weeks and require additional vendor work on a fixed-price contract. The stakeholder asks the team to start immediately so the release date is not questioned.
What is the project manager’s BEST next action?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: Integrated change control exists to evaluate requested changes, determine impacts, and route them for the correct level of approval or rejection. Because the request affects baselined scope/schedule and a fixed-price vendor engagement, the project manager should document the request and obtain formal approval before authorizing work or updating baselines.
In predictive projects, integrated change control is the discipline that prevents unauthorized scope, schedule, cost, or contract changes from being implemented informally. When a stakeholder requests a change that affects approved baselines, the project manager should capture it as a change request, have impacts analyzed (including vendor/contract implications), and route it to the defined approval authority (often a change control board or sponsor, based on the change control process). Only after approval should the project manager update the relevant plans/baselines, communicate the decision, and direct the work. The key takeaway is that approvals authorize implementing the change and updating controlled baselines—starting work or updating baselines first bypasses control.
Integrated change control ensures the change is evaluated and approved/rejected by the appropriate authority before baselines and work are updated.
Topic: Predictive, Plan-Based Methodologies
You are the project manager for a predictive project with an approved schedule baseline. A critical-path activity is slipping because key resources were reassigned.
Exhibit: Issue log excerpt
ID: ISS-12
Issue: Two system engineers reassigned to Operations work
Impact: Activity A-120 on critical path may slip 10 days
Notes: Eng. Functional Manager approves staff assignments;
PM cannot authorize overtime or change assignments
Requested: Restore resources or approve backfill
Based on the exhibit, what is the best next action?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: The issue log shows that the functional manager controls staff assignments and the project manager cannot authorize overtime or reassign resources. That reflects a functional or weak matrix structure, where the PM must obtain and maintain resource commitments through functional management and use escalation paths to protect the predictive schedule baseline.
Organizational structure directly affects how a predictive project manager plans and controls work, especially for resources and decisions. In a functional or weak matrix organization, functional managers have primary authority over people, and the PM’s authority is limited. When a critical-path activity is at risk due to resource reassignment, the PM’s best move is to work through the functional manager to restore resources or arrange approved backfill, then escalate to the sponsor if priorities cannot be resolved.
In contrast, a projectized structure typically gives the PM direct authority to assign resources, and a virtual structure mainly describes where people work (distributed) rather than who controls staffing decisions. The key takeaway is that limited PM authority means negotiation and escalation are central to maintaining baselines in predictive projects.
The exhibit indicates low PM authority typical of a functional/weak matrix structure, so resources must be secured through functional management channels.
Topic: Agile Frameworks/Methodologies
A product team is using an adaptive approach for a mobile app. Instead of waiting 4 months to release all features, they deliver a small set of working features every 2 weeks and review the increment with users and business stakeholders to adjust priorities and clarify requirements.
Which concept best explains how this approach reduces project risk?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: This scenario describes delivering usable product increments frequently and using stakeholder reviews to adjust what to build next. That is iterative and incremental delivery, which reduces risk by validating assumptions early and enabling quick corrections when feedback reveals misunderstood needs or low-value features.
Iterative and incremental delivery means building the product in small slices and learning from each slice. In the scenario, the team delivers working features every 2 weeks (incremental) and uses reviews to adapt priorities and clarify requirements (iterative learning).
This reduces risk because it:
The key takeaway is that frequent delivery plus feedback loops reduces uncertainty compared with a single big-bang release.
Delivering small working increments frequently enables early validation and course correction before large investments are made.
Topic: Project Management Fundamentals and Core Concepts
A project team must select one collaboration tool for a hybrid project. Stakeholders agreed to use a weighted scoring model (1–5 scale; 5 is best) with the criteria weights below.
| Criteria | Weight | Tool Alpha | Tool Beta | Tool Gamma | Tool Delta |
|---|---|---|---|---|---|
| Security controls | 50% | 5 | 4 | 3 | 5 |
| License cost | 20% | 2 | 4 | 5 | 1 |
| Integration with existing systems | 30% | 3 | 3 | 5 | 4 |
Based on the weighted scoring model, which tool should the team select?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A weighted scoring model compares alternatives across multiple criteria by applying agreed weights to each criterion score and summing the results. Using the provided weights (50%/20%/30%), Tool Gamma produces the highest weighted total, so it is the best overall fit per the selection method the stakeholders approved.
A weighted scoring model (decision matrix) is used when you must choose among alternatives using multiple criteria that do not have equal importance. You multiply each alternative’s score by the criterion weight and sum the weighted values; the highest total is the preferred option.
For the tools shown, the weighted totals are:
The key takeaway is to follow the agreed weights rather than choosing the option that looks best on a single criterion.
It has the highest total weighted score when each criterion score is multiplied by its weight and summed.
Topic: Agile Frameworks/Methodologies
In an agile project, the team is breaking down a high-level product scope into smaller items and ordering them so the most valuable work is ready for upcoming iterations. Which artifact is primarily used to capture and prioritize epics, features, and user stories?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: The product backlog is the central agile artifact used to decompose and prioritize scope into an ordered list of work. It commonly contains epics, features, and user stories and is continuously refined to keep the highest-value items ready for near-term iterations.
In agile, scope is managed as an evolving, prioritized list rather than a fully detailed plan up front. The product backlog is the artifact that holds the complete set of desired product work and orders it by factors such as customer value, risk, and dependencies. High-level needs are captured as epics, then decomposed into features and user stories during backlog refinement so the team can select the best candidates for upcoming iterations.
A sprint backlog is a short-term plan for a single iteration, while a WBS and RTM are more typical in predictive/business analysis contexts and are not the primary agile mechanism for prioritizing epics, features, and user stories.
The product backlog is the ordered list of work items (including epics, features, and user stories) prioritized by value and other factors.
Topic: Business Analysis Frameworks
A project team is gathering requirements for a new customer self-service portal. The business analyst is helping stakeholders separate functional requirements (what the system does) from non-functional requirements (how well it works or constraints).
Which requirement below is NOT a non-functional requirement?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: Functional requirements describe specific system behaviors or features, such as what actions users can perform. Non-functional requirements describe quality attributes or constraints, such as performance, capacity, and security. The password reset statement is a feature the portal must provide, so it is functional rather than non-functional.
Functional requirements define what the solution must do (features, behaviors, and business rules), such as enabling a user to complete a task or the system to perform an operation. Non-functional requirements define how well the solution must perform or constraints it must meet, often expressed as measurable quality attributes.
In this scenario:
A user password reset capability is a specific function the portal provides, making it a functional requirement; quality-attribute requirements describe characteristics of that function rather than the function itself.
This describes a system behavior/capability, which is a functional requirement.
Topic: Project Management Fundamentals and Core Concepts
A project team is planning a predictive project to deliver a new internal sales reporting dashboard. During planning, the sponsor asks how “scope” will be defined and controlled.
Which statement is INCORRECT about product scope versus project scope and how each affects planning?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Product scope focuses on what the product is and does (features/functions and acceptance criteria). Project scope focuses on the work required to deliver that product and is decomposed into a WBS for planning. Confusing which “scope” the WBS is based on leads to incorrect planning artifacts and scope control.
Product scope is the set of features, functions, and acceptance criteria that describe the product or service being created (the “what” the customer/user will get). Project scope is the work performed to deliver that product (the “how” in terms of deliverables and tasks).
In a predictive environment, planning typically follows this flow:
The WBS is built from the project scope because it organizes the deliverables and work needed to produce the product, not the product’s feature list itself.
A WBS is a decomposition of the project scope (deliverables/work), while product scope describes the product’s features and functions.
Topic: Project Management Fundamentals and Core Concepts
A hybrid software project is in planning. A new organizational accessibility standard is issued and will apply to all features built going forward.
The project manager decides not to update the quality management plan and tells the team, “We’ll handle accessibility by doing extra testing at the end.”
What is the most likely near-term impact of this decision?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A quality management plan defines the quality standards, metrics, and the planned activities for quality assurance (process-focused prevention) and quality control (deliverable-focused inspection). By not updating the plan and pushing accessibility to end testing, the team misses preventive QA guidance. The most immediate result is defects discovered after work is built, creating rework in the next increments.
The quality management plan documents how the project will meet quality requirements, including applicable standards, quality metrics, roles/responsibilities, and when/how QA and QC will be performed. When a new standard is introduced, the plan should be updated so the team can build quality in from the start.
Quality assurance (QA) is process-focused and preventive (e.g., training, process improvements, audits) to reduce the likelihood of defects. Quality control (QC) is product-focused and detective (e.g., inspections, testing) to identify nonconforming deliverables.
Deferring accessibility to “extra testing at the end” emphasizes QC while skipping near-term QA updates, so accessibility issues are likely to be discovered after features are implemented, driving immediate rework and disruption to near-term delivery.
Relying on end-of-phase inspection (QC) instead of planned preventive QA allows nonconforming work to be built, causing rework when tested.
Topic: Agile Frameworks/Methodologies
A Scrum team is building a customer mobile app in 2-week sprints, with a release scheduled in 6 weeks. Over the last two sprints, production defects have increased (12 open defects), and developers report growing technical debt causing frequent build failures. A key stakeholder is pressuring the product owner to prioritize a new “one-click payment” feature in the next sprint. The team’s capacity is fixed and sprint planning is tomorrow.
What is the BEST next action to ensure defects and technical debt are tracked and prioritized alongside feature work?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: In agile, defects and technical debt should be made visible as work and prioritized with everything else. Capturing them as product backlog items and refining/ordering them with the product owner allows transparent trade-offs with feature work given fixed capacity and an imminent planning event.
The core control in adaptive projects is a single, transparent ordering mechanism for all work. Defects and technical debt are still work that consumes capacity and affects value delivery (quality, stability, speed), so they should be explicitly tracked as product backlog items (for example, bug fixes, refactoring enablers, or time-boxed spikes) and then refined and ordered alongside features.
Given fixed capacity and sprint planning tomorrow, the best next step is to ensure these items are visible, sized/refined enough to compare, and ordered by the product owner using factors such as customer impact, risk, and impediment to future delivery. This enables an intentional sprint selection rather than “leftover time” fixing, which typically hides the cost of quality and increases delivery risk.
Making defects and technical debt visible as backlog items enables the product owner to prioritize them against feature work based on value, risk, and impact.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project team is trying to reduce cycle time in a customer onboarding process. The project manager wants to first generate as many improvement ideas as possible and then quickly make the results easier to understand by organizing them into meaningful themes.
Which TWO actions should the project manager take? (Select TWO)
Correct answers: C, F
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The best approach is to separate divergent thinking from convergent organization. Brainstorming is used first to generate many possible options quickly without judging them. Affinity grouping is then used to cluster those ideas into themes so the team can see patterns and decide what to analyze or prioritize next.
This situation calls for two complementary problem-solving techniques used in sequence. First, use brainstorming to generate a large number of potential improvements by encouraging participation and capturing ideas without evaluating them during generation. Next, use affinity grouping (often captured as an affinity diagram) to organize the raw ideas into logical clusters based on natural relationships.
A practical flow is:
Key takeaway: brainstorming creates options, while affinity grouping structures the output so it can be understood and acted on.
Brainstorming rapidly generates a broad set of options by encouraging idea volume before evaluation.
Affinity grouping organizes many ideas into themes so patterns and focus areas become clear.
Topic: Project Management Fundamentals and Core Concepts
You are supporting a hybrid CRM implementation. The product owner says the next step is to quickly align stakeholders on what “done” means for a high-priority feature before it can be decomposed and planned.
Exhibit: Issue log (excerpt)
ID: ISS-12
Item: Acceptance criteria conflict for "Customer Data Export"
Details: Sales wants 1-click export; Compliance requires audit log + approval
Impact: Story cannot be finalized; risk of rework
Stakeholders: Sales Ops, Compliance, IT Security
Due: Before next backlog refinement (3 business days)
Which meeting type is most appropriate to address this issue?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The exhibit shows conflicting stakeholder needs and unclear acceptance criteria that block finalizing the work. A facilitated workshop brings the right SMEs together to negotiate trade-offs, clarify requirements, and agree on testable acceptance criteria within the short time window. This directly enables refinement and planning.
The core need in the issue log is not routine coordination or executive governance; it is collaborative problem-solving to resolve conflicting requirements and define clear acceptance criteria.
A workshop is the best fit because it is a facilitated working session designed to:
A standup is a short cadence event for synchronizing team progress and impediments, not negotiating requirement conflicts with external stakeholders. A steering review is used when escalation or governance decisions (e.g., major scope/budget trade-offs) are needed. The key takeaway is to match meeting type to the decision/work outcome required.
A workshop is best for collaboratively resolving conflicting needs and agreeing on shared acceptance criteria.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project team holds a 60-minute meeting at the end of each two-week iteration to discuss what went well, what problems occurred, and what to change. They capture the outcomes as lessons learned and immediately adjust their workflow for the next iteration.
Which practice does this BEST describe?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: This is an iteration retrospective: a regular inspection-and-adaptation event where the team reflects on how they work, records lessons learned, and commits to specific improvements. The key indicator is that changes are applied immediately to the next iteration’s way of working, supporting continuous improvement throughout the project.
Continuous improvement means capturing lessons learned frequently and turning them into concrete changes to how the team works. In agile and hybrid delivery, the primary mechanism for this is the iteration (sprint) retrospective, typically held at the end of each iteration. The team inspects its processes and collaboration, identifies root causes and improvement ideas, documents the lessons learned, and agrees on a small set of actionable changes to implement right away.
In contrast, product-focused feedback events validate what was built, and formal change control governs changes to baselines and scope—not day-to-day team process improvements. The takeaway: use retrospectives to institutionalize lessons learned and implement improvements continuously, not just at project closeout.
A retrospective is a recurring team event focused on capturing lessons learned and implementing process improvements in the next iteration.
Topic: Business Analysis Frameworks
A predictive project is implementing a new CRM system with a signed-off scope statement and requirements package. Midway through execution, a sales director asks the business analyst (BA) to “just add” three new dashboard reports that were not discussed during requirements workshops. The project manager is concerned about scope creep and wants a fact-based way to decide whether these requests belong in the approved scope or require a formal change.
Which artifact should the BA use to best support scope definition and avoid scope creep in this situation?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: To prevent scope creep, the BA should use an artifact that ties requested work back to what was approved and why. A requirements traceability matrix provides objective trace links from requirements to scope elements and business objectives, making it clear when a new request is out of baseline and must go through change control.
A BA supports scope definition by making requirements clear, testable, and aligned to business needs, and by maintaining control over how requirements evolve. In a plan-based project with signed-off scope, the key to avoiding scope creep is to verify whether a new request is already represented in the approved requirements and scope baseline.
A requirements traceability matrix (RTM) helps by:
If the new dashboards cannot be traced to an approved scope element, they should be treated as a change rather than “just added.”
An RTM links each requirement to approved scope and business objectives, helping identify additions that require formal change control.
Topic: Business Analysis Frameworks
A business analyst is supporting a hybrid project where requirements are refined each iteration. Several key stakeholders rotate in and out, and the sponsor is concerned that future scope discussions will lack context for why requirements were accepted or rejected.
Which artifact should the business analyst maintain to record the decisions and assumptions that affect requirements and scope?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: A decision and assumption log captures what was decided, when, by whom, and the assumptions that influenced the decision. In a hybrid environment with stakeholder turnover and ongoing refinement, this provides continuity and reduces rework and scope disputes by preserving rationale behind requirement choices.
The core need in this scenario is continuity of requirement rationale as people change and requirements evolve. A decision and assumption log is designed to document decisions that influence requirements and scope (for example, acceptance/rejection of a requirement, priority calls, and constraints/assumptions that shaped those decisions). Keeping this log current supports stakeholder communication by enabling quick, consistent answers to “why did we choose this?” and “what assumption was that based on?” during future reviews and change discussions.
Key takeaway: traceability and change control artifacts are helpful, but they don’t reliably capture the decision rationale and assumptions that prevent repeated debates.
It provides a single, maintainable record of requirement-related decisions and their underlying assumptions for later reference.
Topic: Business Analysis Frameworks
On a hybrid project to build a customer self-service portal, a business analyst must communicate approved requirement changes during execution. Key stakeholders include a time-constrained sponsor who prefers concise summaries, a distributed product owner, a development team that collaborates daily, and a compliance officer who requires an auditable record.
Which communication approach should the business analyst NOT use?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: Communication tools should match stakeholder needs for speed, accessibility, and traceability. In this scenario, at least one stakeholder requires an auditable record of requirement changes, and others need predictable, consumable updates. Using chat as the only channel creates weak traceability and increases the risk of missed or disputed decisions.
Choosing a communication channel/tool is about fit-for-purpose delivery of the message to the audience. Here, requirement changes must be accessible to distributed stakeholders, consumable by a time-constrained sponsor, and traceable for compliance.
A good approach typically ensures:
Relying on an informal chat stream as the only method is risky because it is easy to lose context, hard to baseline, and often insufficient as an audit trail compared with documented repositories, minutes, and planned summaries.
Chat-only communication lacks reliable version control and an auditable record needed by key stakeholders.
Topic: Predictive, Plan-Based Methodologies
A predictive project is installing electrical wiring in a new hospital wing. Once drywall is installed (a fixed milestone on the schedule), most wiring defects will be hidden and rework will be expensive and disruptive.
Which quality metric and control activity should the project manager include in the quality management plan to best manage this risk?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: When work will be concealed and rework is costly, the quality management plan should define objective, preventive controls before the concealment milestone. A first-pass inspection (or acceptance) rate tied to scheduled pre-drywall inspections provides early detection and measurable performance of the control activity. This directly supports planning quality control activities into the predictive schedule.
A quality management plan specifies measurable quality metrics and the control activities used to assess conformance. In this scenario, the decisive factor is that defects will be hidden after drywall, making late detection expensive. The best approach is to plan “hold points” in the schedule before concealment and define a metric that shows how often the work meets requirements the first time.
A practical setup is:
This prevents defects from being built-in, rather than discovering them at the end when correction is most disruptive.
Because defects become hard to detect after drywall, scheduled hold-point inspections with a first-pass yield metric prevent hidden rework.
Topic: Business Analysis Frameworks
A hybrid project team just completed a release review. Several requirements were accepted and deployed, two were deferred to the next release due to schedule limits, and one requirement was removed after stakeholders agreed it no longer provides value. The sponsor has also requested that the team be able to trace every original requirement to its current delivery decision.
What should the business analyst do next to best optimize traceability with minimal disruption to upcoming planning?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: After delivery decisions are made, the traceability artifacts must reflect the current state of each requirement. Updating the RTM and/or product backlog with each item’s disposition (delivered, deferred, removed) and linking it to the release keeps stakeholders able to trace outcomes back to the original requirements. Doing this immediately supports near-term planning and reduces rework.
The requirements traceability matrix (RTM) and the product backlog are living artifacts that should reflect delivery decisions as they occur. When requirements are accepted, deferred, or removed, updating these artifacts maintains a clear, auditable chain from the original requirement to its current outcome.
In this scenario, the best next step is to update traceability by capturing for each requirement:
This optimizes traceability while directly supporting the next planning cycle, instead of creating parallel records or delaying updates.
Recording delivered/deferred/removed status and linking to the release preserves end-to-end traceability for each requirement.
Topic: Predictive, Plan-Based Methodologies
A project manager is using a predictive (plan-based) approach to manage a construction project. The sponsor asks for the core project documents the team will use to plan and control the work.
Which item is NOT a common predictive project artifact for this purpose?
Best answer: C
What this tests: Predictive, Plan-Based Methodologies
Explanation: Predictive projects commonly use plan-based artifacts such as a WBS, baselines (including the cost baseline), and periodic status reports to plan and control scope, schedule, and cost. A product backlog is an adaptive artifact used to manage evolving work through prioritization and iteration. That makes it the only item that does not fit a predictive document set.
In predictive (plan-based) projects, planning and control rely on artifacts that decompose and baseline the work, then report performance against those plans. A WBS organizes the total scope into manageable work packages; baselines (such as the cost baseline) provide the approved plan for measuring variance; and status reports communicate progress, issues, and performance information to stakeholders. A product backlog, by contrast, is an agile artifact used to maintain and reorder upcoming work as priorities change across iterations, so it is not a typical predictive artifact for planning/control.
A product backlog is primarily an agile artifact used to manage and prioritize iterative work, not a typical predictive planning/control document.
Topic: Business Analysis Frameworks
A product team uses Scrum. The next sprint starts tomorrow, and several high-priority user stories depend on new screen designs. In backlog refinement, developers say the stories are ambiguous and QA says test cases cannot be written. The UX designer has draft wireframes but no agreed acceptance criteria. The product owner wants the team to start the sprint on time with minimal rework.
What should the business analyst do next to best optimize this objective while working within the Scrum approach?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: In Scrum, requirements are refined collaboratively and just in time so the team can confidently commit to sprint work. A focused working session with UX, development, QA, and the product owner turns ambiguous stories and draft wireframes into shared understanding and testable acceptance criteria. This best supports starting on time while minimizing downstream churn and rework.
Agile methodologies like Scrum emphasize collaborative refinement of requirements rather than handoffs. When UX artifacts (wireframes) exist but stories are still ambiguous, the BA helps the team converge on a “ready” state by coordinating a quick, cross-functional clarification.
A good next step is to run a timeboxed session with the product owner, UX, developers, and QA to:
This keeps analysis lightweight and iterative while ensuring sprint commitments are based on shared understanding. The key takeaway is to collaborate directly with UX and delivery roles to make requirements and acceptance criteria actionable before sprint commitment.
This creates shared understanding with UX and delivery roles and produces testable acceptance criteria just in time for sprint commitment, reducing rework without heavy upfront documentation.
Topic: Project Management Fundamentals and Core Concepts
On a predictive project, the development lead and QA lead are in conflict about the schedule for end-to-end testing. The dev lead wants to shorten testing to protect a committed go-live date, while the QA lead insists the current plan is the minimum needed to meet quality expectations. The disagreement is becoming personal in emails and is starting to delay decisions.
As the project manager, what is the best next step?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The best next step is to use a collaborative (problem-solving) approach by bringing both parties together to understand interests and constraints and agree on a solution. The issue is important to both quality and schedule, and the relationship is starting to degrade, so a win-win resolution is preferred over quick but fragile fixes.
Conflict resolution techniques should match the situation. Here, the conflict is already affecting decision-making and team relationships, and the outcome impacts both quality and schedule. A collaborate/problem-solve approach is the best next step because it directly addresses root causes and aims for a solution both parties can commit to.
A practical collaborate step is to facilitate a focused discussion to:
Compromise, smoothing, forcing, or avoiding may appear faster, but they typically either leave key concerns unresolved or escalate unnecessarily for an issue the team can work through.
Collaboration addresses the underlying needs of both leads and seeks a durable solution without premature escalation.
Topic: Agile Frameworks/Methodologies
A Scrum team is midway through a 2-week sprint. The product owner says, “The burndown looks off, but I can’t tell if we’re behind.” The chart shown only includes a line labeled “Remaining Work,” and the team reports they updated it yesterday.
What should the project practitioner ask to verify first before interpreting progress toward the sprint goal?
Whether the y-axis is based on story points, hours, or number of tasks
Whether the team is planning to add more scope later in the sprint
Whether a release burndown is also being maintained
Whether the team’s velocity is higher than last sprint
A. Whether a release burndown is also being maintained
B. Whether the y-axis is based on story points, hours, or number of tasks
C. Whether the team is planning to add more scope later in the sprint
D. Whether the team’s velocity is higher than last sprint
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: To use a burndown chart to judge progress toward an iteration goal, you first need to know what the chart’s “remaining work” line represents. Confirming the unit on the y-axis (e.g., hours vs. story points) ensures the data is interpretable and comparable to the planned/ideal trend for the sprint.
A burndown (or burnup) chart is only useful for tracking iteration or release progress if the underlying measure is understood and consistently applied. In the scenario, the only visible information is a “Remaining Work” line; without knowing what it counts (hours, story points, tasks), you cannot reliably interpret whether the team is on track, because the rate of change and any comparison to an ideal line depends on the unit and how it is updated. After confirming the unit/measure, you can then validate update cadence, scope changes during the sprint, and whether the chart matches the sprint goal being tracked. The key takeaway is to verify the chart’s metric definition before drawing conclusions from its trend.
You must confirm what “remaining work” is measuring (and its unit) to interpret the slope and compare it to the ideal trend.
Topic: Project Management Fundamentals and Core Concepts
Which term best describes performing planned quality activities (such as process audits and continuous improvement) and documenting the results to provide confidence that project processes will meet quality standards?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: This describes the work of executing the quality management plan through proactive activities like audits and process analysis, then documenting what was found. The purpose is to increase confidence that the project’s processes will produce deliverables that meet requirements, and to capture quality-related results in reports and updates.
The concept is Manage Quality (often associated with quality assurance). It is the process of carrying out the planned quality activities defined in the quality management plan and documenting outcomes so stakeholders have confidence the project’s processes are capable of meeting standards.
Typical Manage Quality work includes:
In contrast, Control Quality is more focused on inspecting/testing deliverables and verifying they meet acceptance criteria.
Manage Quality focuses on executing planned quality activities and recording results to confirm processes are effective and compliant.
Topic: Project Management Fundamentals and Core Concepts
A department lead asks you to “set up and manage a new process for publishing the company’s sales dashboard” and wants to know whether to treat the work as a project or as ongoing operations. The request includes no end date and no description of what “new process” means.
What should you ask FIRST to determine whether this is a project or ongoing operations?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The most reliable first check is whether the effort is temporary and produces a unique outcome. If the dashboard publishing work is a one-time setup or redesign with an end date, it is a project; if it is continuous, repeatable publishing each period, it is ongoing operations. Confirming temporariness and a defined finish enables that classification quickly.
To distinguish a project from ongoing operations, start by clarifying whether the work is a temporary effort that creates a unique product, service, or result. In this scenario, “set up and manage a new process” could mean a one-time implementation (project) or it could be routine, recurring publication work (operations). Asking whether there is a defined start and finish and a one-time deliverable establishes whether the effort is temporary.
If the answer is “implement a new publishing process by a certain date,” it aligns with a project. If the answer is “publish/update the dashboard every month indefinitely,” it aligns with operations. Budget, tools, and stakeholder details are important later, but they do not determine whether the work is temporary or ongoing.
Key takeaway: classify by temporariness and uniqueness before planning details.
Projects are temporary efforts that create a unique result, so confirming a defined end and one-time outcome is the first discriminator.
Topic: Predictive, Plan-Based Methodologies
A predictive project is tracking 3 weeks behind an approved schedule baseline. The sponsor will not accept a later end date. The project manager proposes starting construction on the first two building floors while detailed design for the upper floors is still being finalized, acknowledging this could cause rework if drawings change.
Which schedule compression technique does this describe?
Best answer: B
What this tests: Predictive, Plan-Based Methodologies
Explanation: The situation describes overlapping design and construction that were originally planned in sequence. This is fast tracking, a schedule compression technique that can shorten duration without necessarily adding resources. The primary tradeoff is increased risk, coordination complexity, and potential rework if upstream work changes.
Schedule compression is used to shorten the project schedule without changing the project end date. In this scenario, the team begins construction before all design is complete, which overlaps activities that would normally be done one after another. That approach is fast tracking.
Fast tracking typically:
By contrast, crashing shortens the schedule by adding resources or paying for expedited work, which usually increases cost and can introduce diminishing returns.
It overlaps activities that were planned sequentially, trading higher risk of rework for time.
Topic: Predictive, Plan-Based Methodologies
A predictive project uses earned value management (EVM) to validate cost performance at the end of month 4. The status report shows EV (earned value) = $180,000 and AC (actual cost) = $200,000.
Which statement best validates the project’s cost performance using cost variance (CV)?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: Cost variance (CV) is calculated as earned value minus actual cost: \(CV = EV - AC\). Using the provided values gives a negative result, which indicates the project has spent more than the value of the work performed (over budget).
In EVM, cost variance (CV) is a direct metric used to validate cost performance for work performed to date. Compute it from the status data:
A negative CV means actual cost exceeds earned value, so the project is over budget by the magnitude of the variance at this point in time. A positive CV would indicate under budget. Don’t confuse cost variance (CV) with schedule status, which is assessed with schedule variance (SV) or schedule performance index (SPI).
Cost variance is EV − AC, so $180,000 − $200,000 = -$20,000, indicating an over-budget condition.
Topic: Agile Frameworks/Methodologies
You are the project manager serving as the Scrum Master for a new agile team in Sprint 2. Halfway through the sprint, a senior stakeholder starts assigning tasks directly to individual developers and demands a daily status email.
Constraints:
What is the BEST next action you should take?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: Servant leadership in agile emphasizes enabling the team to perform by removing impediments, protecting focus, and reinforcing agile roles. The best next step is to coach the system: help the team align on a working agreement for intake of work and then address the stakeholder’s behavior to stop direct tasking. This supports team autonomy while keeping prioritization with the Product Owner.
In agile, a servant leader improves team performance by facilitating, coaching, and removing obstacles rather than directing work. In this scenario, the interruption is causing confusion and reducing focus, putting the sprint goal at risk. The servant-leader response is to (1) listen to the team, (2) reinforce clear role boundaries (work is prioritized via the Product Owner and the team pulls work), and (3) engage the stakeholder to change the interaction pattern so the team can regain flow.
A key distinction is that protecting the team’s focus and clarifying the work intake mechanism is different from taking over prioritization or creating extra reporting overhead.
This models servant leadership by coaching self-organization, protecting the team’s focus, and removing an impediment without taking ownership of prioritization.
Topic: Project Management Fundamentals and Core Concepts
A project team is finishing a hybrid implementation of a new customer support portal. After go-live, the Operations department will own the portal, handle incidents, and manage vendor support. The project manager is asked to provide the best evidence that the deliverables are ready to be transitioned for ongoing ownership.
Which metric/evidence/artifact best validates readiness for the transition to Operations?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Transition readiness is validated by evidence that the receiving organization has accepted the deliverable and can support it operationally. A signed operational handover and acceptance checklist demonstrates that required knowledge transfer, documentation, support arrangements, and acceptance criteria for ownership transfer have been met and formally approved by Operations.
Transitioning deliverables to operations/business ownership requires more than “project work complete”; it requires proof that the receiving group is prepared to take accountability for day-to-day support. The strongest validation is formal acceptance of the handover package, typically documented through an operational handover/transition checklist signed by Operations.
This type of evidence commonly confirms items such as:
Completion percentages and “green” reports are progress indicators, but they do not prove that Operations has accepted ownership or can sustain the deliverable after the project ends.
Operations sign-off on a completed handover checklist confirms they accept ownership and are ready to support the deliverable.
Topic: Agile Frameworks/Methodologies
A Scrum team is about to start sprint planning. The top user story is ranked highest in the product backlog, but it has unclear business rules and no acceptance criteria. The developers say they cannot estimate it accurately.
What is the best next step?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: In Scrum, the product owner is accountable for the product backlog, including clarifying backlog items and defining or ensuring clear acceptance criteria. If a top item is not ready to estimate, the next step is to collaborate to refine it or select another ready item for sprint planning so the team can make a reliable forecast.
This situation is a backlog readiness problem. The product owner is accountable for maximizing value and for the content and ordering of the product backlog, which includes ensuring items are sufficiently understood for planning (often via backlog refinement with the developers). The developers decide what they can take into the sprint and need clear acceptance criteria to estimate and plan.
A practical next step is:
The scrum master supports the process and facilitation, but does not own requirements details or write acceptance criteria as a substitute for the product owner.
The product owner is accountable for clarifying and ordering backlog items so the team can select and estimate ready work.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project team runs a short retrospective at the end of each iteration and identifies process improvements (for example, adding peer reviews to reduce rework). After three iterations, the project manager wants to validate that continuous improvement is actually happening—not just being discussed.
Which evidence best validates that lessons learned are being captured and the changes are being implemented?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: To validate continuous improvement, you need evidence that lessons learned were recorded and that resulting changes were carried out. A lessons learned register that includes improvement action items with owners and completion status shows follow-through and makes implementation transparent over time. Notes and counts show activity, not realized change.
Continuous improvement is demonstrated when the team captures what was learned and then implements a specific change based on that learning. The most credible validation is an artifact that documents the lesson and shows the resulting improvement work being assigned, tracked, and completed (often with accountability fields like owner and status). In the scenario, the goal is to prove that retrospective insights (e.g., peer reviews) moved beyond discussion into practice.
Good validation evidence typically includes:
Meeting outputs or volume-based counts can be produced without any actual process change being adopted.
A lessons learned register that tracks improvement actions through completion provides direct evidence of both capture and implementation.
Topic: Predictive, Plan-Based Methodologies
A project is using a predictive schedule to implement a new HR system. The project manager is defining logical relationships between activities (predecessor -7 successor) to build the network diagram. Which statement about dependency types is INCORRECT?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: Dependency types describe which event (start or finish) of a predecessor constrains which event of a successor. Finish-to-start constrains a successor’s start based on a predecessor’s finish, while finish-to-finish constrains a successor’s finish based on a predecessor’s finish. The incorrect statement mixes up these two relationships.
In activity sequencing, dependencies are defined by the event in the predecessor that drives the event in the successor.
A common error is describing an FF relationship using FS wording (constraining the successor’s start instead of its finish).
That description matches finish-to-start (start is constrained by a finish), not finish-to-finish (finish is constrained by a finish).
Topic: Predictive, Plan-Based Methodologies
A project manager has been assigned to a predictive project to implement a new inventory management system across three warehouses. The project has a fixed budget and a hard go-live date in 6 months. Several stakeholders have requested additional reporting features, but the sponsor wants scope agreed before work begins.
The project charter has been approved and the project manager is starting planning. What is the BEST next action?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: Because the charter is approved and the sponsor wants scope agreed before execution, the project manager should perform key planning work: define and validate what will be delivered, plan how it will be delivered, and set baselines for scope and schedule. These baselines are essential for managing a fixed budget and a hard deadline in a predictive approach.
In a predictive (plan-based) project, planning focuses on defining the work and creating an integrated, approved plan that can be used to guide execution and to measure performance. With the charter approved, the project manager typically proceeds to plan the scope in detail (requirements, scope statement, WBS), develop the schedule and cost plans, and then establish baselines (at minimum scope, schedule, and cost) within the project management plan. This is especially important when there is a fixed budget and a hard go-live date, because the baselines provide a controlled reference for monitoring and for evaluating any requested additions.
Requested new features should be handled through scope definition and prioritization during planning, and then through formal change control once baselines are approved.
Starting build work or convening change control before baselines exist undermines the purpose of predictive planning.
In predictive planning, the next step is to define scope and develop the integrated plan so baselines can be set before executing and controlling changes.
Topic: Business Analysis Frameworks
After a requirements elicitation workshop for a new customer portal, several questions were left open (data retention rules, integration details, and who approves content). The sponsor asks how you will ensure these items are tracked and followed up with clear accountability.
Which artifact best validates that action items have owners and due dates and that follow-up is progressing?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: To validate follow-through after elicitation, you need evidence that each open item is assigned to a specific owner with a due date and that progress is being tracked. An action item log (often captured in meeting minutes and maintained over time) directly shows accountability and status, making it the strongest proof of follow-up progress.
After elicitation, unresolved questions and next steps must be converted into actionable commitments so they do not get lost. The best validation artifact is an action item log (or meeting minutes section) that records each action item with an owner, a due date, and a current status; this enables follow-up, escalation, and transparent communication with stakeholders.
A practical action item log typically includes:
Materials like slides or raw notes can show what was discussed, but they do not validate that accountability and follow-up are happening. The key takeaway is to use an artifact that makes ownership and due dates explicit and trackable over time.
This provides traceable evidence of assigned ownership, due dates, and follow-up status for each elicitation action item.
Topic: Project Management Fundamentals and Core Concepts
In root cause analysis, what best describes the purpose of the 5 Whys technique?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The 5 Whys is a root cause analysis technique that uses repeated “why?” questions to drill down from an observed problem to the underlying cause. The focus is on uncovering the cause-and-effect chain rather than immediately proposing solutions or categorizing data.
The 5 Whys is a simple root cause analysis method used when a team sees a problem (a symptom) and needs to discover what is actually creating it. Starting with the problem statement, the team asks “Why did this happen?” and uses the answer as the basis for the next “why?” question. After several iterations (often around five, but as many as needed), the team typically identifies an underlying cause that can be addressed with a corrective action. The key is that each answer should be evidence-based and logically linked to the previous step, so the group doesn’t stop at superficial explanations.
It iteratively probes causes-and-effects so the team can move past symptoms to an underlying cause.
Topic: Business Analysis Frameworks
A hybrid project team is refining requirements for a customer portal. A key stakeholder states: “Users should be able to log in quickly.” During review, the team agrees the wording is ambiguous and cannot be objectively tested.
Which business analysis artifact/technique is the best choice to make this requirement testable and verifiable?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: Testable and verifiable requirements must have objective, measurable conditions that allow pass/fail evaluation. Adding clear acceptance criteria (for example, a time threshold and measurement conditions) turns “quickly” into something that can be validated. This approach works in predictive, agile, and hybrid methods.
The core issue is requirement quality: “log in quickly” is not testable because it lacks measurable targets and clear verification conditions. The most direct way to make it testable and verifiable is to define acceptance criteria that specify observable outcomes and measures (for example, response time, under what load, and how it will be measured).
In practice, you refine the requirement by adding criteria such as:
Roadmaps, traceability, and stakeholder registers are useful BA artifacts, but they do not, by themselves, convert ambiguous wording into objectively verifiable requirements.
Acceptance criteria make the requirement verifiable by specifying objective measures and conditions for acceptance.
Topic: Project Management Fundamentals and Core Concepts
A project coordinator is compiling the weekly status report for a predictive infrastructure project. The coordinator discovers a confirmed vendor delay that will push a key milestone by two weeks. The sponsor privately asks the coordinator to “keep the report green” until the steering committee meeting next month to avoid scrutiny.
The coordinator follows ethical and professional standards and reports the delay and its impact accurately.
What is the most likely near-term impact of this decision?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Ethical stakeholder communication requires honest, complete, and timely reporting of project status. By reporting the confirmed delay and its impacts, the coordinator enables the sponsor and steering committee to make informed near-term decisions, such as approving corrective actions or initiating formal change control. This preserves professionalism and supports responsible governance.
Ethics and professionalism in project communications emphasize honesty, responsibility, and transparency—especially in status reporting used for governance decisions. In this scenario, the sponsor’s request would intentionally misrepresent known schedule performance, which can lead stakeholders to make immediate decisions based on false information.
Accurately reporting a confirmed delay typically triggers near-term actions such as:
The key takeaway is that truthful reporting supports timely decision-making; “hiding” bad news may feel easier, but it undermines effective oversight.
Honest reporting enables stakeholders to make immediate, informed decisions (for example, escalate, replan, or submit a change request).
Topic: Predictive, Plan-Based Methodologies
A sponsor asks the project manager to provide the document that formally authorizes the project, names the project manager, and summarizes high-level scope, major milestones, and the initial funding level so work can begin. Which predictive artifact best matches this need?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: In predictive projects, the project charter is the artifact used to formally authorize the project and grant the project manager authority to apply resources. It captures high-level scope and milestone information and often includes an initial summary budget/funding level so the project can be initiated.
The core concept is authorization versus planning detail. The project charter is created/issued by the sponsor (or initiator) to formally start the project and empower the project manager. It contains high-level information such as purpose, measurable objectives, high-level scope and requirements, key stakeholders, major milestones, and a summary budget or funding approach.
A WBS decomposes approved scope into deliverable-oriented work packages for planning and control. A schedule baseline is the approved time-phased plan (planned start/finish dates) used to measure schedule performance. A status report communicates current progress and issues but does not authorize starting the project. Key takeaway: the artifact that “starts the project” is the charter; the others manage and report the work after initiation.
The charter formally authorizes the project and provides high-level information and authority to start work.
Topic: Business Analysis Frameworks
A product manager is planning the next two releases for a hybrid software project. The delivery team has a fixed capacity of about 40 story points per sprint, and only two sprints remain before an end-of-quarter contractual deadline for a customer-facing feature set.
Which artifact is the BEST choice to sequence what goes into each release while balancing the team’s capacity with the business deadline?
Best answer: B
What this tests: Business Analysis Frameworks
Explanation: A release plan is used to decide and communicate which features will be delivered in each planned release, explicitly considering available capacity and required dates. In this scenario, the decisive factor is the fixed end-of-quarter deadline combined with limited team capacity, which requires capacity-based release sequencing.
When sequencing releases, a product roadmap is usually too high-level (themes and direction), while a release plan is the artifact that maps prioritized backlog items to specific releases and target dates using realistic capacity assumptions. Here, the team’s capacity (about 40 points per sprint) and the immovable end-of-quarter commitment create a clear need to allocate scope across the next two releases and, if necessary, defer lower-value items. A release plan supports this by:
Key takeaway: use a release plan to balance capacity constraints with business deadlines at the release level.
A release plan allocates prioritized scope into specific releases using known capacity and fixed dates.
Topic: Business Analysis Frameworks
A project team is updating an internal mobile app used by about 200 field technicians across four regions. You need to elicit requirements about which features are most valuable and collect pain points within one week. Technicians have limited availability during business hours, and the sponsor wants input that can be summarized quantitatively without requiring travel or long meetings.
What is the BEST next elicitation technique to use?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: A survey is the best fit when you need fast input from a large, geographically dispersed population and want results that can be analyzed quantitatively. It minimizes disruption to technicians’ work schedules and avoids the logistics of travel or lengthy meetings. Given the one-week constraint, it provides the broadest coverage quickly.
Selecting an elicitation technique depends on constraints such as the number of stakeholders, time available, access to users, and the type of data needed. In this scenario, the team needs input from a large user base across multiple regions within one week, with limited availability during business hours, and the sponsor wants results that can be summarized quantitatively. A structured survey fits these constraints because it scales to many respondents, can be completed asynchronously, and produces comparable data (rankings, ratings, frequency of pain points). Interviews, observation, and workshops can provide deeper insight, but they are harder to schedule and do not scale as efficiently under tight time and access limits. The key takeaway is to use surveys for broad, fast, quantifiable input from many stakeholders.
A survey efficiently gathers quantifiable input from many dispersed users with minimal time commitment.
Topic: Project Management Fundamentals and Core Concepts
You are managing a predictive project to roll out new point-of-sale software to 40 stores. Midway through execution, the Operations director emails you asking to add an offline mode, saying it is “mandatory,” while the Finance manager replies that no additional funding will be approved. Before you decide whether to proceed, what should you clarify first?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The situation contains conflicting direction, so the first step is to determine which stakeholder role has legitimate decision authority over scope and funding. Stakeholder influence depends on their power and accountability (for example, sponsor or designated change approval body). Once authority is clear, you can evaluate impacts and route the request appropriately.
When stakeholders give competing instructions, the project manager should not treat the loudest voice as the decision-maker. First, clarify stakeholder roles and influence: who is accountable for project funding and who is authorized to approve changes to scope, schedule, and cost (often the project sponsor and/or a defined change control authority). In this scenario, Operations is asserting a requirement while Finance is constraining funding; the correct next move is to confirm who has final approval rights and the escalation path. After that, you can gather estimates, document the change request, and facilitate a decision consistent with governance and stakeholder influence. The key takeaway is to verify decision authority before analyzing or committing to change work.
You must confirm the key stakeholder decision authority (typically the sponsor/change control authority) before acting on conflicting requests.
Topic: Project Management Fundamentals and Core Concepts
A company is reorganizing its delivery work. The initiative includes:
Which term best describes the coordinated set of related work managed together to achieve benefits that would not be available if managed individually?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The coordinated management of multiple related efforts to achieve a combined benefit describes a program. A program aligns and oversees related components so their interdependencies are managed and benefits are realized. This differs from a single temporary endeavor (project) or a broader investment grouping (portfolio).
A program is a group of related projects, subsidiary programs, and other work managed in a coordinated way to obtain benefits and control not available from managing them individually. In the scenario, the mobile app launch and the call-center training update are distinct efforts, but they are interdependent and are being managed together to realize a single business benefit.
A project is a temporary endeavor that creates a unique product, service, or result (for example, just the mobile app). A portfolio is a collection of projects, programs, and operations managed as a group to achieve strategic objectives; items in a portfolio may be unrelated except for strategy and funding. Key takeaway: coordinated benefit-focused management across related components indicates a program.
A program manages related projects and work in a coordinated way to obtain benefits not available from managing them separately.
Topic: Project Management Fundamentals and Core Concepts
A project team is implementing a new internal HR self-service portal. Go-live is planned for next week, and the Operations team will take over monitoring and support after deployment.
Which TWO actions best support transition planning by verifying readiness for handover and operational acceptance? (Select TWO)
Correct answers: B, F
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Readiness for handover requires confirming both product acceptance and operational ability to support the solution. Verifying acceptance criteria and obtaining formal acceptance shows the deliverable is acceptable to the customer/sponsor. An operational readiness review with Operations confirms the receiving organization can run, support, and maintain the solution after transition.
Transition planning focuses on verifying that the solution is acceptable and that the receiving organization is prepared to own it. In the scenario, readiness should be verified from two angles:
Activities like documenting lessons learned or archiving files are valuable for closure, but they do not directly verify that the solution is ready to be handed over and supported in operations.
An operational readiness review confirms support processes, training, and support assets are in place before handover.
Formal acceptance verifies the solution meets agreed criteria and is ready to be accepted by the customer/sponsor.
Topic: Business Analysis Frameworks
A hybrid project is delivering an internal finance reporting tool for a regulated organization. An internal audit is scheduled in 6 weeks and will require evidence that approved requirements were tested and formally accepted. During UAT, the team discovers several test cases are not clearly tied to specific requirements, and the product owner is requesting sign-off at the end of the next iteration.
What is the BEST next action to ensure requirements are traceable through testing to acceptance?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: To satisfy an audit, the team needs objective evidence connecting approved requirements to verification/validation activities and to formal acceptance. A requirements traceability matrix (or equivalent trace artifact) is designed to maintain this linkage and demonstrate coverage. Updating it now resolves the immediate gap before the upcoming sign-off and audit.
The core need is audit-ready, end-to-end traceability: each approved requirement should map forward to how it is tested (test cases), the outcomes (pass/fail results), and the acceptance record (who accepted and when). The requirements traceability matrix (RTM) is a common BA artifact that provides this chain of evidence and highlights gaps such as untested requirements or tests that do not validate a requirement.
Best next action in this situation is to update the RTM (or equivalent trace tool) so UAT execution and upcoming sign-off produce defensible, reviewable records. Improving test documentation or restating requirements may help quality, but they do not, by themselves, ensure requirement-to-test-to-acceptance traceability for the audit.
An updated RTM provides end-to-end traceability from requirements through verification/validation results to documented acceptance for auditability.
Topic: Business Analysis Frameworks
A business analyst is supporting a hybrid project to roll out a new customer self-service portal. Requirements workshops have started, but the project sponsor asks how the team will confirm they have identified and involved the right people (subject matter experts, end users, and decision makers) for ongoing elicitation and approvals.
Which artifact best validates this?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: To validate that the correct SMEs, end users, and decision makers were identified and engaged, you need evidence that explicitly names stakeholders and clarifies their roles and decision authority. The stakeholder register is designed to capture this role-based information and can be reviewed/confirmed with the sponsor or product owner to ensure the right representation for elicitation and approvals.
In business analysis, correctly identifying SMEs, end users, and decision makers means knowing not just who participated, but who has the needed domain knowledge, who will use the solution, and who can approve/commit the organization. The artifact that best validates this is one that explicitly documents stakeholder identities and their roles/level of authority so the team can confirm coverage and avoid gaps.
A stakeholder register typically records:
Attendance records or delivery/performance charts may show activity or progress, but they do not confirm that the right roles are represented and empowered to make decisions. The key takeaway is to validate engagement using an artifact that ties people to roles and authority.
A stakeholder register can document who the SMEs, end users, and decision makers are and their influence/decision authority.
Topic: Project Management Fundamentals and Core Concepts
A hybrid project team is investigating a recurring production outage that happens after each monthly release. During a problem-solving session, the team agrees to use the 5 Whys to move from the observed symptom to an underlying cause.
Which action should the team NOT do when applying the 5 Whys?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The 5 Whys is a root cause analysis technique intended to trace a problem back through cause-and-effect to an underlying process or systemic cause. Actions that shift the discussion to blame or personal fault reduce psychological safety and typically stop the analysis at a superficial level. The team should instead keep “why” questions anchored to facts and the work system.
In the 5 Whys, the team starts with a specific problem statement (the symptom) and asks “why?” repeatedly to reveal a chain of causes. The goal is to identify an underlying cause in the process, environment, or system that the team can change to prevent recurrence.
Good practice when using 5 Whys includes:
A blame-focused approach can lead to defensive answers and an unreliable “root cause,” whereas evidence-based, process-focused questioning supports a corrective action that prevents future outages.
The 5 Whys targets process/system causes, so blaming an individual short-circuits root cause analysis and can miss the underlying condition.
Topic: Agile Frameworks/Methodologies
A Scrum team is in iteration planning for a 2-week iteration. The product owner brings a mix of backlog items: a compliance fix needed this month, several usability enhancements, and one performance improvement. The team has already reviewed capacity but is debating what to select because the product owner says, “Just pull the top items and we’ll figure out the purpose later.”
What is the best next step?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: In iteration planning, the team and product owner first align on an iteration (sprint) goal that describes the value to be delivered. That goal then acts as the decision filter for selecting a coherent set of backlog items within capacity. Defining the goal after selecting items makes the selection less intentional and can reduce focus.
An iteration goal (often called a sprint goal) states the single, shared objective the team intends to achieve by the end of the iteration. Because it anchors the iteration’s purpose, it should be established collaboratively during planning before finalizing the iteration backlog.
A practical sequence is:
In this scenario, capacity is already reviewed but selection is unfocused; defining the goal next enables the team to choose a coherent set of items (for example, centered on compliance readiness or a specific user outcome) rather than a random “top of list” bundle.
The iteration goal provides a shared purpose that guides which backlog items to pull into the iteration.
Topic: Business Analysis Frameworks
A product team is building a customer self-service portal using an iterative approach. The sponsor wants a 6-month product roadmap showing major outcomes, while the team manages a detailed product backlog and holds weekly backlog refinement. The business analyst is asked to recommend practices that integrate roadmap planning with backlog management.
Which practice should the BA NOT recommend?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: A roadmap is a directional plan of outcomes and sequencing, while the backlog is a continually refined, ordered list of detailed work. Integrating the two means tracing backlog items to roadmap goals and routinely adjusting both as learning and stakeholder needs evolve. Locking the backlog conflicts with adaptive planning and undermines refinement.
Roadmap planning and backlog management should work as a connected system: the roadmap communicates intended outcomes over time (often as themes/epics and release windows), and the backlog translates those outcomes into detailed, ready work that is continuously ordered and refined. In an iterative environment, refinement is where new information (feedback, dependency discovery, capacity changes) is incorporated, and that may require reordering backlog items while keeping alignment to roadmap priorities.
Good integration practices include:
The key anti-pattern is treating the roadmap as a fixed commitment that prevents backlog reprioritization.
Freezing backlog order blocks ongoing reprioritization and refinement needed to keep the backlog aligned to changing roadmap assumptions.
Topic: Business Analysis Frameworks
Which activity is primarily a business analyst responsibility (rather than a project manager responsibility) on a project?
Best answer: B
What this tests: Business Analysis Frameworks
Explanation: Business analysts focus on eliciting, analyzing, documenting, and managing requirements to ensure the solution delivers business value. A key BA practice is traceability—maintaining links from requirements to design, build, test, and acceptance to control scope and validate outcomes.
Business analysts are primarily accountable for defining and managing requirements and ensuring they remain aligned to business needs throughout the project or product work. A common BA artifact is the requirements traceability matrix (RTM), which connects each requirement to its source and to downstream solution components (such as features, test cases, and acceptance). Project managers, in contrast, are primarily responsible for integrating and coordinating the project work—planning and maintaining baselines (scope/schedule/cost), facilitating governance such as change control, and managing delivery execution. Both roles collaborate closely, but traceability of requirements is most directly a BA responsibility because it supports validation and prevents uncontrolled scope changes. The closest confusion is mistaking “scope” ownership (PM) for “requirements” ownership (BA).
Managing and tracing requirements through to solution components is a core business analysis responsibility.
Topic: Business Analysis Frameworks
A hybrid project is implementing a new CRM. The scope baseline and approved requirements are complete, and the team is configuring features in short iterations.
During a stakeholder review, the Sales Director asks to add three new executive dashboards that were not in the approved requirements. The project manager asks the business analyst (BA) to help prevent scope creep.
What is the BA’s best next step?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: To avoid scope creep, the BA should ensure any new request is captured and evaluated against the approved scope and requirements. The next step is to document the change, use traceability to confirm the gap, analyze schedule/cost/value impacts, and route it through the agreed change/priority decision process before any work starts.
A BA supports scope definition by keeping requirements clear, agreed, and traceable to business objectives and deliverables. When a new feature is requested after requirements are approved, the BA helps prevent scope creep by treating it as a change, not as “extra work.”
A good next-step sequence is:
Only after approval should scope documents (and plans/backlog) be updated and work scheduled. The key takeaway is that evaluation and approval come before updating baselines or starting delivery.
Capturing the request and performing traceability and impact analysis supports scope definition and routes changes through the proper approval path.
Topic: Business Analysis Frameworks
You are the business analyst on a hybrid project to replace a company’s expense-reporting system. Stakeholder analysis shows:
The team has 3 weeks to finalize requirements for an upcoming vendor configuration workshop, and stakeholders have complained about “too many documents.” Which approach best tailors BA work products and communication to optimize alignment and adoption while meeting the time constraint?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: Stakeholder analysis is used to tailor both the BA deliverables and the communication method to what each stakeholder group values and can consume. The best approach provides decision-level summaries for high-power, low-time stakeholders, detailed requirements where technical execution depends on it, and just-enough end-user guidance to support adoption. It also directly addresses the constraint that stakeholders want fewer, more targeted documents.
Tailoring BA work products means selecting the minimum set of artifacts and communication formats that meet stakeholder needs based on attributes such as power, interest, influence, and availability. In this scenario, the sponsor needs concise, decision-ready information, the process owner needs facilitated collaboration and clear acceptance expectations, IT needs detailed interface requirements to execute, and end users need practical guidance to support adoption.
A good tailored approach:
The key takeaway is to match the artifact and communication channel to each stakeholder segment, reducing noise while still covering critical requirements and adoption needs on time.
It uses stakeholder power/interest to right-size artifacts and channels so each group gets only what they need within the 3-week window.
Topic: Business Analysis Frameworks
A business analyst on a predictive project receives a new reporting requirement from the sales director after the requirements baseline has been approved. The BA has already assessed impacts (+2 weeks schedule, +$15,000 cost) and documented the proposed change. The project manager says work cannot start without formal authorization.
What is the best next step?
Best answer: D
What this tests: Business Analysis Frameworks
Explanation: When a new requirement impacts an approved baseline, it must be authorized through the agreed approval path (such as the sponsor or change control board). The BA’s next step is to present the documented request and impact so an accountable decision maker can approve or reject it. After approval, the decision can be communicated and incorporated into project artifacts.
The core concept is communicating requirements decisions and obtaining approvals using the project’s governance. Because the requirement arrives after the requirements baseline is approved and it changes schedule and cost, it is a controlled change. Since the BA has already documented the request and performed impact analysis, the next step is to route it to the defined approval authority (e.g., sponsor/CCB) for a formal decision.
Typical sequence is:
Starting work or updating baselines before authorization undermines control and creates rework; escalation is only needed when normal decision channels cannot decide.
Because the requirement affects a baselined scope, the BA should route the documented change to the defined approval authority before execution.
Topic: Business Analysis Frameworks
You are the business analyst on a hybrid project to implement an online refund feature. A stakeholder provides the requirement: “The system should quickly process refunds.”
Before the team can confirm this requirement is complete, consistent, and testable, what should you ask for FIRST?
Best answer: A
What this tests: Business Analysis Frameworks
Explanation: To validate a requirement for testability, you must be able to verify it objectively. “Quickly process refunds” is ambiguous, so the first step is to obtain measurable acceptance criteria that define what “quickly” means. Once the criteria are clear, the requirement can be evaluated for completeness and checked against other requirements for consistency.
Validating requirements includes ensuring they are complete, consistent, and testable. In the scenario, the requirement uses vague language (“quickly”), which prevents objective verification and makes the requirement not testable as written. The most useful first question is to obtain measurable acceptance criteria (for example, a maximum processing time, a percentile-based response time, or a throughput/volume expectation under stated conditions). With clear, measurable criteria, the team can confirm whether the requirement is sufficiently complete, can be tested in UAT or automated tests, and can be compared to other requirements (such as performance, compliance, or service-level expectations) to identify conflicts. Design details and planning artifacts may be needed later, but they do not resolve the ambiguity that blocks validation.
Defining measurable criteria (e.g., time or throughput) makes the requirement testable and supports completeness.
Topic: Agile Frameworks/Methodologies
A Scrum team is halfway through a 2-week sprint when testing reveals several defects in a newly completed feature. One defect causes incorrect totals in a customer-facing report; the others are minor UI issues. The team is concerned about missing the Sprint Goal.
Which TWO actions are most appropriate to handle these defects without derailing delivery? (Select TWO)
Correct answers: D, F
What this tests: Agile Frameworks/Methodologies
Explanation: In agile, defects discovered during an iteration are handled through rapid transparency, triage, and prioritization. Critical defects that jeopardize the Sprint Goal are addressed by collaboratively re-planning the Sprint Backlog with the Product Owner. Lower-severity defects are recorded as Product Backlog Items for future prioritization to avoid unnecessary disruption.
The key is to treat defects as work that must be prioritized against the Sprint Goal and the team’s capacity. When a defect threatens the Sprint Goal (or the increment’s usability), the team should immediately make it visible, assess impact, and collaborate with the Product Owner to re-plan the Sprint Backlog (for example, swap out lower-priority sprint work to make room).
For defects that do not materially affect the Sprint Goal, capture them as Product Backlog Items (often as bug stories) with enough detail and acceptance criteria so the Product Owner can prioritize them alongside other product work. This preserves delivery flow while ensuring defects remain visible and traceable.
Avoid actions that hide problems, change iteration timeboxes, or bypass team ownership of quality.
Critical defects should be made transparent and handled by re-planning sprint work with the Product Owner while preserving focus on the Sprint Goal.
Non-critical defects can be captured as backlog work and prioritized later to protect current sprint commitments.
Topic: Agile Frameworks/Methodologies
A Scrum team is mid-sprint on a mobile app. In the Daily Scrum, a developer reports they cannot continue a high-priority story because they still do not have credentials to access a required third-party test environment. The Scrum Master decides to “wait a few days” to see if the vendor responds on their own instead of escalating the impediment today.
What is the most likely near-term impact of this decision?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: In agile, blockers should be identified early and addressed immediately to keep flow moving toward the sprint goal. Waiting to escalate a known access issue means the team cannot complete the dependent work now. The most immediate consequence is reduced throughput and slower sprint progress.
An impediment that prevents work from continuing (like missing environment credentials) should be surfaced early and acted on quickly so the team can maintain progress during the sprint. Choosing to “wait a few days” is inaction on a known blocker, so the team will either stop work on the affected story or switch to lower-priority items, creating delays and increasing the likelihood of carryover.
Practical next actions to remove the impediment include:
The key takeaway is that delayed impediment removal most directly causes immediate slowdowns in sprint execution.
Not removing the impediment quickly leaves the team unable to proceed, reducing completed work in the sprint.
Topic: Agile Frameworks/Methodologies
A software team is using Scrum to build an update to a medical-device support portal. Although the team delivers working increments each sprint, the contract has a fixed set of required features and the organization must pass an external compliance audit before release.
Which evidence best validates that the product increment is release-ready in this constrained adaptive context?
Best answer: C
What this tests: Agile Frameworks/Methodologies
Explanation: In a compliance- and fixed-scope situation, progress is not validated by speed or demonstrations alone. The strongest validation is objective evidence that every mandated requirement was verified and can be traced to test results acceptable for an audit. A traceability artifact with pass/fail verification provides that release-readiness evidence.
Adaptive delivery can still be used under heavy constraints, but the “done” evidence must satisfy fixed commitments and compliance expectations. In regulated or contractually fixed-scope environments, stakeholders often need objective, auditable proof that each required capability and control was implemented and verified.
A requirements traceability matrix (or equivalent traceability artifact) that links mandated requirements to implemented work items and to executed test/validation results provides clear, reviewable evidence of completeness and acceptance readiness. This directly supports an external audit because it demonstrates coverage (nothing required was missed) and verification (it was tested and passed), which a demo or velocity-based measures cannot prove.
When scope and compliance are fixed, audit-ready traceability plus verification results best demonstrate acceptance and release readiness.
Topic: Project Management Fundamentals and Core Concepts
You are the project manager for a predictive project that is entering closeout. Review the closeout status excerpt.
Closeout status (excerpt)
- Deliverables installed and verified: Complete
- Ops handover (training + runbook): Complete
- Customer acceptance form: Drafted; sponsor signature pending
- Lessons learned: Session held; notes not finalized
Which action should the project manager take next to support proper project closure?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The exhibit shows deliverables and handover are complete, but formal customer acceptance is still pending. A project is not ready to close until the authorized customer/sponsor provides documented acceptance of the final deliverables. Lessons learned should still be finalized, but acceptance sign-off is the most immediate closure gate shown as incomplete.
Project closure includes confirming acceptance, transitioning deliverables to operations/support, and capturing lessons learned for organizational reuse. In the exhibit, transition activities are complete (training and runbook delivered) and lessons learned were started (session held), but the sponsor has not signed the acceptance form. The next action is to obtain formal acceptance from the authorized stakeholder because it provides documented confirmation that requirements were met and supports final administrative closure activities (finalizing records, releasing resources, and completing any remaining closeout tasks). The key takeaway is that verified delivery is not the same as formal acceptance—closure requires documented sign-off.
Formal acceptance documents that deliverables meet requirements and is a key prerequisite for closing the project.
Topic: Project Management Fundamentals and Core Concepts
You join a small predictive project mid-planning. The sponsor asks, “Are we managing risks appropriately?” The team says they “talk about risks in meetings,” but no one can explain how risks are documented, reviewed, or kept current.
What should you ask for FIRST before deciding whether risk management is being done properly?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A risk management plan explains how risk activities will be performed, including roles, analysis approach, reporting, and review cadence. Ongoing tracking is typically done through a living risk register (or risk log) that is updated as risks are identified, assessed, responded to, and monitored. If neither exists, “talking about risks” is not a controlled tracking process.
The key artifact to verify is the risk management plan, because its purpose is to define the project’s risk management approach (how risks will be identified, analyzed, planned for, monitored, and communicated), including responsibilities and how often reviews occur. To confirm risks are tracked over time, you then look for the risk register/risk log, which should show current risk statements, owners, responses, status, and updates from periodic reviews. In the scenario, the gap is not performance data or change control—it’s the absence of defined risk processes and a maintained tracking record.
These define the approach to manage risk and provide the mechanism to track risks over time.
Topic: Agile Frameworks/Methodologies
A Scrum team is two sprints into a product update. Stakeholders are concerned that the team is delivering new features while bugs accumulate and refactoring is postponed. The product owner wants objective evidence that defects and technical debt are being tracked and prioritized alongside feature work.
Which metric or artifact best validates this?
Best answer: A
What this tests: Agile Frameworks/Methodologies
Explanation: The best validation is evidence that defects and technical debt are captured as backlog items and ordered against feature work. An integrated, prioritized product backlog shows the trade-offs the product owner is making and what work is most important next. This directly addresses whether “hidden” quality work is being managed intentionally rather than deferred.
In Scrum and other adaptive approaches, defects and technical debt should be transparent and managed like any other work. The strongest evidence is an ordered product backlog that contains feature, defect, and technical-debt items, allowing the product owner to explicitly prioritize quality work alongside new functionality.
This validates the team is:
Progress-only charts (velocity/burnup) can improve while quality deteriorates, and a list of completed refactoring tasks is an output that doesn’t prove ongoing tracking and prioritization. The key takeaway is to use backlog transparency and ordering as the primary control for balancing features with quality work.
A single ordered product backlog makes defect and technical-debt work visible and prioritized with features.
Topic: Predictive, Plan-Based Methodologies
A predictive project is in execution. The change control board (CCB) has approved a change request to add an automated reporting feature. The change adds two new work packages to the WBS and increases the budget by $18,000, but the sponsor still expects the team to track performance against baselined scope, schedule, and cost. The scheduler has already inserted the new activities into the schedule.
What is the BEST next action for the project manager?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: Because the change has been approved, the project must be re-baselined where impacted so that reporting and control remain valid. Adding work packages affects the scope baseline and typically drives schedule and cost baseline changes as well. The project manager’s integration role is to coordinate these aligned updates and communicate the revised plan.
Project integration management ensures approved changes are implemented consistently across the project management plan. In a predictive project, adding new deliverables/work packages changes the scope baseline (scope statement, WBS, and WBS dictionary) and will usually affect the schedule and cost baselines used for tracking and performance reporting.
After CCB approval, the project manager should:
Updating only one baseline (or starting work without integrated updates) creates inconsistent control data and unreliable status reporting.
After approval, integration management requires updating all impacted baselines (not just the schedule) so performance can be measured consistently.
Topic: Business Analysis Frameworks
You are supporting a hybrid project delivering a new e-commerce mobile app. The sponsor asks why the team is planning multiple releases instead of waiting for a “complete” launch.
Exhibit: Product roadmap excerpt
Release 1 (MVP): Browse products, add to cart, pay
Release 2: Saved lists, promo codes
Release 3: Personalized offers, loyalty
Risk note: A1—Account setup before purchase is unvalidated
Constraint: PCI security approval needed before full rollout
Which interpretation best aligns with the exhibit and explains how incremental releases reduce risk?
Best answer: C
What this tests: Business Analysis Frameworks
Explanation: An MVP is the smallest set of features that delivers real value and enables validated learning. The exhibit labels Release 1 as the MVP and highlights an unvalidated assumption, which the MVP can test with real users. Releasing incrementally reduces risk by discovering gaps early, limiting rework, and allowing adjustments before investing in lower-value features.
The MVP is a usable, value-delivering version of the product with only the essential features needed to meet a core need and learn from real use. In the exhibit, “browse, add to cart, pay” is the minimum capability that delivers value and can validate the key assumption about account setup.
Incremental releases reduce risk by:
This approach avoids betting the entire schedule and budget on unvalidated assumptions and late discovery.
It delivers the minimum usable value and tests the unvalidated assumption early, reducing risk through learning before adding later features.
Topic: Predictive, Plan-Based Methodologies
A predictive project is in execution. The risk register includes risk R-12: “Network equipment delivery may be late,” with a response already implemented: “Place orders early and confirm shipment weekly.” For the past three weeks, shipments have been on time.
Today, the vendor reports a possible port strike next month that could stop shipments even with early ordering. What is the best immediate action for the project manager?
Best answer: A
What this tests: Predictive, Plan-Based Methodologies
Explanation: The port strike is a newly identified uncertain event, so it should be added to the risk register. The risk register is also where the team tracks response implementation and effectiveness, so the project manager should update the existing delivery risk entry to reflect that the current response is performing as expected so far.
In predictive projects, the risk register is the primary control artifact for documenting newly identified risks and for monitoring risk response effectiveness over time. Here, the port strike is not yet happening, so it is a risk that should be recorded, analyzed (probability/impact), assigned an owner, and given triggers and planned responses as appropriate. Separately, because the delivery response has been in place for three weeks, the risk register should be updated to reflect current response status and observed effectiveness (for example, improved on-time shipments), along with any residual or secondary risks. The key takeaway is to document and track risks in the risk register rather than treating an uncertainty as an issue or jumping straight to baseline changes.
This records the newly identified strike risk and updates tracking on whether the existing delivery response is working over time.
Topic: Predictive, Plan-Based Methodologies
A project manager has an approved project charter for a predictive project to implement a new time-tracking system. The sponsor is asking for a detailed schedule and cost baseline by the end of the week. During planning, the team realizes they only have a high-level scope statement and a list of major deliverables; the work has not been decomposed into work packages.
What should the project manager do next?
Best answer: B
What this tests: Predictive, Plan-Based Methodologies
Explanation: In a predictive approach, detailed planning depends on first decomposing the approved scope into manageable components. Creating the WBS (and documenting work package details) provides the foundation for estimating durations and costs. With that structure in place, the team can then develop a credible schedule and cost baseline.
The key predictive artifact needed here is the WBS, which breaks the project scope into deliverables and work packages. Without work packages, the team cannot reliably estimate effort, durations, resources, or costs, so any schedule or cost baseline would be guesswork. Since the charter is already approved, the next logical step is to complete scope decomposition and document work package details (often supported by a WBS dictionary). After the WBS is established, the team can sequence activities, estimate durations and costs, develop the schedule, and then set the schedule and cost baselines for performance measurement. The takeaway is that baselines come after the work is defined at an appropriate level of detail.
A WBS decomposes scope into work packages that are needed to develop reliable schedule and cost estimates for baselines.
Topic: Predictive, Plan-Based Methodologies
A project manager is planning a predictive project to upgrade a company’s data center. Before building the detailed schedule, the sponsor asks how the team can demonstrate that the scope has been broken down into manageable pieces that can be estimated and assigned.
Which artifact best validates that the project deliverables were decomposed into work packages?
Best answer: B
What this tests: Predictive, Plan-Based Methodologies
Explanation: A work breakdown structure (WBS) is created by decomposing deliverables into smaller components until they reach the work package level. The WBS dictionary provides the supporting details that clarify what each work package includes and helps confirm the decomposition is usable for estimating and assigning work.
Decomposition is a scope-planning technique used to break project deliverables down into smaller, more manageable components called work packages. The WBS is the hierarchical representation of that decomposition and is the best evidence that the project has been structured into work that can be estimated, costed, and assigned. The WBS dictionary strengthens this validation by documenting key work package details (for example, a description, boundaries, and acceptance information), reducing ambiguity before building the activity list and schedule.
Key takeaway: schedules and reports show timing or performance, but they do not prove deliverable-to-work-package decomposition.
A WBS (supported by the WBS dictionary) is the artifact that shows deliverables decomposed into manageable work packages.
Topic: Agile Frameworks/Methodologies
A Scrum team is halfway through a 2-week sprint. The product owner asks for evidence showing whether the team is on track to finish the sprint backlog by the sprint end date. Which metric or artifact BEST validates this day-to-day progress?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: A sprint burndown chart is designed to track remaining work during the sprint and visually shows whether work is burning down fast enough to reach completion by the sprint end date. This makes it strong evidence of current progress against the sprint plan.
In adaptive projects, progress is best validated with information that shows completed value and remaining work over time. A sprint burndown chart plots remaining work (often in story points or hours) each day of the sprint, making it easy to see whether the team is trending toward finishing the sprint backlog by the end date.
Velocity is a separate concept: it is the team’s average amount of work completed per iteration and is mainly used to forecast future capacity (for example, how many story points are likely to fit in upcoming sprints), not to show day-to-day progress inside the current sprint. The key takeaway is: use burndown to track in-sprint progress; use velocity to forecast.
A sprint burndown shows the daily trend of remaining work toward zero by sprint end, directly validating in-sprint progress.
Topic: Project Management Fundamentals and Core Concepts
A project team is delivering a hybrid rollout of a new customer portal. In the last two iterations, work has been re-done because the compliance manager and call center supervisor raised late objections, even though status emails were sent weekly. The project manager reviews the stakeholder register and finds it lists only names, titles, and contact details from the kickoff; it does not note stakeholder influence, interests, or preferred engagement, and it has not been updated since a recent reorganization.
What is the most likely underlying cause of the recurring late objections?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A stakeholder register should document who the stakeholders are and summarize their influence, interests, and engagement needs so the team can plan targeted involvement. Here, the register contains only contact details and was not updated after a reorganization. That makes it likely the team missed high-influence stakeholders’ needs until late, causing rework.
The core issue is weak stakeholder identification and analysis captured in the stakeholder register. A useful stakeholder register is more than a contact list; it captures attributes that drive an engagement approach (e.g., influence/power, interests, expectations, preferred communication, and engagement needs). In this scenario, late objections from compliance and call center leaders suggest the team did not proactively involve stakeholders with high influence or specific concerns.
Using the stakeholder register effectively means:
The key takeaway is that targeted engagement planning depends on an accurate, analysis-rich stakeholder register, not just broadcast status updates.
Without documented influence, interests, and engagement needs (and updates after changes), key stakeholders are not engaged appropriately, leading to late objections.
Topic: Agile Frameworks/Methodologies
A cross-functional team is using Scrum on a 2-week iteration. The product owner wants to better understand the purpose and timing of key ceremonies.
Which TWO statements correctly describe the purpose and timing of Scrum’s daily standup, iteration review, and retrospective? (Select TWO)
Correct answers: B, E
What this tests: Agile Frameworks/Methodologies
Explanation: The daily standup is a brief daily synchronization to coordinate work and expose blockers quickly. The iteration review occurs at the end of the iteration to inspect the completed increment with stakeholders and use feedback to adapt the product backlog and direction.
In Scrum, each ceremony has a distinct purpose and a typical place in the iteration cadence. The daily standup happens every day (usually 15 minutes) to synchronize the team’s work and highlight impediments early so they can be addressed quickly. The iteration review happens at the end of the iteration to inspect the increment with stakeholders, confirm what was completed, and use feedback to adapt the product backlog and upcoming priorities. The retrospective also occurs near the end of the iteration (commonly after the review) but focuses on the team’s way of working—identifying actionable process improvements to try in the next iteration. A key takeaway is to separate “product inspection and feedback” (review) from “process improvement” (retrospective).
Daily standups occur each day of the iteration to quickly synchronize work and identify blockers early.
Iteration reviews happen at iteration end to review what was built and use stakeholder feedback to adjust upcoming work.
Topic: Predictive, Plan-Based Methodologies
A project manager on a predictive project reviews the monthly earned value (EVM) report. It shows CPI = 0.75 and SPI = 0.90.
What do these indicators signal about project performance?
Best answer: B
What this tests: Predictive, Plan-Based Methodologies
Explanation: CPI and SPI are EVM efficiency ratios where 1.0 means on plan. A CPI less than 1.0 indicates the project is getting less value per cost spent (over budget). An SPI less than 1.0 indicates the project is earning value more slowly than planned (behind schedule).
Cost Performance Index (CPI) and Schedule Performance Index (SPI) are basic EVM indicators that compare earned value to the relevant baseline measure.
CPI = EV / AC: cost efficiency; values < 1.0 mean a cost overrun.SPI = EV / PV: schedule efficiency; values < 1.0 mean behind the planned rate of progress.With CPI = 0.75, the project is spending more than planned for the value it has earned (over budget). With SPI = 0.90, earned value is lagging planned value (behind schedule). The key takeaway is that values below 1.0 indicate unfavorable performance for that dimension.
Both indices are below 1.0, indicating cost overrun (CPI) and schedule slippage (SPI).
Topic: Project Management Fundamentals and Core Concepts
A company is running a hybrid project to implement a new CRM system. During kickoff, the project manager reminds everyone to follow standard roles and responsibilities. Which action is NOT an appropriate responsibility of the project sponsor?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The project sponsor provides high-level direction, resources, and organizational support, and is often involved in approving and accepting key outcomes. The project team is responsible for planning and performing the day-to-day work to produce deliverables. Therefore, assigning daily tasks to individuals is outside the sponsor’s responsibilities.
Sponsors and project teams operate at different levels. The sponsor typically champions the project, secures funding, provides strategic guidance, and supports governance activities such as approving the charter and making or enabling key decisions. The project team focuses on executing the work: decomposing work, coordinating tasks, producing deliverables, and reporting progress.
In a hybrid environment, the sponsor may help clarify business priorities and accept major deliverables or phase outcomes, but should not manage daily task assignments or supervise individual contributors’ work. The takeaway is that sponsors enable and govern, while teams execute and deliver.
Directing day-to-day task assignments is a project team/PM function, not the sponsor’s role.
Topic: Agile Frameworks/Methodologies
A product team is using Scrum on a 2-week sprint. Five days into the sprint, a sales leader requests a new reporting filter that could increase customer value. The team has no extra capacity, and the sprint goal is still achievable if they do not add work.
As the project manager supporting the agile team, which action best optimizes value delivery while managing the change within agile constraints?
Best answer: D
What this tests: Agile Frameworks/Methodologies
Explanation: In adaptive approaches, change is intentionally managed through the product backlog. The best action is to capture the request as a backlog item, refine it to make it understandable and sized, and let the product owner reprioritize based on value. If the change is truly urgent, the team manages it transparently by renegotiating sprint scope rather than bypassing backlog controls.
Agile teams expect change and control it primarily through continuous product backlog refinement and product owner reprioritization, not through formal change requests and a change control board. When a new request arrives, the team should capture it as a product backlog item, clarify it (including acceptance criteria), and estimate it during refinement so the product owner can make an informed ordering decision.
If the work is needed before the sprint ends, it should still be handled transparently by collaborating to adjust the sprint backlog (for example, swapping out equivalent effort while protecting the sprint goal). This preserves visibility, manages capacity constraints, and keeps decision-making aligned to value.
Bypassing the backlog or “freezing scope” prevents effective agile change control and undermines empirical planning.
In agile, changes are managed by refining and reprioritizing the backlog, with any mid-sprint change handled transparently by adjusting the sprint backlog through collaboration.
Topic: Project Management Fundamentals and Core Concepts
You are an associate PM on a hybrid software rollout with multiple teams. The sponsor asks for evidence of how the project will develop the schedule, measure schedule performance, and control schedule changes so reporting is consistent throughout delivery.
Which artifact best validates that this guidance has been defined and agreed?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The schedule management plan describes the rules and methods for creating, monitoring, and controlling the project schedule. It documents how progress will be measured and reported and how schedule changes will be evaluated and approved, providing consistent guidance across teams.
The schedule management plan is the component of the project management plan that explains how scheduling will be performed and governed on the project. In the scenario, the sponsor is not asking for the current dates; they want evidence of the agreed approach for scheduling and schedule control.
It commonly documents items such as:
A project schedule shows planned/forecast dates, while the schedule management plan explains how the schedule will be built, tracked, and controlled.
It defines the scheduling methodology, tracking, reporting, and control approach used for the project.
Topic: Agile Frameworks/Methodologies
A Scrum team is struggling with too much work started at once, frequent context switching, and unclear status during the sprint. The project manager wants evidence that the team is visualizing workflow and actively managing work in progress during daily coordination.
Which artifact best validates this?
Best answer: B
What this tests: Agile Frameworks/Methodologies
Explanation: The most direct validation is a task board that displays work items moving through workflow states (for example, To Do/In Progress/Done) and highlights WIP against agreed limits. This provides transparent, real-time evidence of progress and supports decisions to stop starting and start finishing.
In adaptive delivery, a task board (physical or electronic) is a primary information radiator used to visualize workflow and manage work in progress. By showing each work item’s current state and making WIP limits and blockers visible, the team can quickly validate whether work is flowing toward “Done” and adjust daily behaviors (swarming, rebalancing, unblocking) to reduce multitasking and queues.
Evidence on a task board typically includes:
Measures like effort hours or backlog size don’t show flow or WIP control, which is the core problem described.
A task board makes flow and WIP visible so the team can limit starts, swarm, and unblock work.
Topic: Predictive, Plan-Based Methodologies
A project is using a predictive approach to deliver a new payroll system. The sponsor asks for evidence that every approved business requirement has been addressed and verified (and that no extra features were built). Which artifact best validates this?
Best answer: D
What this tests: Predictive, Plan-Based Methodologies
Explanation: Requirements traceability in a predictive project is used to connect each approved requirement to the deliverables and verification activities that satisfy it. This provides objective evidence of completeness (all requirements covered) and helps detect gold plating (work not tied to a requirement). The RTM is the most direct artifact for demonstrating that coverage.
In a predictive project, requirements traceability ensures each approved requirement can be tracked forward to solution components (design, build, deliverables) and to verification (test cases/results, inspections) and traced backward from deliverables to the originating requirement. In the sponsor’s request, the key need is evidence of coverage: that all requirements were implemented and verified, and that delivered scope aligns to what was approved. The requirements traceability matrix (RTM) is designed for this purpose because it provides a structured, auditable link between requirements and the deliverables/tests used to confirm them. A schedule status report or meeting minutes may show activity or agreement, but they do not prove end-to-end requirement fulfillment.
An RTM provides end-to-end mapping from each requirement to its implementation and verification evidence.
Use the CAPM Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the CAPM guide on PMExams.com for concept review, then return here for PM Mastery practice.