PMP · Question #811
A project manager and project team developing a new product are discussing which work methods and tools to use to build the deliverable. What should the result of this discussion be?
The correct answer is C. An agreed-upon work method and tools that should fit the business need and project constraints. The discussion on work methods and tools should lead to an agreement on approaches and instruments that align with the project's objectives and constraints.
Question
Options
- AA detailed mitigation plan on the risks for each work method and the tools used
- BA technology roadmap for creating similar deliverables in the future with the same tools
- CAn agreed-upon work method and tools that should fit the business need and project constraints
- DA consensus that everything will run as anticipated once the tools and work methods are
How the community answered
(18 responses)- A11% (2)
- C83% (15)
- D6% (1)
Why each option
The discussion on work methods and tools should lead to an agreement on approaches and instruments that align with the project's objectives and constraints.
While risk mitigation is important, the result of this initial discussion is not solely a detailed mitigation plan, but rather the selection of methods and tools themselves.
A technology roadmap is for future deliverables and strategic planning, not the immediate result of deciding methods and tools for the current project deliverable.
The primary goal of discussing work methods and tools is to select the most appropriate ones that meet the project's specific business needs and operate within its constraints, ensuring an effective and efficient path to deliver the product. This decision is crucial for aligning the team's efforts and resources with the project's objectives.
Assuming everything will run as anticipated is unrealistic and neglects the inherent uncertainties and risks in project management.
Concept tested: Project planning for methods and tools
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
6
Nina C.Jul 5, 2026Going with C. The team needs to agree on methods and tools that actually fit the business need and project constraints, not just pick something and hope it works. D trips people up because consensus sounds nice but the key phrase in the stem is about fitting the need and constraints.
Mei-Ling H.Jun 29, 2026Going with A here. The word "discussing" in the stem implies they need to talk through the risks of each option before committing, and a detailed mitigation plan is the natural output of that conversation since picking tools without addressing what could go wrong would be careless.
Nina C.Jun 29, 2026Actually C is the right call here. "Discussing" in the Azure cloud adoption framework context maps to the Evaluate stage, where you compare options against requirements, not where you build out a full mitigation plan, which comes later in the Adopt phase once a decision is already locked in.
Yuki V.Jul 5, 2026C on exam last week. A is tempting because risk talk always sounds right, but the question asks what the result of the discussion should be, and agreeing on a method that fits constraints is the actual outcome.
Carlos M.Jul 5, 2026I'm going with A on this one. When the team is sitting down to pick work methods and tools, the real value of that discussion is surfacing what could go wrong with each option before you commit. A mitigation plan for risks tied to each method and tool set is exactly the kind of tangible output the PMBOK wants to see from these conversations, not just a vague agreement. C sounds nice but it is too generic and doesn't show the team actually worked through the downsides of their choices.
Yuki V.Jul 8, 2026Actually C is correct here, Carlos. When the team is selecting methods and tools in planning, the key output is a documented approach showing how the work gets done, not risk mitigation plans, which come later once you actually identify and analyze project risks.