Exam PMP topic 1 question 367 discussion

i would go with a, since it was approved so we need to submit change request

A. Make a change request and get formal approval from the project owner. Explanation: In PMP methodology, any change to an already approved design must go through the formal change control process. This involves: - Submitting a Change Request – The project manager documents the proposed design revision and submits a formal Change Request (CR). - Evaluating the Change – The impact on scope, schedule, cost, quality, and risk is assessed. - Getting Approval – The Change Control Board (CCB) or project owner formally approves the change before implementation. - Updating Project Documents – Once approved, project plans, design documents, and other records are updated accordingly. - Communicating with Stakeholders – The client and relevant team members are informed about the approved change.

A is not right because you should get approval from CCB but not 1 person - Project Owner. C is the next step after getting approval from CCB.

I choose C

Dumb PMI question. If they had said the new desing or the redesign has alreay been approved, I would have picked C. They said the design has already been approved as if the faulty design is the context. Dammit

I choose C on the notion that an agreement by all players to revise the design to avoid system defect when deployed indicate that the revision will introduce new features and functionalities. On the risk management phenomenal, any new control introduced brings about new risk. This is what is referred to as secondary risk, and a risk assessment is required to ascertain whether the revised design will not introduce new challenges. So when the design is already approved, the PM is definitely oblige to perform proof concept to ensure the revised design will not introduce new challenges that will undermine the project. So C is the best next step the PM should undertake before proceeding on any other steps. I strongly bow down for C as the obvious answer to this question.

A proof of concept demonstrates that a proposed system or idea will work as intended. The goal is to show that it works and can be implemented. It is built in the early stage of product development. It doesn't usually involve user feedback and is evaluated by the team.

B and A are good answers. We have an approved document/ request and saw a problem. To me, it's more B than A just because B includes A when it says "follow the CR process" but adds the need to talk to the client. If I can start a CR process it means that I already have, or will have, a plan for HOW to change it. may be a proof of concept, maybe some document, IDK... I don't think it must go through C

It correct answer has to be C - Conduct a proof of concept to make sure there are no problems in the revised design! It can NOT be B - Inform the client of the problem and follow the change request process! Because, as written in the Question - "The design is already approved"! - That means that the Change request process is fulfilled! Therefore there is no need to aprove it again! The "best" answer remains C!

B. Inform the client of the problem and follow change request process. Since design is revised . since we have to go for a formal approval process even though we agreed with all

B. Inform the client of the problem and follow the change request process

I think C is correct. From the description, the team has identified a change (on the approved design), the typical change control process after change identification is to raise a change request to CCB, but A is wrong as the formal approval is not from the project owner, it’s from CCB (steering committee etc). B sounds promising, there’s no information saying it’s an Agile project, so PM can communicate this with the client. But informing the client of the problem sounds like part of the change implementation. Think about that, they are your client, instead of presenting them with the problem, it’s more important and effective that you can also provide the solution, and the solution should be approved by the CCB first. So B is not yet the step to do. C sounds promising. It describes the Change Evaluation, which typically occurs before a change request is submitted to the CCB, and which is exactly the current situation. D sounds great but it also should be done after getting the formal approval from CCB.

my answers is C, the design Problem was reviewed by the Project Owner and team member , Project owner can be a Project Sponsor ( external or Internal ), Executive, or Director , since all agreed to revised and approved. so PM doesn't have to inform the client about the change since we can consider them client

I think C. All agreed to changes, next step is to poc it before putting up formal change request

The essence of the matter seems to revolve around whether it is possible to bypass the formal approval stage simply based on the statement of "Agreed." I firmly believe that obtaining formal approval is imperative to prevent any procedural issues. Therefore, I assert that A is correct.

The correct answer is B. The project manager should inform the client of the problem and follow the change request process. This will help to ensure that the client is aware of the problem and that the change is made in a controlled manner. The other options are not as effective. Option A would involve making a change request and getting formal approval from the project owner. This would not be necessary, as the client is the one who needs to approve the change. Option C would involve conducting a proof of concept to make sure there are no problems in the revised design. This would be unnecessary, as the client has already agreed to the change. Option D would involve amending the design specifications and passing them to the development team for reprogramming. This would be premature, as the client has not yet approved the change.

The change should have been approved by the CCB