18.3 Managing Projects and Portfolios

18.3 Managing Projects and Portfolios

Quick Answer: Task A.23 is manage projects and portfolios of projects. A project is a temporary unique deliverable. A program coordinates related projects for a shared benefit. A portfolio is the governed set of work selected under capacity. Demand management decides what a new yes displaces.

Chapter 15.4 put the IT plan and a keep/kill/combine portfolio on the page. Chapter 13 taught scope, schedule, budget, and quality inside an implementation. A.23 is the leadership skill that sits between them: classify the work, manage demand, and run the stack so strategy does not drown in “small requests.”

CPHIMS practice questionsPractice questions with detailed explanations

Project, program, portfolio, operations

HIMSS does not publish a CPHIMS-official intake score or mandate a PMI template. The distinctions still decide stems.

Examples that survive stems:

• Project: Turn on electronic prescribing of controlled substances in twelve clinics with a named acceptance test.
• Program: Closed-loop medication safety—dispensing interoperability, barcode administration, pharmacy verification redesign, downtime med-pass, and benefits measurement. Managing those as unrelated projects will “finish” devices and still miss the harm aim.
• Portfolio: The fiscal-year mix of run (identity modernization), grow (ambulatory access tools), and transform (hospital-at-home) that the A.3 forecast said the staff can absorb.

A PMO is a support and governance function. It does not own clinical outcomes. A project manager runs a project. A program manager integrates dependent projects. A portfolio owner (often the CIO with an integrated operations–finance–quality–HIT committee) selects and stops work. Do not staff a PMO and call the org chart “portfolio management.”

Demand management

Demand management is the process that turns incoming wants into classified work and an honest capacity conversation. Without it, you get forty “priority-one” projects, shadow work funded by a department, and an official portfolio that is only a slide.

Typical flow:

1. Intake with a written organizational or departmental objective (A.1/A.4), not a vendor demo.
2. Classify: operations, project, or component of an existing program. “Just a small interface” is usually a project or a program increment.
3. Estimate capacity in the scarce unit—often skilled people from 18.1, not dollars alone.
4. Compare to the portfolio. What in-flight work uses the same identity, interface, informatics, or testing pool?
5. Decide: accept, defer, combine, or refuse. Publish what the new yes displaces.
6. Charter only after the decision. A charter is not an intake form.

Shadow projects are demand that skipped the gate. They consume the same competent people, create unowned interfaces, and later appear as “urgent” production risk. Treat them as unauthorized portfolio entries, not as entrepreneurial spirit. The operational and contract treatment of shadow IT is section 18.4; A.23’s job is to stop pretending the official list is the real list.

Managing the work once selected

For projects, A.23 expects the usual controls in a healthcare key: scope that names clinical acceptance, a schedule that respects safety freezes, a budget that includes internal labor, testing (chapter 14), and a named operational owner for the day after go-live. Green bars with no benefits owner are theater.

For programs, add integration: shared risk register, shared identity and environment plan, sequenced go-lives, and a benefits measure that no single project can claim alone. Killing a component because it is late may be correct project control and still be wrong program control if the remaining pieces cannot produce the benefit.

For portfolios, add cadence: quarterly keep/kill/combine against the written aims and the actual remaining capacity. Adding a new transform program without stopping something is not management. Resource leveling is people math. If the same three interface analysts appear on every charter, you do not have a portfolio. You have a queue with extra logos.

Stage gates (intake → charter → design → build → test → train → go-live → benefits) are tools. They are not a HIMSS-required waterfall. Iterative delivery still needs portfolio intake and an operational home. “We are agile” is not permission to skip classification or demand management.

People from 18.1 and education from 18.2 are the binding constraint more often than capital. A portfolio that assumes contractors will appear with production competency is not managed; it is hoped.

Distinctions the exam will punish

• Project versus program versus portfolio versus operations.
• Demand management versus project scheduling. Scheduling assumes the work was already selected.
• PMO versus portfolio owner who can kill.
• On time / on budget versus benefits the program exists to create.
• Strategic program versus strategy. The upgrade is still not the organizational aim.

Scenarios and exam traps

Scenario. Closed-loop medications is split into five unrelated projects with five sponsors. Reassemble as a program. The benefit is safer administration, not five green charters.

Scenario. The portfolio list shows 40 priority-one items. That is a demand-management failure. Force ranking against capacity and aims; publish the deferred list. A new yes without a named displacement is not A.23.

Scenario. Cardiology funds a “quick” imaging viewer because official intake is slow. The same identity and interface pool will still do the work. Pull it into demand management. Do not bless it after go-live because it is already loved.

Scenario. Leadership calls the EHR upgrade “the portfolio.” It is one program at most. The portfolio is everything else you will stop or starve if the upgrade consumes the year.

Watch these traps:

1. Calling every request a project—or calling a program a single project so dependencies disappear.
2. Treating the PMO as the strategy or outcome owner.
3. Forty P1s and no displacement list.
4. Ignoring operations work that consumes the same scarce people.
5. Allowing departmental shadow projects to skip intake.
6. Declaring portfolio success when only Gantt bars are green.

/practice/cphimsPractice questions with detailed explanations