PMPRocket
PMP Practice QuestionsRequirements Management
Process Domain

Requirements Management PMP Practice Questions

Test yourself with 10 free, scenario-based PMP practice questions on requirements management, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Question 1 of 10

During analysis and planning for a new claims processing system, the finance and operations groups each describe the need for "faster claim approval" in separate workshops. Finance means approval within two business days; operations means fewer manual review steps. The business analyst has drafted both versions into the requirements documentation. What should the project manager do FIRST?

  1. A.Have the business analyst analyze each version separately and estimate the cost of building both definitions into the claims workflow.
  2. B.Facilitate a joint workshop where finance and operations reconcile their definitions of faster approval into one measurable requirement.
  3. C.Keep both definitions in the requirements documentation and let the design team choose the one that the new claims workflow will satisfy.
  4. D.Forward both versions to the sponsor and ask the sponsor to pick the definition of faster approval that the claims project will keep.
Show answer and explanation

Correct answer: B

The two groups use the same words for different needs, and the gap must be closed with both groups present before design starts. A joint facilitated workshop lets finance and operations hear each other and agree on one measurable requirement. Having the business analyst analyze and cost each version separately keeps the groups apart and treats a conflict as an estimating exercise. Passing both versions to the design team pushes a business decision onto people who cannot make it. Asking the sponsor to pick one skips the collaboration that could satisfy both groups and should only follow if they cannot agree.

Question 2 of 10

On a hybrid project, the development team works in two-week iterations while the overall release follows a predictive plan. During analysis and planning, user stories are entering iterations without clear acceptance criteria, and developers are guessing at what done looks like for each story. Which action should come FIRST?

  1. A.Let the developers agree on acceptance criteria among themselves during the iteration in which each user story is built.
  2. B.Have the testers review the finished code at the end of each iteration and derive acceptance criteria for the stories from it.
  3. C.Draft acceptance criteria for each user story personally and ask the product owner to sign off on them before the next iteration.
  4. D.Have the product owner add acceptance criteria to upcoming stories in backlog refinement, before the team pulls them into an iteration.
Show answer and explanation

Correct answer: D

Acceptance criteria express what the business needs, so the product owner must define them, and backlog refinement is the place to do it before stories enter an iteration. Developers agreeing on criteria among themselves mid-iteration means they define their own target, which is the guessing the team already suffers from. Testers reviewing finished code reverses the order and only confirms what was built. The project manager drafting every criterion takes ownership of backlog content away from the product owner, even if the product owner signs off afterward.

Question 3 of 10

An agile team is building a scheduling app. During analysis and planning, the product owner announces a change: appointments must now support multiple time zones. The architect warns this may affect several downstream design decisions already reflected in backlog items for notifications, reporting, and calendar sync. What should the team do FIRST?

  1. A.Review with the product owner and architect which backlog items the time zone change affects before it is reprioritized.
  2. B.Submit a change request to the change control board for the time zone requirement and hold all affected backlog items until it rules.
  3. C.Pull the time zone change into the current iteration right away and rebuild the notification, reporting, and calendar sync stories around it.
  4. D.Agree with the product owner to add a time zone story at the bottom of the backlog and revisit its impact during the next release planning.
Show answer and explanation

Correct answer: A

On an agile project, change is expected and handled through the backlog, but the product owner needs to see its ripple effects before deciding where it fits. Reviewing the affected items with the product owner and architect makes the impact on notifications, reporting, and calendar sync visible before reprioritizing. A formal change control board submission adds predictive overhead the agile approach does not require for backlog changes. Pulling the change into the current iteration disrupts the iteration commitment before anyone understands the impact. Parking the story at the bottom ignores that later items depend on this decision.

Question 4 of 10

A predictive project is delivering a laboratory information system for a regulated client. During analysis and planning, a completed quality review confirms that many requirements cannot be linked to the deliverables that satisfy them or to the test cases that will verify them, and several test cases have no requirement behind them. What should the project manager do NEXT?

  1. A.Ask the test lead to write extra test cases for the laboratory system and raise the coverage percentage reported in the test plan before execution.
  2. B.Have the business analyst rewrite the requirements documentation in a new template with clearer wording for each laboratory requirement.
  3. C.Establish a requirements traceability matrix that links each laboratory system requirement to its source, its deliverables, and its test cases.
  4. D.Assess requirements coverage at the end of system testing by comparing the executed test cases with the requirements documentation.
