INFO6007 Chap.14 Building the Project Management Plan
Building the Project Management Plan
The group task produces one consolidated Project Management Plan. Its 70-mark rubric allocates 60 to the report and 10 to contribution; the five core planning criteria carry 35. This chapter develops Thirteen plan sections, Foundations 11, Core Planning 35, Support Plans 8, Professionalism 6, Teamwork 10, Thirty-percent report, Five-percent peer evaluation, Harvard referencing, Optional appendix.
Each idea is framed as a management decision: what evidence is needed, who owns the decision, which baseline or service outcome changes, and how the result is communicated.
Make every section tell one project story. Trace assumptions and dependencies so scope, schedule, cost, resources, risk, quality, communication, change and monitoring agree. The method is deliberately connective.
Scope choices affect dependencies and estimates; resource choices affect schedule and cost; governance choices affect escalation and benefit ownership; service choices affect operating value. A strong answer names those links rather than reproducing an isolated framework.
Do not invent rubric bands, treat the optional technical appendix as extra marks, or overlook the 30% report plus 5% SparkPlus split.
The chapter uses direction checks, boundary cases and original scenarios to make those errors visible. Where a supplied figure is reproduced third-party material, the guide rebuilds it on new dimensions.
Where an answer is independently computed from a published table, it is labelled AskSia-authored rather than attributed to the University.
For assessment, start with a one-sentence definition, apply it to the stated facts, explain the consequence for objectives or constraints, and finish with the controlled action. Quantitative work must show the formula, substituted values, result, direction and management meaning.
Qualitative work must identify the decision owner and the evidence that would change the recommendation.
Study this chapter through retrieval. Rebuild the central artefact from a blank page, test it against a changed assumption, then check it against one neighbouring plan or practice.
That routine prepares for explanations, comparisons, scenarios and calculations without inventing a past-paper format or per-question mark scheme.
What this chapter covers
- 01
Thirteen plan sections
- 02
Foundations 11
- 03
Core Planning 35
- 04
Support Plans 8
- 05
Professionalism 6
- 06
Teamwork 10
- 07
Thirty-percent report
- 08
Five-percent peer evaluation
- 09
Harvard referencing
- 10
Optional appendix
Free worked application: Building the Project Management Plan
- FrameIdentify the objective, decision owner and evidence available at the decision point.
- MethodApply the chapter rule and keep assumptions, units and direction words explicit.
- IntegrateTrace effects into at least one connected plan, baseline, stakeholder or service outcome.
- ActState the recommendation and the change, control or communication action that follows.
- VerifyCheck the result against the chapter trap and explain why the conclusion is reproducible.
Key terms
- Thirteen plan sections
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Foundations 11
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Core Planning 35
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Support Plans 8
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
- Professionalism 6
- A chapter concept used to make the relevant scope, flow, responsibility, measure or outcome explicit. Interpret it in the scenario rather than from its label alone.
- Teamwork 10
- A chapter concept used to connect evidence to a controlled project or service decision. Interpret it in the scenario rather than from its label alone.
Building the Project Management Plan FAQ
How are the 70 rubric marks distributed?
Foundations 11, Core Planning 35, Support Plans 8, Professionalism 6 and Teamwork 10. These sum to 70; the displaced Support Plans heading is restored to its four two-mark criteria.
What is the main decision rule for Building the Project Management Plan?
Make every section tell one project story. Trace assumptions and dependencies so scope, schedule, cost, resources, risk, quality, communication, change and monitoring agree.
What is the most common trap in Building the Project Management Plan?
Do not invent rubric bands, treat the optional technical appendix as extra marks, or overlook the 30% report plus 5% SparkPlus split.
How should I structure a written answer on Building the Project Management Plan?
Define the concept, apply it to specific facts, explain the effect on an objective or constraint, identify the decision owner, and state the next controlled action.
Are the worked scenarios for Building the Project Management Plan official answers?
No. They are AskSia-authored learning examples derived independently from the concepts and stated inputs. They are not official questions, marking schemes or university solutions.
Exam move
Begin with the chapter map: Thirteen plan sections, Foundations 11, Core Planning 35, Support Plans 8, Professionalism 6, Teamwork 10, Thirty-percent report, Five-percent peer evaluation, Harvard referencing, Optional appendix. Write the purpose of each item in your own words and connect it to a decision, an artefact and an owner. Then rebuild the worked application without looking at the answer.
Use this governing rule: Make every section tell one project story. Trace assumptions and dependencies so scope, schedule, cost, resources, risk, quality, communication, change and monitoring agree. Create two variations by changing one assumption, dependency, rating, probability, duration or stakeholder priority. Explain what changes and what remains stable.
Keep an error ledger headed direction, boundary, authority, precision and integration. The chapter's highest-risk mistake is: Do not invent rubric bands, treat the optional technical appendix as extra marks, or overlook the 30% report plus 5% SparkPlus split.
For quantitative work, write symbols and units before arithmetic, keep intermediate precision visible and translate the result into under/over, ahead/behind, faster/cheaper or selected/not selected as appropriate. For qualitative work, write claim, scenario evidence, causal reasoning and controlled action. Finish by checking one neighbouring plan or practice.
Review operational assessment details on Canvas; this learning chapter does not invent dates, a viva rubric, past-paper questions or a per-question university mark scheme.
Working through Building the Project Management Plan in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Building the Project Management Plan question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
