Sammy is the project manager for her organization. She would like to rate each risk based on its probability and affect on time, cost, and scope. Harry, a project team member, has never done this…

Harry's claim that risk probability and impact must always consider all objectives cumulatively is incorrect; PMBOK supports per-objective scoring as a valid alternative.

The risk probability and impact matrix is one tool among many for risk assessment, not the exclusive or mandatory approach.

Being the project manager does not by itself make Sammy correct; the answer requires a valid technical justification, not an appeal to authority.

PMBOK explicitly allows organizations to evaluate risks against each project objective individually, producing separate risk scores for time, cost, scope, and quality. This approach provides more granular insight into how a specific risk may affect different aspects of the project differently. Creating separate scores is a recognized and valid approach, not a methodological error as Harry suggests.