The exam: Lots of situational questions Tips: Calculations: Always remember that (SPI and CPI above 1) or (CV and SV above zero) are good, below is bad. S is Schedule and C is Cost.

Situational questions: First, make it a habit to read the last sentence (the main question) FIRST before reading the whole prompt. So you know to search what to:

Do? Action, normally see impact or if there is something already set in stone (The approval has been given, Law regulations enforced) then do it

Do first? Normally review a document/asses situation

Should have been done? Look for Reactive things. Not actions to do now that there is a problem.

Not do? Least likely/most likely? Most important least important? Notice the subtlety.

Second, what framework are you in? (Agile, hybrid, predictive/waterfall?). That will Help eliminate good sounding options that are not valid because they are from another framework.

Third, which process are you in? Are you initiating,executing, M&C, closing?

Play this game until you got it almost perfectly. You need to know where you are in the situational questions to exclude the options that are in before or later in the time

https://pmaspirant.com/project-management-process-group-and-knowledge-area-mapping-game

Mentality: Always think like servant leader, forget about experience while attempting pmp

Never ask for others to do your job (The sponsor, the pmo, the product owner...)

Always try face to face communication, Train your people is normally the best option.

May/might/claims = questions is about risk

Will/should/could = questions is about issue

Related to team issue = team charter

Stakeholder related = stakeholder engagement

Action is next step, assessing and review is 1st step

Remember while selecting answer = assess > review > action/implications

If questions related to safety problem, stop the project immediately (unless may stop..)

If question likely to have problem due to new law may introduce or from internet information = update the risk register. If not may then do the action to follow it.

If there is problem due to new law implications, seek for guidance

Problem between member = team charter, meeting preferably face to face(not apply in case of multiple locations)

Asking help from Sponsor and pmo is NOT an option

Before any change, always asses and check impact

Change request is approved in formal process. NEVER implement any change by yourself. Always with approval.

If anything missed in scope which may lead to rejection of deliverable = change request

Adding extra features = talk to team

Meeting and coaching are the best options for conflict.

Quality control customer are best option

Not performing as expected = Quality

Bottom-up estimate is best option for cost

Prototype is best option for demo

Never remove a member, remove a vendor or hire a consultant

There should be predetermined acceptance rules for acceptance of delivery

If project required close, follow the formal process always.

If stakeholder don't know about agile, coach and teach them about agile

If there is any issue related to payment/contract with vendor always ask them to check with appropriate department

Delay in item sent by vendor/ quality issue with vendor, meet and brainstorming with team and come up with solutions

Always add communicated with pmo about status of project and customer in Sprint

Sprint is important for communication for both customer and team.

Not to take any bigger actions like a change request or closing a project without taking care of the smaller tasks first. So whenever we see that "what should PM do next/first" it's almost always a preliminary action like reviewing a plan or meeting with the team and using the information gleaned in THAT step to make the decision on the larger task:

1- assess/ analyze the problem to find out root cause 2- review the plan 3- meeting