Project and Program Management Fundamentals
A project is a temporary endeavor undertaken to create a unique product, service, or result; a program is a group of related projects managed in a coordinated way to obtain benefits not available from managing them individually. Candidates must distinguish projects from ongoing operations, programs from portfolios, and know the role boundaries among the project manager, program manager, portfolio manager, sponsor, and PMO. Understand the project life cycle versus the development life cycle, and how predictive, iterative, incremental, and agile approaches differ in when scope and cost are fixed.
Traps in questions: confusing a program (related projects, shared benefits) with a portfolio (a collection of projects/programs aligned to strategy, not necessarily related). Another trap is assuming the project manager owns benefits realization; benefits are typically realized after project closure and are owned by the sponsoring organization or program. Watch for questions that describe ongoing repetitive work and call it a project.
Rule of thumb: if the work is temporary and produces a unique output, it is a project; if it coordinates related projects for shared benefits, it is a program; if it is a strategic collection prioritized for investment, it is a portfolio.
Worked example: A firm runs three related projects to launch a new payment platform, coordinated by one manager who tracks combined benefits. That is a program, not a portfolio, because the projects are related and managed together for shared benefit.