Show answer and explanation

Correct answer: C

The review has already identified the problem: missing links between requirements, deliverables, and tests. The tool designed to hold those links is the requirements traceability matrix, and establishing it during planning exposes every requirement without a test and every test without a requirement. Writing extra test cases raises a coverage number without proving each requirement is verified and may add more orphan tests. Rewriting the requirements in a new template improves readability but creates no links. Assessing coverage only at the end of system testing finds gaps when they are expensive to fix on a regulated system.

Question 5 of 10

On a hybrid program to modernize a retail loyalty platform, the team has started coding new features from a wish list gathered from store managers. During analysis and planning, the project manager notices that none of the features has been tied to the objectives in the business case, and the sponsor has not confirmed which outcomes matter most. What is the BEST action for the project manager to take?

  1. A.Let the sponsor evaluate the features already built at the phase-end review and decide then which of them meet the business need.
  2. B.Stop starting new features until the sponsor and product owner have tied every wish list feature to a business case objective.
  3. C.Work with the sponsor to approve a complete, detailed requirements specification for the loyalty platform before any more coding.
  4. D.Raise a change request to remove every store manager feature from the scope baseline until the business case has been formally updated.
Show answer and explanation

Correct answer: B

Building before the business need is confirmed risks delivering features nobody values, so new work should wait until it is connected to the business case. Holding new starts while the sponsor and product owner tie each item to an objective stops the waste without discarding useful work. Having the sponsor evaluate features at the phase-end review is too late, because the team keeps building unvalidated features in the meantime. Approving a complete detailed specification overcorrects and ignores the iterative part of the hybrid approach. A change request to strip every store manager feature from the baseline is premature because some may be exactly what the business case needs.

Question 6 of 10

An agile team building a citizen services portal has captured dozens of requirements as backlog items. During analysis and planning, the product owner admits there is no agreed basis for ordering them: some stakeholders push for legal deadlines, others for user volume, and the team keeps asking what to pull next. What should the project manager do FIRST?

  1. A.Have the team order the portal backlog by technical simplicity and deliver as many backlog items as possible during the first few iterations.
  2. B.Agree with the product owner that they will rank the backlog on personal judgment for now and settle the ordering criteria later in the release.
  3. C.Order the backlog by the date each stakeholder submitted a request and tell each department its items will be handled in sequence.
  4. D.Facilitate a session where the product owner and stakeholders agree on ordering criteria such as legal deadlines, user value, and risk.
Show answer and explanation

Correct answer: D

The product owner owns the backlog order, but without shared criteria every ranking will be challenged by stakeholders pushing different priorities. As a servant leader, the project manager facilitates a session where the product owner and stakeholders agree on explicit criteria such as legal deadlines, user value, and risk. Ordering by technical simplicity maximizes output rather than value. Agreeing that the product owner ranks on personal judgment for now leaves the disagreement in place and invites rework. Ordering by submission date treats arrival order as value and may push legally required items too late.

Question 7 of 10

On a predictive project to replace a bank's payment gateway, performance, security, and audit logging requirements have repeatedly surfaced late, after designs were approved. A lessons learned review has concluded that elicitation workshops included only business users. The next release is still in analysis and planning. What should the project manager do NEXT?

  1. A.Invite security, operations, and audit representatives to the elicitation workshops for the next payment gateway release.
  2. B.Process each late nonfunctional requirement through integrated change control as it appears during the next release.
  3. C.Add contingency reserve to the next release budget and schedule for rework from late performance and security requirements.
  4. D.Work jointly with the same business users to list the performance, security, and logging needs they can think of.
Show answer and explanation

Correct answer: A

