First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Project and programme context
In PRINCE2, which project variable is defined as the means by which the project's products are produced, and is one of the four dimensions balanced by the project manager?
- Time
- Cost
- Quality Correct answer.
- Scope
Explanation
PRINCE2 frames the project manager's balancing act across four dimensions: cost, time, quality and scope. Quality is the dimension concerned with the characteristics and fitness for purpose of the products being delivered, not merely the budget or schedule.
Question 2Project and programme context
A programme is best distinguished from a project because a programme:
- delivers a set of related projects and change activities to achieve outcomes of strategic benefit Correct answer.
- has a fixed end date that cannot be altered once baselined
- is always delivered by a single supplier under one contract
- requires a business case only at the start of each constituent project
Explanation
A programme coordinates related projects and transition activities to realise outcomes and benefits of strategic importance to the organisation. Projects, by contrast, deliver defined outputs within a finite timescale and are typically managed under a single business case.
Question 3Project and programme context
Which document in a project's context sets out the justification for the investment, the expected benefits and the reasons the work should proceed?
- Risk register
- Business case Correct answer.
- Benefits map
- Project brief
Explanation
The business case provides the reasoning and justification for the project, including expected benefits, costs, risks and the rationale for the investment. It is the reference point against which continued viability is judged.
Question 4Project and programme context
In governance terms, what is the primary role of a project board (steering group)?
- To provide direction and oversight, making key decisions and authorising stage boundaries Correct answer.
- To conduct the day-to-day technical testing of project deliverables
- To audit the organisation's financial statements independently
- To produce the detailed work packages and assign tasks to team members
Explanation
A project board or steering group provides senior direction and oversight, approves plans and business case changes, and authorises progression at key decision points. It does not perform operational delivery work.
Question 5Project and programme context
An organisation's portfolio is best described as:
- the schedule of stage boundaries within one project
- the collection of projects and programmes that together deliver the organisation's strategic objectives Correct answer.
- the set of risks recorded across all live projects
- the single largest project currently underway in the business
Explanation
Portfolio management coordinates the collection of projects, programmes and other change activity so that collectively they support strategic objectives and are prioritised and resourced coherently. It sits above programme and project management.
Question 6Project and programme context
Which stakeholder group in the project context is characterised by having an interest in the project but no formal authority over its decisions?
- Sponsor
- Project manager
- Interested parties (for example, end users and regulators) Correct answer.
- Project board members
Explanation
Interested parties such as end users, regulators or community groups can influence or be affected by the project without holding decision authority. The sponsor, board and project manager all hold defined authority roles.
Question 7Project and programme context
A project manager is told the organisation has adopted a 'management by exception' principle. What does this most directly imply for reporting in the project context?
- The board sets no tolerances and reviews all decisions itself
- The project manager reports every minor deviation to the board as soon as it occurs
- The project manager may ignore all governance requirements that are not legally mandated
- The project manager operates within agreed tolerances and escalates only when those tolerances are forecast to be exceeded Correct answer.
Explanation
Management by exception means the board delegates authority within defined tolerances and expects escalation only when forecast performance will breach them. This keeps senior time focused on genuine exceptions rather than routine detail.
Question 8Project and programme context
The project manager forecasts that the stage will exceed its cost tolerance by 8 per cent in three weeks' time. Under typical governance arrangements, the appropriate action is to:
- reduce quality checks to recover the cost without informing anyone
- instruct the finance department to increase the budget without board involvement
- wait until the overspend actually occurs, then include it in the next routine highlight report
- escalate to the project board now with an exception report and options for recovery Correct answer.
Explanation
Tolerance breaches are managed on forecast information, so a forecast breach should be escalated before it happens. An exception report sets out the situation, impact and options so the board can decide.
Question 9Project and programme context
A sponsor is leaving the organisation mid-project. Which consequence poses the greatest risk to the project's context?
- The project's products will no longer meet their quality criteria
- All stakeholder registers become obsolete immediately
- Accountability for the business case and senior decision-making may lapse, delaying approvals and direction Correct answer.
- The project's technical architecture will automatically become invalid
Explanation
The sponsor owns the business case and provides senior accountability and direction, so a departure can leave a governance vacuum. Until a replacement is appointed, approvals and escalation paths are weakened.
Question 10Project and programme context
Which pair of factors best describes the wider organisational context that a project manager must understand before planning?
- The number of products in the project's breakdown structure
- The personal career goals of individual team members
- The organisation's strategic objectives and its governance and assurance arrangements Correct answer.
- The team's preferred software tools and meeting cadence
Explanation
The project context includes the strategic direction the project must support and the governance, assurance and reporting arrangements it must operate within. These shape how the project is justified, authorised and controlled.
Question 11Project and programme context
A programme's constituent projects each have their own business cases. How should the programme business case relate to them?
- It replaces them, so individual projects need no justification
- It duplicates each project business case word for word
- It is written only after all constituent projects have closed
- It provides the overarching justification and benefits, within which each project's contribution is positioned Correct answer.
Explanation
The programme business case justifies the overall investment and expected strategic benefits, while each project business case explains that project's contribution to those outcomes. The two levels are complementary, not substitutes.
Question 12Project and programme context
During a benefits review, a project has delivered all its outputs on time, but the expected operational savings have not appeared. What is the most appropriate contextual interpretation?
- Outputs have been delivered, but the realisation of benefits depends on outcomes and business change that may sit beyond the project Correct answer.
- The project manager should be replaced for poor performance
- The business case should be deleted because savings were overstated
- The project has failed because outputs alone do not count
Explanation
Projects deliver outputs; benefits arise when those outputs are adopted and used to create outcomes, often through business change managed beyond the project. Judging benefit realisation requires looking at the wider change context.
Question 13Project and programme context
A regulator is identified as an interested party with the power to halt the project but currently low interest. Which contextual response is most appropriate?
- Ignore the regulator because interest is currently low
- Publish all internal project data publicly to demonstrate transparency
- Transfer the regulator's concerns to the project board and cease contact
- Keep the regulator adequately informed and engaged so that latent power is not triggered unexpectedly Correct answer.
Explanation
Stakeholder analysis weighs both power and interest, so a high-power, low-interest party needs sufficient engagement to keep them supportive and avoid surprises. Low current interest does not neutralise their capacity to affect the project.
Question 14Project and programme context
An organisation mandates a stage-gate review before each major funding release. Which governance purpose does this primarily serve?
- It guarantees the project will finish within its original budget
- It removes the need for a project board during delivery
- It provides assurance that the project remains justified and controlled before further commitment Correct answer.
- It replaces the need for any risk management activity
Explanation
Stage gates give decision-makers a checkpoint to confirm continued viability, review performance and authorise the next tranche of work. They provide control and assurance rather than guaranteeing outcomes.
Question 15Project and programme context
A project manager is appointed into an organisation with a weak project governance framework and unclear decision rights. What is the most prudent first contextual action?
- Establish and agree with the sponsor the decision rights, reporting lines and escalation route Correct answer.
- Delegate all governance decisions to the delivery team
- Assume full decision authority to keep momentum
- Suspend all delivery until a perfect framework is designed
Explanation
Where governance is unclear, the project manager should agree decision rights, reporting and escalation with the sponsor so accountability is explicit. This creates a workable control environment without halting delivery.
Question 16Project and programme context
Two projects in the same portfolio are competing for the same scarce specialist team. From a portfolio perspective, the correct approach is to:
- prioritise and schedule the work against strategic value and overall capacity at portfolio level Correct answer.
- cancel the lower-profile project without any assessment
- run both simultaneously and let the specialists decide their own allocation
- let both project managers negotiate privately and accept whichever wins
Explanation
Portfolio management resolves resource contention by prioritising work according to strategic contribution and available capacity. Private negotiation or unilateral cancellation bypasses that coordination.
Question 17Project and programme context
A project's business case shows a positive return only if a dependent project delivers its enabling system. How should the project manager treat this dependency in the project context?
- Replan the project to build the enabling system itself without approval
- Ignore it because the dependency lies outside the project's scope
- Assume the other project will deliver and remove the risk from the register
- Record it as an external dependency and assess the risk to the business case with the sponsor Correct answer.
Explanation
Dependencies outside the project's control can undermine the business case and must be recorded, assessed and owned with the sponsor. The business case is only valid if its assumptions, including dependencies, hold.
Question 18Project and programme context
A programme director wants to close a tranche although one constituent project is forecasting a benefits shortfall. What is the most defensible programme-level position?
- Transfer the shortfall to the finance function as an accounting matter
- Close the tranche unchanged because project closure decisions are purely local
- Assess the shortfall against the programme business case and decide whether benefits, timing or scope must be rebalanced before transition Correct answer.
- Delay all programme reporting until the shortfall is resolved by the project
Explanation
At programme level, decisions are judged against the programme business case and the delivery of strategic benefits. A forecast shortfall should trigger an assessment of whether benefits, timing or scope need rebalancing before the tranche closes.
Question 19Project and programme context
An organisation applies a 'three lines' assurance model. A project manager is told internal audit will review the project independently. Which statement correctly places this activity?
- It replaces the project board's responsibility for approving stage boundaries
- It is a second-line function that sets the project's tolerance levels
- It is a third-line independent assurance activity, distinct from the project's own assurance arrangements Correct answer.
- It is a first-line control performed by the delivery team as part of quality assurance
Explanation
In the three lines model, operational management owns controls in the first line, risk and compliance functions provide second-line oversight, and internal audit provides independent third-line assurance. Independent audit therefore sits apart from the project's own assurance.
Question 20Project and programme context
A project is delivered into a host organisation that will not accept the new process, even though the technical solution works. Which contextual factor has been most neglected?
- The organisational readiness and business change needed to embed the outputs Correct answer.
- The configuration of the technical infrastructure
- The accuracy of the project's cost forecast
- The number of risks recorded in the risk register
Explanation
Adoption depends on organisational readiness, capability and change management in the receiving environment, not only on technical delivery. Neglecting the host organisation's capacity to absorb change prevents benefits from being realised.
Question 21Stakeholder and communications management
In stakeholder analysis for a project, what does the power/interest grid primarily help the project manager determine?
- The technical complexity of each stakeholder's requirements
- The communication strategy appropriate for each stakeholder group Correct answer.
- The chronological order in which stakeholders should receive deliverables
- The contractual penalties attached to each stakeholder agreement
Explanation
The power/interest grid classifies stakeholders by their ability to influence the project and their concern about its outcomes. Each quadrant then maps to a tailored engagement approach, from manage closely to monitor. It does not sequence deliverables or assess technical scope.
Question 22Stakeholder and communications management
A project manager identifies a regulator who has high power but low interest in the project. According to the power/interest grid, which engagement approach is most appropriate?
- Ignore until the regulator raises a concern
- Keep satisfied through periodic, concise updates Correct answer.
- Manage closely with daily interactive engagement
- Monitor with minimal effort and no reporting
Explanation
High-power, low-interest stakeholders can significantly affect the project but do not want heavy involvement. The standard approach is to keep them satisfied with sufficient, well-targeted information so they remain supportive without being overloaded. Monitoring only suits low-power, low-interest parties.
Question 23Stakeholder and communications management
Which document formally records who will receive which project information, in what format, and at what frequency?
- The communications management plan Correct answer.
- The risk register
- The project charter
- The stakeholder register
Explanation
The communications management plan defines the who, what, when, how, and by whom for project information flows. The stakeholder register identifies and classifies stakeholders but does not specify the reporting schedule. The charter and risk register serve different purposes entirely.
Question 24Stakeholder and communications management
A stakeholder register entry typically includes which combination of attributes?
- Cost baseline, schedule baseline, and quality metrics
- Identification details, role, influence, expectations, and engagement classification Correct answer.
- Risk probability, impact, and response strategy
- Lessons learned, change requests, and issue logs
Explanation
The stakeholder register records identifying information, organizational role, level of influence, expectations, and a classification such as internal/external or supporter/neutral/resister. Baselines, risk data, and issue logs are maintained in separate project documents.
Question 25Stakeholder and communications management
During execution, several stakeholders complain they are receiving technical reports they cannot interpret. Which communication model element most directly addresses this problem?
- The communication channel
- The encoding and decoding process Correct answer.
- The feedback loop
- The noise factor
Explanation
Encoding is how the sender translates meaning into a message, and decoding is how the receiver interprets it. When reports are unreadable to the audience, the sender has encoded in a form the receiver cannot decode, so the encoding/decoding fit is the root issue. Feedback confirms receipt but does not fix an unsuitable format.
Question 26Stakeholder and communications management
What is the primary purpose of the stakeholder engagement plan?
- To document the project budget by stakeholder department
- To list every email sent to stakeholders during the project
- To define strategies and actions needed to involve stakeholders effectively Correct answer.
- To replace the communications management plan
Explanation
The stakeholder engagement plan describes how the project will work with each stakeholder to support their needs and expectations, including desired engagement levels and strategies. It complements, rather than replaces, the communications management plan. It is not a log of correspondence or a budget tool.
Question 27Stakeholder and communications management
A key sponsor becomes disengaged midway through the project. Which action best reflects proactive stakeholder engagement management?
- Remove the sponsor from the stakeholder register
- Wait for the sponsor to raise concerns at the next steering committee
- Escalate immediately to senior management without further assessment
- Reassess the sponsor's engagement level and adjust the engagement strategy Correct answer.
Explanation
Monitoring engagement levels is a continuous process, and deviations should trigger a review of the engagement strategy and tailored corrective actions. Waiting allows disengagement to worsen, and removal from the register is inappropriate for a key sponsor. Escalation without assessment skips the diagnostic step.
Question 28Stakeholder and communications management
Which communication method is most appropriate for conveying a complex, sensitive change to a large, geographically dispersed audience while still allowing questions?
- A live virtual town hall with a moderated Q&A Correct answer.
- A private message to a single team lead
- A one-way written memo only
- An informal corridor conversation
Explanation
Sensitive, complex messages benefit from richer, interactive channels that allow immediate clarification. A live virtual town hall reaches a dispersed audience while preserving a feedback mechanism. One-way memos lack interaction, and informal or single-recipient channels fail to reach the whole audience.
Question 29Stakeholder and communications management
In communication theory, what does 'noise' refer to in the context of project communications?
- The number of stakeholders on a distribution list
- The volume level of a presentation
- Any interference that distorts or disrupts the transmitted message Correct answer.
- The frequency of status reports
Explanation
Noise encompasses any factor that interferes with the accurate transmission or reception of a message, such as jargon, cultural differences, or technical faults. It is not literal audio volume, list size, or reporting frequency. Reducing noise improves communication effectiveness.
Question 30Stakeholder and communications management
A project has stakeholders across three time zones. Which planning consideration most directly affects the choice of communication technology?
- The availability and connectivity constraints of each audience Correct answer.
- The seniority of the project manager
- The color scheme of the project dashboard
- The number of risks in the risk register
Explanation
When selecting communication technology, the project manager weighs urgency, availability, ease of use, and the receivers' environment. Time-zone spread and connectivity constraints directly shape whether synchronous tools are viable. Dashboard styling, risk counts, and PM seniority do not determine technology fit.
Question 31Stakeholder and communications management
Which tool best helps a project manager visualize informal influence and communication pathways that are not captured by the formal organization chart?
- A stakeholder engagement assessment matrix
- A work breakdown structure
- A responsibility assignment matrix
- A network diagram of informal relationships Correct answer.
Explanation
Informal influence and communication networks are best surfaced through sociograms or network diagrams that map relationships between people. The engagement assessment matrix tracks engagement levels, not relationship structure. The RAM and WBS address responsibilities and scope decomposition.
Question 32Stakeholder and communications management
During a status meeting, a stakeholder consistently raises issues that were already resolved. Which communication practice would most reduce this recurrence?
- Removing the stakeholder from future meetings
- Maintaining and circulating an action and decision log Correct answer.
- Increasing the meeting frequency
- Shortening the meeting duration
Explanation
A maintained action and decision log gives stakeholders a shared, authoritative record of what was decided and closed. Circulating it before and after meetings reduces re-litigation of resolved items. Shortening or increasing meetings does not address the information gap, and exclusion is inappropriate.
Question 33Stakeholder and communications management
What distinguishes a stakeholder who is classified as a 'resister' in the engagement assessment matrix?
- They are aware and actively opposed to the project or its outcomes Correct answer.
- They are aware but neither supportive nor opposed
- They are aware and actively supportive of the project
- They are unaware of the project and its impacts
Explanation
The engagement assessment matrix classifies stakeholders as unaware, resistant, neutral, supportive, or leading. A resister is aware of the project and its potential impacts but actively opposes it, which signals a need for targeted engagement. Neutral and supportive describe different positions.
Question 34Stakeholder and communications management
A project manager must report to executives who want only outcomes and exceptions, while the technical team needs detailed specifications. What does this best illustrate?
- The need to standardize a single report for all audiences
- The need to reduce the number of stakeholders
- The need to eliminate the communications management plan
- The need to tailor communications to different stakeholder information needs Correct answer.
Explanation
Effective communication planning recognizes that different stakeholders require different levels of detail, format, and frequency. Tailoring satisfies both executive and technical audiences. A single standardized report would under-serve one group, and reducing stakeholders or abandoning the plan does not address the need.
Question 35Stakeholder and communications management
Which of the following best describes the relationship between stakeholder identification and stakeholder analysis?
- Identification is optional when analysis is performed
- Analysis precedes identification and determines who exists
- Identification lists stakeholders; analysis evaluates their influence, interest, and engagement Correct answer.
- Identification and analysis are identical activities performed once
Explanation
Identification produces the list of people and groups affected by or able to affect the project. Analysis then assesses their influence, interest, expectations, and engagement levels to guide strategy. The two are sequential and complementary, not identical or interchangeable.
Question 36Stakeholder and communications management
A critical stakeholder is identified as 'leading' in the engagement assessment matrix. What does this classification indicate?
- They are actively engaged in ensuring the project succeeds Correct answer.
- They are neutral toward the project
- They are resistant to the project
- They are unaware of the project
Explanation
A 'leading' stakeholder is actively engaged in making the project succeed, the highest engagement level in the matrix. This differs from supportive, which is favorable but less actively involved. Unaware, neutral, and resistant describe lower or opposing positions.
Question 37Stakeholder and communications management
Which factor is most important when deciding whether to use a pull or push communication method for a status update?
- The project manager's writing style
- The number of characters in the report
- The color of the report template
- The urgency and the audience's preference for self-service access Correct answer.
Explanation
Pull methods let recipients access information when they need it, while push methods distribute it directly. The choice depends on urgency, audience preference, and the need for immediate awareness. Template color, character count, and writing style do not determine the push/pull decision.
Question 38Stakeholder and communications management
A project manager discovers that a powerful stakeholder was omitted from the stakeholder register. What is the most appropriate immediate action?
- Delegate the issue to the team without documentation
- Proceed and add the stakeholder only at project closure
- Ignore the omission because the project is already underway
- Update the stakeholder register and reassess engagement and communication needs Correct answer.
Explanation
Stakeholder identification is iterative, and omissions should be corrected as soon as discovered. The register must be updated and the engagement and communication approaches reassessed for the new stakeholder. Delaying to closure or ignoring the gap leaves the project exposed to unmanaged influence.
Question 39Stakeholder and communications management
Which statement best captures the principle of 'manage stakeholder engagement' as a project process?
- It is limited to distributing status reports
- It applies only to external stakeholders
- It is a continuous process of communicating, negotiating, and addressing concerns Correct answer.
- It is performed once during initiation and then closed
Explanation
Managing stakeholder engagement is ongoing throughout the project, involving communication, negotiation, and resolution of concerns to foster appropriate involvement. It applies to internal and external stakeholders alike. It is not a one-time initiation activity or merely report distribution.
Question 40Stakeholder and communications management
A team member reports that a stakeholder's expectations conflict with the documented project scope. What should the project manager do first?
- Ignore the conflict because scope is already baselined
- Document the conflict and engage the stakeholder to reconcile expectations with scope Correct answer.
- Immediately change the scope to match the stakeholder's expectations
- Escalate to the sponsor without any analysis
Explanation
Conflicting expectations should be documented and addressed through engagement and negotiation, often via the change control process if scope adjustment is warranted. Unilateral scope change bypasses governance, and ignoring the conflict leaves it unresolved. Escalation without analysis skips the diagnostic step.
Question 41Scope and requirements management
In requirements management, what distinguishes a project scope statement from a requirements traceability matrix?
- The scope statement is created only during project closure, while the traceability matrix is created during initiation.
- The scope statement documents deliverables, boundaries, and acceptance criteria, while the traceability matrix links requirements to their sources and downstream artifacts. Correct answer.
- The scope statement records the schedule baseline, while the traceability matrix records the cost baseline for each requirement.
- The scope statement lists approved change requests, while the traceability matrix lists rejected change requests.
Explanation
The scope statement defines what is in and out of the project, including deliverables, exclusions, constraints, and acceptance criteria. The traceability matrix is a relationship tool that maps each requirement to its origin, tests, and deliverables so coverage can be verified. These are complementary but distinct documents.
Question 42Scope and requirements management
A project manager needs a formal document that authorizes the project and gives the project manager authority to apply organizational resources. Which document is required?
- The project management plan
- The project charter Correct answer.
- The work breakdown structure
- The requirements management plan
Explanation
The project charter formally authorizes the existence of the project and empowers the project manager to commit organizational resources to activities. It is issued by the sponsor or initiating entity before detailed planning begins. The other documents are planning outputs created after authorization.
Question 43Scope and requirements management
During scope planning, a team decomposes the total project scope into progressively smaller deliverables until reaching work packages. What is the primary purpose of this decomposition?
- To estimate cost and duration more reliably and to assign clear ownership of work Correct answer.
- To eliminate the need for a scope baseline
- To assign functional managers as approvers for each requirement
- To replace the requirements traceability matrix with a schedule
Explanation
Decomposition into a WBS produces work packages at a level where cost, duration, and responsibility can be estimated and assigned with confidence. It makes the total scope visible and manageable. It does not replace baselines or traceability artifacts.
Question 44Scope and requirements management
A stakeholder requests a new reporting dashboard two weeks after the scope baseline was approved. Which action best reflects integrated change control for scope?
- Document the request, assess its impact on scope, schedule, and cost, and route it through the change control process Correct answer.
- Reject the request because the baseline is approved and cannot change
- Ask the developer to build it quietly and record the effort as contingency
- Add the dashboard to the WBS and inform the team at the next stand-up
Explanation
Approved baselines are changed only through the perform integrated change control process. The request must be recorded and evaluated for impact before a change control board or authorized approver decides. Implementing work without approval undermines the baseline.
Question 45Scope and requirements management
Which statement accurately describes the relationship between product scope and project scope?
- Product scope describes the features and functions of the product, while project scope describes the work required to deliver it. Correct answer.
- Product scope describes the work to be performed, while project scope describes the features and functions of the deliverable.
- Product scope and project scope are synonyms and are used interchangeably in the scope baseline.
- Product scope applies only to IT projects, while project scope applies to all projects.
Explanation
Product scope concerns the characteristics and functions that define the product or service, measured against product requirements. Project scope concerns the work the team must perform to create that product, measured against the project management plan. Completion of project scope is assessed differently from product acceptance.
Question 46Scope and requirements management
Which tool is specifically designed to verify that every requirement has been tested and delivered by tracing it forward to design, build, and test artifacts?
- A risk register
- A requirements traceability matrix Correct answer.
- A stakeholder engagement assessment matrix
- A resource histogram
Explanation
A requirements traceability matrix records each requirement's origin and links it forward to design components, deliverables, and test cases. This supports verification that no requirement is dropped and no unrequested work is added. The other tools address resourcing, risk, and stakeholder engagement.
Question 47Scope and requirements management
A project manager is preparing the requirements management plan. Which content belongs in that plan rather than in the requirements documentation itself?
- The list of approved change requests affecting requirements
- The test results demonstrating each requirement was met
- The detailed functional requirements and their acceptance criteria
- The process for prioritizing requirements and the traceability structure to be used Correct answer.
Explanation
The requirements management plan is a process document describing how requirements will be elicited, analyzed, prioritized, documented, and traced. It defines configuration of the traceability structure and change handling. The actual requirement statements, change records, and test results live in other artifacts.
Question 48Scope and requirements management
A client says the system must be 'user-friendly and fast.' Which action best applies requirements analysis to make these statements usable?
- Defer them to the closing phase so the client can judge the final product
- Record them as assumptions in the risk register and proceed
- Convert them into measurable acceptance criteria such as page load under two seconds for defined transactions Correct answer.
- Accept them as-is because customer satisfaction is subjective
Explanation
Vague requirements must be analyzed and made testable through measurable acceptance criteria. Specifying thresholds and conditions allows objective verification during control quality and acceptance. Leaving them ambiguous invites disputes at acceptance.
Question 49Scope and requirements management
A project manager uses focus groups, facilitated workshops, and questionnaires to gather requirements. Under which process are these techniques applied?
- Create WBS
- Control Scope
- Collect Requirements Correct answer.
- Define Scope
Explanation
Collect Requirements is the process where elicitation techniques such as interviews, focus groups, facilitated workshops, questionnaires, and prototypes are used to determine and document stakeholder needs. Define Scope then develops the detailed scope statement from those outputs.
Question 50Scope and requirements management
Which characteristic identifies a well-formed requirement statement?
- It omits acceptance criteria so the team can innovate freely
- It combines several unrelated capabilities into one statement to save space
- It is verifiable, unambiguous, and traceable to a business need Correct answer.
- It is written so that only the original author can interpret it
Explanation
Good requirements are clear, unambiguous, verifiable, and traceable to a source or business need. These qualities enable testing and coverage analysis. Combining unrelated capabilities or omitting criteria reduces verifiability and increases ambiguity.