PMP · Question #1304
A project manager is managing a new development program to automate some technical functions. During project kickoff, the project manager expresses the need for a technical architect to support the pr
The correct answer is A. Share the existing technical architect so they can be allocated to the current project and other. Given that the existing technical architect has valuable knowledge and is only needed for a moderate amount of time, the project manager should share the resource to leverage their expertise without fully reassigning them from portfolio-level duties.
Question
A project manager is managing a new development program to automate some technical functions. During project kickoff, the project manager expresses the need for a technical architect to support the project for a moderate amount of time. The project sponsor informs the project manager about an existing technical architect who possesses valuable knowledge but is already assigned at the portfolio level. What engagement model should the project manager use for the technical architect role to ensure project success?
Options
- AShare the existing technical architect so they can be allocated to the current project and other
- BHire a new technical architect who would be solely dedicated to the current project.
- CHire a new technical architect who would be shared between the current project and other
- DAssign the existing technical architect to solely be dedicated to the current project.
How the community answered
(31 responses)- A74% (23)
- B13% (4)
- C3% (1)
- D10% (3)
Why each option
Given that the existing technical architect has valuable knowledge and is only needed for a moderate amount of time, the project manager should share the resource to leverage their expertise without fully reassigning them from portfolio-level duties.
Sharing the existing technical architect is the most effective engagement model because it allows the project to benefit from their valuable, pre-existing knowledge and experience while accommodating their current portfolio-level responsibilities. This approach optimizes resource utilization for a moderate time commitment without incurring the cost of a new hire.
Hiring a new, solely dedicated technical architect is an expensive and unnecessary option, especially when an existing knowledgeable resource is available and only a moderate time commitment is needed.
Hiring a new shared technical architect still incurs the cost of recruitment and onboarding and might not provide the same 'valuable knowledge' as the existing portfolio-level resource.
Assigning the existing technical architect solely to the current project would remove them from their critical portfolio-level duties, which might not be feasible or justified by the 'moderate amount of time' required for the new project.
Concept tested: Resource allocation strategy
Source: https://www.pmi.org/pmbok-guide-standards/foundations/pmi-lexicon#resource-management-plan
Topics
Community Discussion
5Just to confirm my understanding here, the question is basically asking what to do when a key resource is needed only moderately but is already tied up at the portfolio level. Option A makes the most sense because the project manager only needs the architect for a moderate amount of time, which aligns perfectly with a shared engagement model. The existing architect already has valuable knowledge, so sharing them across projects maximizes their expertise without pulling them completely away from their portfolio duties. D would be overkill for a moderate need and would likely disrupt the portfolio, while B and C ignore the fact that the sponsor already pointed you
Picked A on my exam last month because the stem says moderate amount of time and the architect already exists at the portfolio level, so sharing them is the only model that fits without stepping on portfolio commitments. Anyone know if the exam always treats portfolio level resources as shared by default, or would that change if the project was flagged as high priority?
Saw this on my exam, the architect is shared since they are at portfolio level.
Agreed on portfolio level for the architect, but remember that shared resources can also show up at the program level depending on how the question frames the governance structure, so I'd watch for that wording distinction.
I first leaned toward B since a dedicated hire seemed like the cleanest way to get the architect's full attention. But one of the senior PMs on my team pointed out that the sponsor specifically mentioned the existing architect's valuable knowledge, which you would lose by bringing in someone new. Since the project only needs a moderate amount of the architect's time and the person is already assigned at the portfolio level, sharing them across projects makes the most sense. That lines up with how resource leveling works in practice, you negotiate for a percentage of someone's time rather than pulling them off their other commitments entirely.