1.3. Reflection Checkpoint

Key Takeaways

• A project is temporary and produces a unique result; operations are ongoing and produce repeatable output — the distinction is about the nature of the work, not its size or duration.
• Programs coordinate related projects to capture benefits unavailable if those projects were managed separately; portfolios group work strategically, regardless of whether that work is operationally related.
• The project life cycle (initiating → planning → executing → monitoring & controlling → closing) exists in both predictive and adaptive approaches — what differs is when detailed planning happens and how change is handled.
• Predictive approaches front-load planning and control change against a baseline; adaptive approaches plan iteration-by-iteration and treat change as expected input.
• A project's ultimate purpose is to serve as a vehicle for change — delivering a benefit the organization didn't have before, not just completing a deliverable.

Connecting Forward

Phase 2 goes deep on Domain 1 (36% of the exam) and puts these first-principles ideas to work: the full project life cycle in PMI's own process language, the planning documents that formalize the predictive/adaptive choice, project roles (and how leadership differs from management), and the everyday problem-solving tools associate-level team members are expected to recognize.

Self-Check Questions

• A department wants to launch a new internal expense-reporting process that will run indefinitely once live. Is building that new process a project, operations, or both — and at what point does it stop being one and become the other?
• A company is running three separate initiatives — a new website, a new CRM rollout, and a rebranding effort — and manages them together specifically because coordinating them reduces duplicate vendor contracts and aligns messaging. Is this most likely a program or a portfolio, and what evidence in the scenario tells you that?