Exam PK0-005 topic 1 question 126 discussion

I understand why people would say CCB but in real life they’re not going to host a CCB to just fix a typo. A CCB would be for major changes that impact the scope and cost of the project, a typo is NOT one of them. But I definitely see why academia would say “well actually by the book every change must be amended by a CCB.” I host CCB’s in real life and small edits like typos don’t go through a CCB.

The PM can authorize minor, non-impacting edits like typo corrections without formal approval. Don't overthink it...

In the Real World I think the PM would just fix the typo. But I think according to Comptia etc officially only the CCB can make changes to the projects baselines.

A project manager can make typo changes without the need for the Change Control Board (CCB) to be involved. Typo changes are considered minor and do not impact the project scope, schedule, or budget significantly. The project manager has the authority to make such changes as part of their day-to-day responsibilities. However, it is good practice for the project manager to inform the CCB or relevant stakeholders about the change to ensure transparency and maintain proper documentation. This helps in keeping everyone informed and accountable for any changes made to the project.

For a typo as minor as this one in the project management plan, the decision maker who would most likely authorize the change for the correction would typically be "A. PM" (Project Manager). In many organizations, small changes like correcting typos usually fall under the authority of the Project Manager and do not require formal approval from higher-level entities like the Change Control Board (CCB) or the project sponsor.

This one is tough and I was stuck between A and B although the issue at hand is very minor I’m going think the way comptia is going to want us to think and they’re probably going to with CCB since technically it should go to CCB since it’s an officially document but in the real world it would probably be PM

A is correct. -Though a project is filled with changes, not every change needs to go through a change control process. The purpose of change control is to manage changes to the scope, time, and cost baselines. Therefore, changes that do not affect the baselines would not activate the change control process (certmaster-learn-for-project-pk0-005#read/section/change-control-overview-2)

The Change Control Board (CCB) is a designated group or committee responsible for reviewing and approving changes to the project's scope, schedule, budget, or other project components. The CCB ensures that changes are evaluated and approved based on their potential impact on the project's objectives, constraints, and overall management. In this case, a typo in the project management plan is considered a change to the document. While it may seem like a minor change, any modification to project documentation should go through the proper change control process to maintain consistency and accuracy.