INFO6007 Chap.14 Building the Project Management Plan
Building the Project Management Plan
This chapter assembles the assessed Project Management Plan as one professional management system. Charter, stakeholder evidence, literature, governance, scope, schedule, cost, resources, risk, quality, communication, change and monitoring must describe the same project. The rubric rewards detailed plan content and separately rewards integration, coherence, presentation and credible references.
Build in dependency order so scope drives the WBS, schedule, cost and resources, then use those baselines to make risk and quality specific. Communication and change should reference real stakeholders and authority, while monitoring compares actual performance with the measures already defined.
A coherence audit checks that every deliverable is scheduled, resourced and costed, every material risk has a response and every acceptance criterion has an owner. Stable terminology, reconciled totals, controlled versions and purposeful cross references make the logic inspectable. Professional presentation supports this evidence but cannot conceal contradictory plans.
What this chapter covers
- 01
Charter and stakeholder foundations
- 02
Literature and governance
- 03
Scope to schedule dependency
- 04
Cost and resource reconciliation
- 05
Risk and quality integration
- 06
Communication and change control
- 07
Monitoring, coherence and professional evidence
- 08
Reconcile objectives, deliverables, milestones, costs and acceptance structures before polishing individual subsidiary plans
- 09
State the owner, input, cadence, tolerance, decision and resulting record for every material control process
- 10
Cross-check that risk responses, procurement dates, resource capacity and quality evidence appear in connected baselines
- 11
Design communications around stakeholder decisions and information needs rather than producing a generic meeting calendar
- 12
Finish with transition criteria, operational ownership, document control and an auditable integrated-change route
- 13
Expose contradictory dates, totals, responsibilities and assumptions through a final cross-plan coherence review
Worked example · free
Repair a contradictory proposal
- +1Add missing deliverables to the WBS.
- +1Sequence migration, training and transition work.
- +1Estimate resources and costs.
- +1Fund adoption risk responses and quality tests.
- +1Reconcile ownership and monitoring across plans.
Key terms
- Subsidiary plan
- A specialised component governing one project management area within the integrated plan.
- Coherence
- Consistency of assumptions, boundaries, work, ownership, timing, costs and controls across the report.
- Monitoring framework
- The measures, reporting cycles, thresholds and corrective routes used to compare actual performance with baselines.
Building the Project Management Plan FAQ
What must the group project contain?
It compiles the charter, stakeholder plan, literature review, governance, scope, schedule, cost, resources, risk, quality, communication, change and monitoring and control sections into one proposal.
How do I demonstrate integration?
Ensure every deliverable is scheduled, every scheduled activity is resourced and costed, major risks have funded responses, acceptance tests have owners and changes update connected baselines.
How should the rubric guide writing?
Use descriptors as evidence checks for project specific analysis, ownership, criteria and links. Do not add generic paragraphs where the project logic supplies no real management need.
Exam move
Build the Project Management Plan in dependency order rather than dividing templates into isolated writing jobs. Establish the charter, stakeholder evidence and literature justification first. Define governance and scope before producing the WBS, schedule, cost and resource plans. Use those baselines to make risk and quality controls project specific.
Communication and change plans should reference real stakeholders, thresholds and decision authorities. Monitoring should compare actual performance with the same approved baselines and measures named elsewhere. Run a weekly integration audit.
Check that every deliverable appears in the schedule, every activity has realistic resources and cost, every material risk has an owner and funded response, and every acceptance criterion has evidence and authority. Reconcile terminology, dates, totals, role names, assumptions and exclusions. Trace literature insights into actual management choices rather than leaving the review as a disconnected essay.
Use cross-references where they help a reviewer test coherence without repeating whole sections. Apply the official rubric as an evidence checklist: comprehensive scope and WBS, realistic milestones and dependencies, justified estimates, allocated resources, rated risks and responses, QA and QC linked to deliverables, clear communication and escalation, a change workflow, monitoring measures and corrective action.
Do not invent generic detail merely to make a section longer. Before submission, assign an integration editor while keeping each section owner responsible for correcting contradictions. Inspect figures and tables for readability and purpose, verify references support the choices made and confirm that optional material is not presented as assessed work.
On the notes sheet, keep a final audit chain: deliverable, schedule, resource, cost, risk, quality, authority and monitor. The strongest final edit usually removes a contradiction, because professional presentation cannot rescue a plan whose components describe different projects.
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.