Exam PMP topic 1 question 729 discussion

I believe the correct answer is C. Any thoughts please? I know that the product owner gathers all the requirements and all, but this concern should be reviewed with the entire team and not just the product owner. Maybe after discussing with the entire team, the PM connects with the PO to discuss it further.

C is alright

Iteration review is a meeting that PO and team have with the customer or the main stakeholder. In this case the stakeholder raised some concerns with PO and team. The project manager has to do FIRST THING FIRST is to gather information about the concern that stakeholder raised. so option D is good

D for me. The problem with the question is that he does not include the stakeholders in any meeting. Because it's agile first must be discussed with the owner.

Stakeholder raised concern for final product and there is no enough detail to review requirement documentation. There is not enough detail to discuss with team. PO should be informed first about concern and since PO create backlog items, they should take more detail about concern.

I think Option A : is wrong because it says (Concern) which is not an issue but it's a risk Option C: is logical answer

Noticed that we are confused between A and C, where right answer shows D, Why ? if we review this question carefully, it says "a stakeholder raised a concern about the final product." meaning it's a Agile project, with that Product owner is the representative of stakeholder/customer so I go with D.

When a stakeholder raises a concern about a deliverable, the first step for a project manager should be to understand the nature of the concern in relation to the project requirements. By doing this, the project manager can ascertain whether the concern is valid or if it's a potential scope change. Therefore, the best first action would be: C. Discuss this with the team and review the project requirements documentation. This step helps to ensure that the concern aligns with the defined requirements, and if not, it provides a basis for the subsequent actions. Once the project manager and team have a clear understanding of the concern in relation to the requirements, further steps can be taken, such as engaging the sponsor, product owner, or logging the concern as an issue.

It's A. This is from Agile Guide. https://www.pmi.org/learning/library/motivation-increase-project-team-performance-7234

I think that the Team should be met with first and the documentation reviewed before talking to anyone else. Key word being FIRST.

C. Discuss this with the team and review the project requirements documentation

Yeah it's A. Discuss, Log and move on.

First discuss with team. Once the team has a clear understanding of the concern and any possible issues related to the deliverable, they can decide on the appropriate course of action, such as putting the stakeholder's concern in the issue log (option A), setting up a meeting with the sponsor (option B), or discussing the concern with the product owner (option D). But the initial review with the team and the requirements documentation is critical to gather the necessary context and information.

A seems the most rational and the first thing I would do. Yeah I might look at requirements, but I would talk with my team first, maybe there is just a misunderstanding.

Discussion with the team would come first. No reason to jump to conclusions, just log the issue.

The question is, "What should the project manager do first?" PMBOK 4.3.3.3 - Issues Log to log issues that come up through out the project lifecycle. First thing you do is put the new issue in the Issue Log.

The first step should be to acknowledge and document the stakeholder's concern by adding it to the issue log. This will help to ensure that it is not overlooked and can be addressed by the appropriate team members. The project manager can then discuss the issue with the team and review the project requirements documentation to determine the best course of action. If necessary, the project manager can also set up a meeting with the product owner or sponsor to discuss the issue further.