Every project needs formal mechanisms to start, to change, and to end. The project charter is the document that formally authorizes a project. It names the project manager, defines high-level objectives and scope, identifies key stakeholders, and clarifies the manager's authority level, and it is typically issued by the sponsor. With the charter in hand, the project begins. As work unfolds, scope creep, the uncontrolled expansion of project scope without corresponding adjustments in time, cost, or resources, becomes one of the most common threats. To guard against it, organizations use a formal change control process in which proposed changes to baselines for scope, schedule, or cost are reviewed, evaluated, approved, or rejected, often by a group called the Change Control Board.
Procurement Management handles the acquisition of products, services, or results from outside the organization and covers planning procurements, conducting them, controlling them, and closing them. A key early decision is whether to make or buy, after which the contract type sets the financial arrangement. Common contract types include Fixed-Price agreements, which suit well-defined scopes because the seller bears much of the cost risk; Time and Materials contracts, which charge for labor hours plus materials and are useful when scope is unclear; and Cost-Reimbursable contracts, which reimburse the seller's costs and are appropriate for uncertain or evolving scopes. Beyond PMBOK, some organizations adopt structured methodologies such as PRINCE2, or Projects IN Controlled Environments, a process-based approach built on seven principles, themes, and processes that emphasizes defined roles, staged progress, and continuous business justification.
Closure is more than marking a task complete. The Closing process group finalizes all activities, obtains stakeholder acceptance of the deliverables, releases project resources, archives documents, and, importantly, captures lessons learned. Lessons learned are the documented experiences and insights gained during the project, both positive and negative, recorded throughout the effort and consolidated at closure. They feed into organizational knowledge so that future projects can repeat what worked and avoid what did not. In this way, even a project that ends poorly can leave behind knowledge that improves the next one, closing the loop between execution and learning.