A transit agency describes one coordinated suite of related station upgrades sharing combined benefits as its “portfolio.” What correction should the associate make?
Select an answer to reveal the explanation.
Short Explanation
Related station upgrades managed together for combined benefits—that’s a program. A portfolio is the bigger strategic collection across themes and funding pools, not one coordinated suite.
Full Explanation
A program coordinates related projects to obtain combined benefits not available from managing them separately. A transit agency’s coordinated suite of related station upgrades sharing combined benefits is a program, not the broader portfolio. Keeping the portfolio label because any group of stations is automatically a portfolio fails by concept: a portfolio is the enterprise-level collection of projects, programs, and other work prioritized for strategy and funding—related station upgrades pursuing shared benefits fit program. Renaming it a single project even though multiple related upgrades are involved fails because multiple related temporary endeavors with distinct deliverables are projects under a program, not one monolithic project by default. Labeling it operations because stations remain open during construction fails because keeping stations open is an operational constraint during delivery; it does not redefine capital upgrades as BAU operations. Exam caveat: CAPM terminology traps swap program and portfolio—ask whether the focus is related-project benefit coordination (program) or strategic selection across the organization (portfolio). Operational check: establish program-level benefit metrics across stations, keep separate project plans for each upgrade, and reserve portfolio reviews for ranking this program against other agency investments.