PMGT1860 Project Initiation and Scope
The Complete Study & Assessment Guide · S1 2027PMGT1860 Overview
- University of Sydney
- S1 2027
- 11 chapters
- Project Management
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.
- Assessed by Individual Academic Writing — thematic literature review 25% · Individual Reflection — Learning Journal 20% + 4 more
- Key terms Project, Triple constraint (iron triangle), Project scope, Project Charter
- Assessment move 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.
- Most asked Does PMGT1860 have a hurdle task or attendance requirement?
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 |
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.
What Is a Project? Foundations & the Iron Triangle
project vs operations · PMI/PMBOK 8th definitions · triple constraint · life cycle · (Week 1)Week 1 sets the vocabulary the whole unit and every assessment rests on: a project as a temporary, unique, value-creating endeavour versus ongoing operations, the triple constraint (iron triangle) and broader success criteria, and the project life cycle from initiation to closure.
- Project defined — PMI classic (temporary, unique, product/service/result) and PMBOK 8th (temporary initiative in a unique context to create value)
- 'Temporary' = defined start and end (not short); 'unique' = not produced in exactly this form before
- Characteristics of a project: specific objectives/deliverables, start and end, allocated resources, uniqueness, uncertainty, tracked tasks, distinct stakeholders
- Projects vs operations (repetitive, ongoing, routine work)
- The triple constraint / iron triangle — scope, time, cost, with quality as a fourth/central constraint
- Success criteria beyond the triangle — quality, user/client/team satisfaction, innovation, sustainability
Project Selection & Feasibility Evaluation
org strategy · business case · project as investment · SWOT/PESTLE · (Week 2)Week 2 shows how projects are chosen before a project manager is even hired: the organisation's strategy and mission motivate the project, a business case justifies the investment, and feasibility weighs benefits against costs across technical, operational, financial and market lenses.
- Why organisations select and evaluate projects — limited resources, prioritise value, catch doomed proposals early
- Project as an investment; the strategic chain Mission → Goals → Objectives → Strategies → Implementation (Gray & Larson Ch 2); portfolio types (compliance, operational, strategic)
- Feasibility dimensions — technical, operational, financial, market (also schedule and legal/regulatory)
- SWOT — Strengths/Weaknesses (internal) over Opportunities/Threats (external)
- PESTLE macro-environment scan — Political, Economic, Social, Technological, Legal, Environmental
- Financial screens — payback period and NPV (accept if NPV > 0); limitations of purely financial models
Organising Projects Within the Enterprise
organisational structures · strategy-to-project alignment · (Week 3)Week 3 explains how projects sit inside the parent organisation and how organisational structure shapes authority, resourcing and a project manager's real power.
- Projects cut horizontally across the organisation, drawing on different functions (R&D, Purchasing, Marketing, HR, Accounting, ICT)
- Cross-cutting work as a source of inter-departmental and inter-group conflict (Robbers Cave experiment)
- Functional organisation — project stays inside one function, reports to the functional manager, often no dedicated PM
- Dedicated / projectised team — resources extracted and co-located, strong PM authority, reintegration risk
- Matrix organisation — resources shared, PM and functional manager share authority, two-boss tension
- Matrix sub-types — weak/functional, balanced, strong/project matrix
Stakeholder Engagement & the Stakeholder Register
identification · power/influence–impact analysis · stakeholder register · (Week 4)Week 4 teaches who a project's stakeholders are and why managing them is a core initiation task, building analysis on a power/interest grid and the three-attribute salience model, then translating it into a Stakeholder Register.
- Stakeholder defined — anyone who can affect, be affected by, or perceive itself affected by the project (positive or negative)
- The stakeholder-management roadmap — identify → analyse → plan (current→desired) → engage
- Internal (sponsor, PM, team, PMO, resource managers) vs external (customers, users, suppliers, regulators, community, government) stakeholders
- Shadow stakeholders — unrecognised influencers with no official title who can still affect the outcome
- The Stakeholder Register — a lightweight record of role, power, interest, needs, risks and preferred channel
- Power–Interest grid — Manage Closely / Keep Satisfied / Keep Informed / Monitor
Managing Scope & the Project Charter
scope statement · scope creep & change control · 12 charter components · milestone schedule · (Week 5)Week 5 is the heart of the unit: writing a usable scope statement, recognising and controlling scope creep, and assembling the Project Charter — the document that formally authorises a project — with its twelve components and a milestone schedule carrying acceptance criteria.
- Project scope — the boundaries: deliverables, size, timing and cost (what is and is not included)
- The six-element scope statement — purpose/problem, deliverables, in-scope, out-of-scope, assumptions & constraints, success criteria
- Scope creep — uncontrolled growth without adjusting time, budget or resources (~52% of projects, PMI 2023)
- Protecting scope — get it in writing, formal change control (document → evaluate → approve/reject), milestone reviews, sign-off
- Change Control Board (CCB) and the change request as the way to say 'no' safely
- Project Charter — the deliverable that formally authorises the project and grants the right to detailed planning
Work & Organisational Breakdown Structures
WBS purpose · decomposition to work packages · OBS · (Week 6)Week 6 teaches the Work Breakdown Structure — the tool that organises and defines the total scope and becomes the basis for planning, budgeting and resourcing — decomposed down to work packages, plus the Organisational Breakdown Structure that assigns responsibility.
- In-scope vs out-of-scope activities as the project boundary
- WBS defined (PMBOK) — a hierarchical decomposition of the total scope of work into deliverables
- Role of the WBS — visualises scope, verifies completeness, is the scope baseline for change control; describes the 'what' (deliverables), NOT the schedule/timing or reporting lines
- Decomposition and the work package — the lowest level at which cost, effort, duration and resources can be estimated
- The four WBS levels — Top Level → Control Account → Work Packages → Activities
- Representations — indented outline, tree/org-chart, Gantt; organising schemes — deliverable-based vs phase-based
Schedule, Budget, Resources, Quality, Risk & Procurement
estimation methods · quality · risk · procurement · RACI · (Week 7)Week 7 covers establishing the project's resources: estimating time, cost and resources and the methods of estimation, plus first principles of quality, risk and procurement management, and the RACI matrix for clarifying responsibility.
- Estimate defined (PMBOK) — a quantitative assessment of likely cost, resources, effort or duration; duration vs effort
- Methods of estimation — analogous (top-down), parametric (unit rate), bottom-up (roll up work packages), three-point (PERT), Wideband Delphi
- Quality in projects — plan quality → manage/assure quality → control quality; conformance, verification vs validation
- Risk defined — an uncertain event with a positive (opportunity) or negative (threat) effect on objectives
- Risk process — identify → analyse (probability × impact; Expected Monetary Value) → plan responses → monitor
- Threat responses (avoid, mitigate, transfer, escalate, accept) and opportunity responses (exploit, enhance, share, escalate, accept)
Project Value & Success
value beyond the iron triangle · plural perspectives · Opera House case · (Week 8)Week 8 broadens success beyond on-time/on-budget to value across financial, strategic, social and environmental dimensions and plural stakeholder perspectives, using the Sydney Opera House case to argue that the real question is whether a project created value and for whom.
- Value defined — the worth, importance or usefulness of something to someone; project value = benefits and impact to stakeholders
- Project success — the degree to which a project meets objectives and delivers expected value (a consensus view across stakeholders)
- Four dimensions of project value — financial, strategic, social, environmental
- Success is more than the iron triangle — time/cost/scope/quality plus sustainability and social impact
- Value through plural perspectives (Clegg) — profit, people, planet
- The Sydney Opera House case — ~10 years late, ~1,357% over budget in real terms, yet >A$1.2 billion annually
Operations-Oriented Project Initiation
designing the transition to operations · strategy/structure/process/people · (Week 9)Week 9 looks past handover: how large inter-organisational projects should be initiated with the eventual transition to operations already in mind — across strategy, structure, process and people (Zhang et al. 2024).
- Core question — traditional initiation asks 'can we deliver this?'; operations-oriented asks 'will it work in real life?'
- Projects (unique, temporary) vs operations (repetitive, ongoing); project vs operations management
- Delivery success vs operational success — completed on time/budget/scope vs useful, adopted, benefits realised
- Why delivered projects still fail after handover — wrong requirements, poor adoption, high operating cost, weak handover, limited benefits
- What operations-oriented initiation embeds — operational needs, user requirements, maintenance, transition planning, benefits realisation
- Translating operational questions into initiation decisions
Best Practices & New Considerations in Initiation
hybrid/Agile · AI · sustainability · emerging frontiers · (Week 10)Week 10 is the capstone content week, surveying contemporary and forward-looking considerations in project initiation — the evolution toward Agile and hybrid methods, the strategic role of the PMO, AI-enabled and ethically-framed projects, sustainability, and sector-specific early risks.
- Business need and justification — why the project should exist (problem/opportunity, strategic alignment, feasibility, priority, cost of not doing it)
- The initial Stakeholder Register as the key early output of stakeholder analysis (not a budget/closure report or WBS)
- The Project Charter recap — formally authorises the project and defines objectives, high-level scope, assumptions, constraints
- Predictive vs adaptive (Agile) vs hybrid approaches
- The strategic role of the PMO (Project Management Office)
- Sector-specific early considerations — construction/infrastructure (whole-life, maintainability, disruption) vs manufacturing (supply-chain resilience, geopolitics, reputation)
Assessment Success Toolkit: Literature Review, Journal & Group Presentation
thematic lit review 25% · learning journal 20% · group presentation 25% · quizzes 25% · (Weeks 7–13)This closing chapter pulls the whole unit into its assessments: how to structure the 25% thematic literature review by theme, how to keep a reflective weekly Learning Journal that earns the 20%, and how to plan and deliver the 25% group Comprehensive Project Initiation Plan presentation and Q&A, plus how the weekly in-class quizzes and workshop participation are earned.
- The assessment mix — literature review 25%, learning journal 20%, group presentation 25%, weekly quizzes 25%, participation 5% (Early Feedback Task 0%)
- Thematic literature review — organise by theme (intro → themes → gap → future directions), not author by author
- Learning Journal — weekly reflection on readings, class insights and application across Weeks 1–10
- Group Comprehensive Project Initiation Plan — business case, scope statement, stakeholder register, WBS, milestones
- Presentation and Q&A — 25 minutes per group of 4–6; run sheet and rehearsal
- Weekly in-class quizzes — short concept checks on the week's pre-work; individual, one attempt
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.
Worked example · free
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.
Questions students ask in each PMGT1860 chapter
- What is the difference between a project and operations?
- A project is temporary and unique — it has a defined start and end and produces something not made in exactly this form before, then it finishes. Operations are repetitive, ongoing and routine, with no end date. Migrating to a new system is a project; running that system month after month is operations. This distinction returns in Week 9 when the unit looks at the transition from project delivery to operations. Chapter 01 · What Is a Project? Foundations & the Iron Triangle
- Why do organisations bother selecting and evaluating projects at all?
- Because resources are limited, so an organisation must prioritise the proposals that create the most value rather than run every idea, and feasibility evaluation is an early check to confirm a proposal is viable before major resources are committed — catching a doomed project before it starts. Not every approved idea becomes a project; selection chooses among competing options. Chapter 02 · Project Selection & Feasibility Evaluation
- Why does organisational structure matter for a project manager?
- Because structure decides where the resources sit and how much authority the project manager actually has. In a functional structure the work stays inside one department and there may be no dedicated PM; in a dedicated team the PM has strong command; in a matrix the PM shares authority with functional managers and has to influence rather than direct. The same project can be easy or hard to run depending on which structure it lives in. Chapter 03 · Organising Projects Within the Enterprise
- Who counts as a stakeholder — just the client and the team?
- No. A stakeholder is anyone who can affect, be affected by, or even perceive themselves affected by the project — internal (sponsor, PM, team, PMO, resource managers) and external (customers, end users, suppliers, regulators, community, competitors, government). It deliberately includes people who are not paying for or building the project, because they can still support, block or reshape it. Chapter 04 · Stakeholder Engagement & the Stakeholder Register
- What exactly does a scope statement need to contain?
- Six things: the project purpose or problem, the major deliverables, the in-scope work, the out-of-scope items, the key assumptions and constraints, and the success or acceptance criteria. Naming what is out of scope is as important as what is in — it draws the boundary that protects the project from scope creep later. Chapter 05 · Managing Scope & the Project Charter
- What is the difference between the WBS and a schedule?
- The WBS describes the 'what' — the deliverables and work, decomposed into a hierarchy — while the schedule describes the 'when'. The WBS deliberately ignores chronology and reporting lines; sequencing tasks in time is the schedule's job. A common quiz error is to describe a WBS as 'tasks in the order they happen', which is wrong. Chapter 06 · Work & Organisational Breakdown Structures
- Which estimation method should I use — and which is most accurate?
- It depends on how much detail you have. Analogous (top-down) estimating is fast and useful early when little is known, but least accurate; parametric uses a unit rate; bottom-up estimates each work package and rolls them up for the most accurate figure with the most effort; three-point (PERT) blends optimistic, most-likely and pessimistic estimates. Once your WBS has defined work packages, bottom-up is the accurate choice. Chapter 07 · Schedule, Budget, Resources, Quality, Risk & Procurement
- Isn't a project a success if it's delivered on time and on budget?
- That is necessary but not sufficient. Delivering on time, on budget and to scope is delivery success, but a project can hit all three and still fail to create value if no one adopts it or the benefits never materialise. This week reframes success around value — financial, strategic, social and environmental — and asks not just 'did we deliver to plan?' but 'did we create value, and for whom?' Chapter 08 · Project Value & Success
- Can a project be a success if it's delivered on time and budget but nobody uses it?
- By delivery metrics yes, but by operational and whole-life measures no. Operations-oriented initiation argues that many 'delivery successes' are actually initiation failures, because the future operation was never properly understood at the start. A system delivered to spec but ignored by users, expensive to run, and delivering no benefits has failed where it counts — in use, not in handover. Chapter 09 · Operations-Oriented Project Initiation
- What does 'business need and justification' actually mean at initiation?
- It means being able to answer why the project should exist — the problem or opportunity it addresses, how it aligns with strategy, whether it is feasible and a priority, and what happens if it is not done. It is deliberately not about operational logistics like how big the team is, how often it meets or which software it uses; those are downstream. The defining question is 'why is this project needed?' Chapter 10 · Best Practices & New Considerations in Initiation
- How should I structure the thematic literature review?
- By theme, not by author. Open with an introduction that frames your project-initiation topic, then organise the body into thematic sections that group what different authors say about each theme, synthesising and comparing rather than summarising one source at a time. Identify the gap in the literature, and close on future directions. Support every claim with the reading list. An author-by-author 'A says, B says' structure is the classic weak submission because it lists instead of analysing. Chapter 11 · Assessment Success Toolkit: Literature Review, Journal & Group Presentation
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.
