MGT-440 · Topic 2

MGT-440 Topic 2 project charter example

Project Management Grand Canyon University Free custom sample in 24 to 48h

This page holds a complete MGT-440 Topic 2 project charter example, shown finished. The charter authorizes the relocation of a credit union's call center, names the project manager and the exact decisions that person may make without asking, records what the functional managers have committed, and marks the lease expiry as the constraint that cannot move. Early topics in MGT 440 often treat the charter as a grant of authority.

What this page holds

A finished MGT-440 Topic 2 project charter example, authorizing one relocation project and stating precisely what the project manager may decide, spend and assign. Searches like "mgt 440 topic 2 assignment example", "mgt440 topic 2 sample" and "mgt-440 topic 2 example" land here.

What a finished MGT-440 Topic 2 project charter looks like

The finished charter is two pages a sponsor signs, not a project plan in disguise. It opens with the reason for the project in one paragraph and three measurable objectives, including the call center taking member calls from the new floor with no more than one day of reduced service. The project manager is named, and the authority is written as specific permissions: approving purchases up to 10,000 dollars per item, assigning tasks to the facilities and IT staff committed to the project, and escalating conflicts to the sponsor within two business days. The functional managers' commitments are recorded by name and hours. The lease expiry is marked as the fixed constraint. All figures are labeled illustrative, and the budget of 180,000 dollars sits beside a sponsor-held reserve of 18,000.

How an MGT-440 Topic 2 example is structured

The charter is arranged in the order a sponsor reads before signing. The business reason and the objectives lead, each written so that someone could later say whether it was met. A second part gives high-level scope with an explicit list of exclusions, such as new furniture for departments that are not moving. A third part names the sponsor and the project manager and sets out the manager's authority as numbered permissions rather than general responsibility. A fourth part records the staff lent by functional managers, with names, hours and the period covered, since in a matrix organization those people still report elsewhere. A fifth part states the summary budget, the reserve and who controls it, followed by the milestones. A sixth part identifies the fixed constraint and what flexes around it. Signature lines for the sponsor and both lending managers close the document.

Objectives someone could later check

Each objective states a result and a measure, such as calls answered from the new floor with no more than one day of reduced service.

Authority written as numbered permissions

The project manager may approve purchases up to a labeled limit, assign committed staff and escalate conflicts, which is far clearer than being held responsible.

Borrowed staff recorded by name

Facilities and IT managers commit named people for stated hours, because in a matrix organization those people keep reporting to their own managers throughout.

Reserve held above the manager

The 18,000 dollar reserve stays with the sponsor, so the charter shows exactly where spending decisions pass from the project manager upward.

The lease date marked fixed

Time is named as the constraint that cannot move, which tells everyone in advance that scope or cost gives way once the schedule comes under pressure.

Signatures from every lending manager

The sponsor signs and so do the two managers lending staff, since a commitment made aloud in a meeting tends to fade by the second month.

Where marks go in MGT-440 Topic 2

Authority is where most charter marks are decided. A document naming a project manager and describing that person as responsible for success has handed over responsibility without power, and the topic asks precisely what the role can decide. Objectives written as goals, such as a smooth transition, cannot be checked at closure and invite argument about whether the project succeeded. Charters listing no exclusions leave scope open to every department that hopes to benefit. Staff commitments missing from the document mean the functional managers keep full control of the people the project depends on. Budgets without a stated reserve or its owner blur the point at which spending needs approval. A charter that runs to a full schedule and task list has turned into a plan and lost the purpose of being signed quickly.

Get an MGT-440 Topic 2 example written to your instructions

Send the MGT-440 Topic 2 instructions, your section's rubric and the project or case the charter is for. We write a custom example to those criteria, with checkable objectives, exclusions listed, authority set out as permissions, borrowed staff recorded and the fixed constraint named, in 24 to 48 hours. The first one costs nothing, and all figures come labeled illustrative.

MGT-440 Topic 2 questions, answered

Who writes and signs a project charter?

The project manager often drafts it, but the sponsor issues and signs it, because the charter is the organization granting authority and resources to the project. Where staff are lent from other departments, their managers signing as well turns a verbal promise into a recorded commitment. A charter signed only by the person it empowers has authorized nothing at all.

How is a charter different from a project plan?

The charter authorizes the project and sets its boundaries, objectives, authority and summary budget, and it is meant to be short enough to sign quickly. The plan comes afterward and holds the detail: the work breakdown, the schedule, the risk register and the cost baseline. Packing a full schedule into the charter usually delays the signature it exists to obtain.

What authority does a project manager usually have?

It depends on how the organization is structured. In a strong matrix the project manager controls the budget and directs assigned staff; in a weak matrix the role coordinates while functional managers keep the real decisions. The charter should state which applies, in specific permissions, so nobody discovers the limits halfway through the work.