The relationship between Proposal and Charter is best described as

• A. A Project Charter replaces the Project Proposal
• B. The Project Charter is independent of the Proposal
• C. The Project Proposal is derived from the Charter
• D. The Project Charter expands on the Proposal, adding formality and detail

Answer: (D)

The relationship being tested is how a project charter builds on the initial proposal. A project proposal lays out the business justification, high-level objectives, and a rough idea of scope and costs to justify moving forward. Once that proposal is approved, the Project Charter formalizes the authorization to proceed and adds more formality and detail. It specifies the project’s purpose, measurable objectives, high-level requirements, a high-level scope description, key deliverables, milestones, budget and funding, constraints, assumptions, and risks. It also defines roles and authority—who can commit resources and the project manager’s level of authority—setting the governance framework for planning and execution.

That’s why this option is the best: the Charter expands on the Proposal by providing the formal, detailed authorization needed to start the project and guide its governance. The other ideas don’t fit because the Charter isn’t a replacement for the Proposal, it isn’t independent of it, and the Proposal isn’t derived from the Charter.