PMGT1860 · Project Initiation and Scope
The Complete Study & Assessment Guide · S1 2027Project Initiation and Scope
PMGT1860 Project Initiation and Scope is a University of Sydney first-year unit in the Faculty of Engineering's School of Project Management, worth 6 credit points and delivered as blended weekly pre-work (readings plus short video lectures) followed by a two-hour in-person or Zoom workshop, for roughly 120–150 hours of effort across the semester. It teaches the front end of a project — the decisions made before anyone starts building — working from "what is a project?" and the triple constraint through project selection and feasibility, stakeholder engagement, writing a scope statement and Project Charter, building a Work Breakdown Structure, estimating schedule, budget and resources with quality, risk and procurement, and finally project value, success and the transition to operations. There is no final examination: the whole mark is coursework, and your grade rolls into your Weighted Average Mark (WAM). The components are a 25% individual thematic literature review (due around Week 7), a 20% weekly Learning Journal reflecting on Weeks 1–10 (due around Week 10), a 25% group Comprehensive Project Initiation Plan presentation and Q&A (Weeks 11–13), 25% short weekly in-class quizzes on the week's pre-work, and 5% workshop participation, with a formative 0% Early Feedback Task in Week 3. Because the marks are spread across the semester rather than sitting in one timed test, the unit rewards steady weekly work over any last-minute STUVAC cram. All weights and timings here mirror the published University of Sydney unit outline; confirm the current split and the exact due dates on Canvas for your session, as component details are periodically adjusted.
What PMGT1860 covers
PMGT1860 is a first-year, 6-credit-point unit that runs across the semester as weekly pre-work plus a two-hour workshop, building from "what is a project?" through feasibility, stakeholders, scope and the project charter, work breakdown structures, resourcing, project value and the transition to operations. There is no final examination: your Weighted Average Mark is assembled from a thematic literature review, a weekly learning journal, a group Comprehensive Project Initiation Plan presentation, weekly in-class quizzes and workshop participation. The chapters below follow the teaching order week by week and end with an assessment toolkit that maps each topic onto those tasks.
How PMGT1860 is assessed
| Component | Weight | Format |
|---|---|---|
| Individual Academic Writing — thematic literature review | 25% | Individual research analysis on a project-initiation topic, up to 15 pages incl. references; due ~Week 7 — confirm the exact due date on Canvas / the unit outline |
| Individual Reflection — Learning Journal | 20% | Weekly reflective journal for Weeks 1–10 on readings, class insights and application; ≤15 pages; due ~Week 10 — confirm the exact due date on Canvas / the unit outline |
| Group Presentation — Comprehensive Project Initiation Plan | 25% | Groups of 4–6; real-world or conceptual project; presentation + Q&A, 25 min per group; scheduled Weeks 11–13 |
| Small Quizzes (in-class) | 25% | Short weekly in-class quizzes (typically 5–8 min, 5 questions) on the week's pre-work and workshop; individual, one attempt |
| Workshop Participation | 5% | Ongoing; graded 0–5 across the semester for active workshop involvement |
| Early Feedback Task (formative) | 0% | Week 3 checkpoint — submit Weeks 1–3 journal entries; does not count toward the final grade |
Applied: should we green-light this proposal? A feasibility screen (payback · NPV · go/no-go)
- +1Payback period. Accumulate the net inflows until they recover the $120,000 outlay: end of Year 1 = $40k, Year 2 = $80k, Year 3 = $120k. The cumulative inflow reaches the initial cost exactly at the end of Year 3, so the payback period = 3 years. Payback is quick to read but ignores the time value of money and any cash beyond the payback window.
- +1Discount each inflow to present value at 10% using PV = Fₜ ÷ (1 + k)ᵗ. Year 1: 40 ÷ 1.10 = 36.36; Year 2: 40 ÷ 1.21 = 33.06; Year 3: 40 ÷ 1.331 = 30.05; Year 4: 40 ÷ 1.4641 = 27.32 (all in $000s).
- +1Sum the present values of the inflows: 36.36 + 33.06 + 30.05 + 27.32 ≈ $126.79k.
- +1NPV = present value of inflows − initial investment = 126.79 − 120.00 ≈ +$6.8k. Decision rule: NPV > 0 → the proposal is financially eligible for further consideration; NPV < 0 → reject. Here NPV is positive, so the project clears the financial screen (a marginal, but positive, result).
- +1Sense-check with a simple return figure: total net benefit over four years = $160k inflows − $120k cost = $40k, a total return on investment of 40 ÷ 120 ≈ 33% across the project's life. Positive, consistent with the positive NPV.
- +1State the limits: a positive NPV alone does not auto-select the project. Screening also needs strategic fit (does it align with organisational strategy and mission?) and risk (what are the major uncertainties?), plus non-financial value the numbers miss. Financial models can bias a portfolio toward easily-quantified projects, so the go/no-go call combines the number with strategy and risk.
Key terms
- Project
- A temporary endeavour undertaken to create a unique product, service or result (PMI classic); the PMBOK 8th edition frames it as a temporary initiative in a unique context undertaken to create value. 'Temporary' means a defined start and end, not necessarily short; 'unique' means the output has not been produced in exactly this form before. Contrast with ongoing operations.
- Triple constraint (iron triangle)
- The three interdependent limits every project balances — scope (what is delivered), time (the schedule) and cost (the budget) — with quality often shown as a fourth constraint or at the centre. Changing one usually forces a change in the others.
- Project scope
- The boundaries of a project — what is and is not included, its deliverables, and the assumptions and constraints around them. A usable scope statement carries the purpose, deliverables, in-scope and out-of-scope work, assumptions/constraints, and success criteria.
- Project Charter
- The document that formally authorises a project and grants the team the right to proceed to detailed planning. The sponsor owns it; the PM and team usually develop it. Its twelve components run from title and scope statement through business case, milestones, stakeholders, constraints, assumptions, risks, budget, success criteria and signatures.
- Work Breakdown Structure (WBS)
- A hierarchical decomposition of the total scope of work into progressively smaller, more manageable deliverables down to the work-package level (the lowest level at which cost, effort and duration can be estimated). It describes the 'what' — deliverables — not the schedule, and obeys the 100% rule: children sum to exactly 100% of their parent.
- Stakeholder
- Any individual, group or organisation that can affect, be affected by, or perceive itself to be affected by the project's decisions, activities or outcomes (positive or negative). Identifying and analysing stakeholders — often on a power/interest grid, captured in a Stakeholder Register — is a core initiation task.
PMGT1860 FAQ
Is PMGT1860 hard?
PMGT1860 is a first-year foundation unit, so the concepts themselves are accessible — it is more about understanding frameworks (the triple constraint, feasibility tools, stakeholder analysis, scope statements, the Project Charter, the WBS) and applying them than about heavy calculation. The one numeric thread is light feasibility screening (payback and NPV). The real challenge is that the mark is spread across the whole semester with no exam to save it: a 25% literature review, a 20% weekly learning journal, a 25% group presentation and 25% of weekly in-class quizzes. Students who keep up with the pre-work each week, start the journal early and contribute in workshops tend to find it very manageable; those who let the weekly quizzes and journal slide lose easy marks that cannot be recovered.
Can AI help me with PMGT1860?
Yes, as a study aid. Sia is an AI tutor trained on how PMGT1860 is taught and assessed at the University of Sydney: it can explain a framework like the triple constraint, a power/interest grid or the 100% rule for a WBS step by step, walk you through a feasibility screen on your own figures, and help you structure a thematic literature review or a reflective journal entry. It explains the method and checks your reasoning; it does not complete graded assessment for you, and the University of Sydney academic-integrity policy applies — generative AI may only be used where the coordinator explicitly allows it for a task, and any permitted use must be acknowledged.
How is PMGT1860 assessed?
Entirely by coursework — there is no final examination. The components are an individual thematic literature review (25%, due around Week 7), a weekly Learning Journal covering Weeks 1–10 (20%, due around Week 10), a group Comprehensive Project Initiation Plan presentation and Q&A (25%, in Weeks 11–13), short weekly in-class quizzes (25%, typically 5 questions in 5–8 minutes), and workshop participation (5%). There is also a formative Early Feedback Task in Week 3 worth 0%. Each mark rolls into your WAM. Confirm the current weights, page limits and exact due dates on Canvas and the unit outline for your session.
Does PMGT1860 have a hurdle task or attendance requirement?
None of the six components is marked as a hurdle in the assessment table, so treat the unit as having no hurdle — but the unit outline carries the University's generic clause that a unit 'may include' hurdle tasks, so confirm on the unit outline for your session. There is an attendance expectation: students are expected to attend a minimum of 85% of timetabled activities, and falling below that may risk a fail grade. Late work attracts a 5%-per-day penalty, reaching zero after 10 days, except where special consideration applies. Group work may use peer evaluation.
There's no exam — how should I spend my time?
Because the marks are spread weekly and there is no formal examination period to cram for, the winning strategy is consistency, not a final push. Do the pre-work before each workshop so the weekly quiz is easy marks, write a few honest journal lines every week (Weeks 1–10) so the 20% reflection has real material instead of a rushed reconstruction, and treat the group presentation as a genuine initiation plan — scope statement, stakeholder register, WBS, milestones. Start the literature review early and structure it by theme, not by author. Confirm every due date on Canvas rather than assuming last year's dates.
How to prepare for the assessments
Treat PMGT1860 as a toolkit to apply, not a set of readings to memorise, and remember the mark is earned week by week with no exam to fall back on. Each week, do the pre-work (readings plus the short videos) before the workshop so the weekly in-class quiz is easy marks, then take that week's framework and apply it to a real project you know — sort four factors into a SWOT, place three stakeholders on a power/interest grid, or write a two-line scope statement. Keep the Learning Journal from Week 1: a few honest, reflective lines each week on what a reading changed in your thinking feeds the 20% journal directly and saves you reconstructing ten weeks from memory. For the 25% thematic literature review, structure by theme (intro → themes → gap → future directions), not author by author, and support claims with the reading list. For the 25% group presentation, build a genuine initiation plan — business case, scope statement, stakeholder register, WBS and milestone schedule — and rehearse the 25-minute run and Q&A. Aim to attend at least 85% of workshops, contribute for the 5% participation mark, and confirm every weight, page limit and due date for your session on Canvas and the University of Sydney unit outline. When a framework won't click, ask Sia to re-explain that single model a different way and quiz you on applying it — it teaches the method and checks your reasoning, and never substitutes for your own graded work.
Your AI Project Management tutor for PMGT1860
Stuck on a hard PMGT1860 question? Sia is AskSia’s AI Project Management tutor — ask any PMGT1860 Project Initiation and Scope question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.
