PMP · Question #13
During a system demo, a project stakeholder rejects the features completed from the most recent user stories. According to the stakeholder, the product does not meet the quality standards required by
The correct answer is B. Ensured the stakeholder concerns were properly addressed in the iteration to avoid future. To prevent a stakeholder from rejecting features due to unmet regulatory quality standards, the project manager should have ensured these specific stakeholder concerns were identified and properly addressed throughout the development iteration.
Question
During a system demo, a project stakeholder rejects the features completed from the most recent user stories. According to the stakeholder, the product does not meet the quality standards required by regulations. What should the project manager have done to avoid this?
Options
- AEnsured that the project sponsor understood the scope of the project to avoid any future
- BEnsured the stakeholder concerns were properly addressed in the iteration to avoid future
- CReviewed with the product owner that all acceptance criteria were met for the stories worked on
- DReviewed with the product owner that all the stories worked on in the iteration were in the project
How the community answered
(59 responses)- A3% (2)
- B76% (45)
- C7% (4)
- D14% (8)
Why each option
To prevent a stakeholder from rejecting features due to unmet regulatory quality standards, the project manager should have ensured these specific stakeholder concerns were identified and properly addressed throughout the development iteration.
While ensuring the project sponsor understands the scope is important, it does not directly guarantee that specific regulatory quality standards will be identified, incorporated, and met within the product's features.
To avoid a stakeholder rejecting features for failing to meet regulatory quality standards, the project manager should have proactively engaged to understand and ensure these critical concerns were adequately identified, integrated, and addressed within the iteration's work, including design, development, and testing activities, to guarantee compliance.
Reviewing whether acceptance criteria were met is crucial, but if the regulatory quality standards were not adequately defined or included within those acceptance criteria, simply meeting the existing criteria would not prevent a rejection based on external regulatory requirements.
Reviewing that all stories worked on are part of the project's scope addresses scope control, but it does not directly ensure that the features meet required regulatory quality standards or prevent a stakeholder from rejecting them on that basis.
Concept tested: Requirements Management, Quality Assurance, Stakeholder Engagement
Topics
Community Discussion
No community discussion yet for this question.