MT245 Project Fundamentals and Project Initiation sample papers, unit by unit

What MT245 is really about

This is the first project course and it covers the part students find least interesting and most decisive. Nothing is built here. The work is deciding what the project is, who wants it, what it will not include and who has authority to approve changes, and every one of those becomes expensive later if it was skipped. Assessments are built around documents rather than deliverables, and a charter that reads as description rather than agreement is the most common weak submission, because a charter is meant to be something the parties could argue about before signing. Nothing here is visible to anyone outside the project, which is exactly why it gets skipped and why it is graded.

Scope definition carries most of the marks and depends on writing exclusions rather than inclusions. What a project will do is usually easy to list; what it deliberately will not do is where later disputes originate, and stating those boundaries early is treated as competence. Stakeholder identification runs alongside and is often thin in student work: listing obvious parties is straightforward, while identifying the person who will object in month three because nobody consulted them is the actual skill. Where an assignment supplies a scenario, the criteria generally expect that person to be found. Sections vary in how formal the documents must be, but each is assessed on whether it would settle an argument rather than describe one.

What MT245’s assessments ask for

Early units generally establish what distinguishes a project from ongoing work and ask you to classify examples, which is less obvious than it sounds. The middle of the term usually produces initiation documents, a charter, a scope statement and a stakeholder register, each graded on its own. Several sections require a business case, asking why this project rather than another. Feasibility work appears in many units. Later assessments frequently ask you to defend an initiation package or to identify what an incomplete one would cost later. Board threads run every unit and commonly examine projects classmates watched go wrong from the start. Several sections additionally ask what an incomplete initiation would cost once the project is underway and the omission surfaces.

Where students lose points in MT245

The heaviest loss is a charter that describes rather than agrees, with no authority named and nothing anyone could dispute. Scope statements without exclusions cost similarly, since they defer every argument to a point where it is expensive. Stakeholder registers that list only the obvious parties give up ground too. Weaker papers also write a business case that never compares this project to an alternative use of the money, assume approval authority without saying whose it is, and describe feasibility as an opinion when the assignment supplied figures to test it against. A last loss comes from charters that name a sponsor without naming what that sponsor has actually committed, which leaves the authority unenforceable.

The MT245 drawers

Using a MT245 sample the right way

Read a charter sample and try to disagree with it. If there is nothing to push against, it is a description, and describing a project is not chartering one. Then look for the exclusions in the scope statement, which is where a strong document does its quiet work. Check the stakeholder register for the awkward name, the person with no formal role who can still stop things. Then draft your own from your unit's scenario. Pass over the scenario your section posted; the opening example is prepared at no charge and returns in a day or two.

How these samples are written

Every sample in this binder is written the way the custom ones are: the rubric decoded row by row, a subject-matched writer drafting to the top band, formatting checked line by line. Purdue Global revises courses; a custom request is always written to the rubric in YOUR classroom, never from a stale template.

MT245 questions, answered