Five projects are competing for the same specialist employees. Senior managers currently approve projects based on who argues most persuasively. What is the strongest reason to introduce a project priority system?

The current method of approving projects is subjective ("who argues most persuasively") and leads to inconsistent decision-making, especially when resources are limited. A project priority system aims to bring objectivity and consistency to project selection.

• a. To eliminate all management judgement: This is incorrect. While a priority system reduces subjectivity, it typically guides management judgment rather than eliminating it entirely, as strategic decisions often still require human input.
• b. To ensure projects are ranked consistently against strategic and resource criteria: This is correct. A priority system provides a standardized framework with objective criteria (like strategic alignment and resource availability) to consistently evaluate and rank projects, addressing the problem of subjective approval.

In a functional organizational structure, employees are grouped by their specialized functions (e.g., engineering, marketing). Project managers in such structures typically have limited authority and must negotiate with functional managers to acquire and utilize resources (staff). Functional managers prioritize their departmental goals.

The project manager "repeatedly waits for departmental managers to release staff, causing delays." This directly highlights a lack of authority for the project manager over project resources and a dependency on functional managers. This often leads to resource conflicts and delays because functional managers may prioritize their departmental work over project needs.

The most evident structural weakness is the lack of project manager authority and control over resources, leading to resource contention and delays. (The options for this question are not visible in the image, so a specific option cannot be selected).