The review has already found the root cause: the people who own nonfunctional needs were never part of elicitation. Inviting security, operations, and audit representatives to the next release's workshops addresses that cause directly. Running each late requirement through change control is correct procedure but only manages the symptom after designs are approved. Adding contingency reserve accepts the rework rather than preventing it. Working again with the same business users repeats the gap, since they are not the experts on performance, security, or audit logging.

Question 8 of 10

A hybrid project is consolidating three HR systems. During analysis and planning, the backlog has grown to more than 150 requests from HR, payroll, and IT. The product owner says they cannot rank the requests because the charter lists the consolidation objectives only in general terms and no one has said which outcomes count as value. What is the BEST action for the project manager to take?

  1. A.Have the team analyze the size of each request in story points and give the smallest HR system items the earliest slots.
  2. B.Ask the product owner to evaluate each request by how many HR, payroll, and IT stakeholders asked for it and rank them on that.
  3. C.Ask the sponsor to state which consolidation outcomes define value, for the product owner to rank requests against.
  4. D.Remove the oldest requests from HR, payroll, and IT and bring the list to a manageable size before anyone ranks it.
Show answer and explanation

Correct answer: C

The product owner is blocked by a missing definition of value, and that definition belongs to the sponsor, who owns the business case and the consolidation objectives. Asking the sponsor to state which outcomes count as value gives the product owner a basis for ranking the backlog. Analyzing request size gives cost information but says nothing about value, and doing the smallest items first is not a value strategy. Evaluating requests by number of requesters rewards lobbying rather than business benefit. Deleting the oldest requests is arbitrary and may discard the most important needs.

Question 9 of 10

An agile team is delivering a sales analytics product. During analysis and planning, the sales, finance, and marketing departments disagree on what the monthly performance report must include, and each has sent the team a long list of required fields. The first increment is due in three weeks. How should the project manager respond?

  1. A.Agree with sales, finance, and marketing to include every requested field in the first increment of the monthly performance report.
  2. B.Have the product owner walk the three departments through a rough mockup of the report and settle the minimum first-increment content.
  3. C.Escalate the disagreement to the sponsor and ask the sponsor to decide the report fields before the team starts the first increment.
  4. D.Let the marketing department, which sent the most detailed field list, define the report and adjust it for the others in a later increment.
Show answer and explanation

Correct answer: B

In an agile setting, a quick visual model and fast feedback are the best way to turn conflicting wish lists into a shared understanding, with the product owner making the final call on content. Walking the three departments through a rough mockup surfaces what each truly needs and settles a minimum first increment. Agreeing to include every requested field creates a bloated report and delays delivery. Escalating to the sponsor is premature because the product owner has the authority and the departments have not yet worked through the conflict together. Giving marketing control because its list is the most detailed favors one group without evidence of greater value.

Question 10 of 10

On a predictive project delivering a hospital billing system, the requirements traceability matrix links every approved requirement to a deliverable. A coverage review has just finished and found that 40 approved requirements, mostly regulatory billing rules, have no verification method or acceptance criterion. The sponsor asks how the team will make sure these are tested before go-live. What should the project manager do NEXT?

  1. A.Assure the sponsor that user acceptance testing by the hospital billing staff will exercise the 40 uncovered regulatory requirements.
  2. B.Raise a change request asking the sponsor to remove the 40 uncovered requirements from the approved requirements baseline.
  3. C.Have the business analyst and compliance owners define acceptance criteria for each of the 40 uncovered regulatory requirements.
  4. D.Review the 40 uncovered requirements with the sponsor after system testing and decide then which ones still need verification.
Show answer and explanation

Correct answer: C

The coverage review has already found the gap, so the next step is to close it by defining what acceptable looks like for each of the 40 requirements. Acceptance criteria express the business and regulatory need, so the business analyst and the compliance owners of those billing rules are the right people to define them, and the test lead can then plan how each one is verified. This gives the sponsor concrete assurance that the regulatory rules will be tested. Relying on user acceptance testing is hope rather than control, because billing staff test what they use, not every regulatory rule. Removing approved requirements through a change request avoids the testing problem rather than solving it and may breach regulations. Reviewing them after system testing leaves the gap open until it is expensive to fix.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

More Process practice questions