FIT5057: ace the project, not just read the notes
Your complete guide to Monash University's project management unit. See where the marks are, work real practice questions, and study with an AI tutor that knows FIT5057.
Sia generates FIT5057 practice questions, walks through organisational context and project planning: scope statement step by step, and quizzes you on the material the project that weights most heavily.
Study FIT5057 with Sia
A new IT project has a budget at completion (BAC) of $500,000. At the Month 3 status review, the planned value (PV) is $200,000, the earned value (EV) is $180,000, and the actual cost (AC) is $210,000. Using cost variance CV = EV − AC and schedule variance SV = EV − PV, is this project over or under budget, and ahead of or behind schedule? Paste this into Sia to work the full earned-value cluster (CV, SV, CPI, SPI, then EAC = BAC / CPI) step by step.
One project decides 40% of your grade. Project deliverable; no bring-in restriction (it is take-home applied work). This whole page is built around that.
Overview
What FIT5057 is, and where it sits
FIT5057 Project Management is a 6-credit-point postgraduate unit in Monash University's Faculty of Information Technology, taken in the Master of IT and related coursework programs. It builds one end-to-end project-management toolkit and applies it to information-technology projects: the project versus operations distinction and the iron triangle, PMBOK 7 principles and performance domains, the business case and project charter, scope and the work breakdown structure, schedule and cost (critical path, PERT, Gantt and earned value), risk and governance, quality and stakeholders, and then the full agile half (the Agile Manifesto, Scrum, Kanban, and scaled and hybrid delivery).
The unit is built around two ways of running a project and the judgement to choose between them. The first half is predictive (PMBOK-based) planning across Weeks 1 to 7: a business case becomes a charter, the charter becomes scope and a WBS, and the WBS feeds a schedule, a cost baseline and a risk register. The second half is adaptive across Weeks 8 to 12: the Agile Manifesto and 12 principles, Scrum roles, events and artifacts, personas and user stories, sprint planning and execution, and advanced and scaled practices, closing on hybrid models and tailoring. Lecturers explicitly contrast PMBOK 7 (the why: principles and performance domains) with PMBOK 6 (the how: process groups and knowledge-area tools) and ask students to use both.
There is no traditional written final exam. The grade is two project assignments worth 40% each plus a 20% invigilated quiz sat under Safe Exam Browser, so most of the work is applied project deliverables rather than memorised theory. The hard part is breadth and judgement: you must carry a predictive plan from business case to earned-value control, then run an agile pilot feature through personas, a prioritised backlog and four sprints to a working Scrum-board demo, and defend the tailoring choices behind both. Group work with peer evaluation and a running case study (a Monash student-services style web app) keep the load continuous across the term.
Official outline: handbook.monash.edu · FIT5057 outline. Always treat the official outline and the exam timetable as authoritative.
Difficulty & time commitment
Is FIT5057 hard, and how much time does it take?
FIT5057 is manageable if you keep a weekly rhythm and treat the back half as the main event. Across student reviews the pattern is consistent: it starts gently and steepens, and the heaviest assessment is the part that separates grades.
A read across student reviews and course feedback. See what students say ↓
The difficulty curve and the assessment weighting point the same way: the back half is harder and worth more. Front-loading effort there is the highest-return decision in the unit.
Is this unit for you
Who tends to do well, and who tends to struggle
You will likely do well if
- You stay on top of continuous applied work. With two 40% projects and no single exam to cram for, falling behind on the predictive plan or the sprint deliverables compounds across the term.
- You can choose and defend a framework, not just describe it. Both projects and the HD reward correct tailoring (predictive versus agile, PMBOK 7 principles versus PMBOK 6 tools) with a clear justification.
- You are a reliable, contributing team member, since the group components carry peer evaluation and Assignment 2 culminates in a live Scrum-board demonstration and interview.
- You practise the manual procedures by hand (critical path forward and backward pass and float, PERT, the EVM family) until they are automatic, so the workshop computations and the quiz concept items are quick.
You may struggle if
- You memorise definitions but cannot apply them. The quiz tests recognition under time pressure and the projects test judgement, so rote theory without application underperforms.
- You treat the predictive and agile halves as separate units. The unit is built on contrasting and tailoring between them (Gantt versus sprint board, earned value versus burndown, lessons learned versus retrospective), and that contrast is itself examinable.
- You confuse the closely related artefacts: scope statement versus WBS versus charter, risk versus issue versus assumption, contingency reserve versus management reserve, Definition of Ready versus Definition of Done. These distinctions are favourite quiz traps.
- You disengage in group work, because peer evaluation can scale non-contributors down and the agile demo exposes who built what.
- Build one running cheat-sheet of the manual procedures (CPM passes and float, PERT, the full EVM cluster with sign conventions, risk score and EMV, velocity forecast) and rehearse each from a blank dataset.
- Drill the predictive-to-agile contrast as a single map: charter and WBS and Gantt and earned value on one side, personas and backlog and sprints and burndown on the other, with tailoring (Stacey, hybrid) as the bridge.
- Make the traceability spine of Assignment 2 immaculate (persona to requirement to epic to user story to priority to sprint to story points). It is the skeleton markers check first.
- Practise the recognition-level quiz items (which dependency type, what a negative cost variance means, a milestone's zero duration, leading versus lagging indicator, DoR versus DoD) until they are instant, since the quiz is short and time-pressured.
Syllabus
The 12 topics, week by week
The exam-weight marker on each topic shows where the marks concentrate. The amber topics carry the highest exam weight.
W1 · Introduction to Project Management
Project versus operations, the iron triangle (scope, time, cost bounded by quality), project versus program versus portfolio, strategic alignment, and the project charter introduced. PM skills and methodology overview (PMBOK, Agile, PRINCE2).
W2 · Organisational context, PMBOK 7 principles and performance domains
Organisational structures (functional to projectised), the Value Delivery System, the 12 PMBOK 7 principles and 8 performance domains, PMBOK 6 versus 7 (process groups and 10 knowledge areas), development approaches (predictive, iterative, incremental, adaptive, hybrid), the business case and the project charter, and NPV as financial justification.
W3 · Planning and delivery domains
Scope planning (in scope versus out of scope, constraints, assumptions), collecting requirements, the Requirements Traceability Matrix, scope creep, the work breakdown structure and the 100% rule, the three dimensions of quality, and the team working agreement.
W4 · Project planning: scope statement, WBS and quality
The project scope statement (justification, product requirements, deliverables, success criteria), developing and critiquing a WBS, and quality management fundamentals (planning, assurance, control) with the PMBOK quality tools (Pareto, control charts, fishbone, cost of quality). Own-time ethics mini-lecture.
W5 · From scope to schedule and cost to integrated project control
Sequencing (PDM dependency types FS, SS, FF, SF; leads and lags), duration estimation (analogous, parametric, bottom-up, three-point PERT), the critical path (forward and backward pass, total and free float), the Gantt chart, cost classifications and reserves, estimate types (ROM, budgetary, definitive), and earned value management (PV, EV, AC, CV, SV, CPI, SPI, EAC).
W6 · Governance in practice: risk, measurement and integration
The risk management process, the probability times impact matrix and risk score, Expected Monetary Value, threat and opportunity response strategies, the measurement domain (KPIs, SMART, RAG, leading versus lagging), and integration management (change control, configuration management, lessons learned).
W7 · Quality management, stakeholder engagement and integration
Quality revisited (three dimensions, three phases, measurable standards such as uptime and WCAG 2.1 AA), stakeholder engagement (the Power/Interest grid, the salience model, the stakeholder register and engagement levels), communication planning (interactive, push, pull), and project integration across the plan.
W8 · Agile project management (the bridge)
Why adaptive (predictive strengths and weaknesses), tailoring predictive to adaptive, the Agile Manifesto (4 values, 12 principles), the Stacey diagram for lifecycle selection, the agile frameworks landscape (Scrum, Kanban, Lean, XP, SAFe), and Scrum foundations (empiricism, the 3 pillars, 5 values, roles).
W9 · Agile execution: personas to sprint
Personas, problem and vision statements, user journey maps, the backlog hierarchy (epic, feature, user story), the user-story format with acceptance criteria, INVEST, estimation (story points, Fibonacci, planning poker), prioritisation (MoSCoW, Kano), and sprint mechanics (sprint goal, DoR, DoD, MVP, Scrum events).
W10 · Agile execution part 2: sprint delivery and monitoring
Sprint planning end to end, Definition of Ready versus Definition of Done, team capacity, sprint execution on the Scrum or Kanban board, and agile metrics (velocity and the sprints-to-finish forecast, the burndown chart, the burnup chart), with Sprint Review versus Retrospective.
W11 · Advanced agile practices and scaled Scrum
Product vision and agile planning (Product Vision Board, Lean Canvas, the roadmap to release to sprint cascade), advanced prioritisation (WSJF, the risk-adjusted backlog, spikes), scaled agile (Scrum of Scrums, Inspect and Adapt, system demo, RACI, program increments), and advanced metrics (Cumulative Flow Diagram, lead and cycle time).
W12 · Adaptive and hybrid models: putting it all together
The hybrid development approach (combining predictive governance with adaptive iterations), tailoring (PMBOK 7) to project size, complexity, risk and maturity, and synthesising the choice between predictive, iterative, incremental, adaptive and hybrid using the Stacey logic and the life-cycle characteristics table.
How it's assessed
Assessment structure
| Component | Weight | Format & timing |
|---|---|---|
| Assignment 1: Project (predictive plan) | 40% | Applied predictive project: business case to charter to scope statement and WBS to Gantt schedule and cost baseline to risk, quality and stakeholder artefacts, built on the running case study. Includes a Part 1 and Part 2 with group and individual components, and an individual reflection on the AlbaSim PM simulation (Artos scenario). Aligned to ULO1, ULO2 and ULO5. Earlier in the semester, spanning the predictive half (dates per the unit's Canvas, subject to change). Project deliverable; no bring-in restriction (it is take-home applied work). |
| Assignment 2: Project (agile execution) | 40% | Applied agile project: deliver a pilot feature over four sprints. Personas and a user journey, a prioritised backlog of INVEST user stories with acceptance criteria, sprint planning with DoR and DoD, a persona-to-requirement-to-story traceability table, and a live Scrum-board demonstration plus an interview. Later in the semester, spanning the agile half (dates per the unit's Canvas, subject to change). Project deliverable with a live demonstration and interview component. |
| Quiz / Test (invigilated) | 20% | Invigilated, closed-book quiz sat under Safe Exam Browser; multiple-choice, select the most suitable answer, time-pressured and covering content up to that point. Tests concept recognition (dependency type, sign of a cost variance, milestone duration, leading versus lagging indicator), not long hand calculation. Held in the teaching period under Safe Exam Browser (date per the unit's Canvas). Safe Exam Browser quiz: closed, no bring-in, not open-book. This page is a study aid, not the exam. |
- Pass on a weighted average of at least 50% across the two project assignments and the quiz. No single-component hurdle is stated in the unit materials reviewed.
- There is no traditional written final exam. The closest equivalent is a 20% invigilated Safe Exam Browser quiz of multiple-choice, select-the-most-suitable-answer items that reward quick concept recognition rather than multi-step hand computation.
- Calculator policy: The invigilated quiz is closed-book under Safe Exam Browser with no bring-in. The project assignments are applied take-home work where scheduling and cost tools (including ProjectLibre) are used, so quantitative methods are computed there rather than under quiz time pressure.
This is a coursework unit. Coursework carries 100% of the grade and the assignment 1: project (predictive plan) is the single heaviest piece at 40%, so steady work across the semester decides your result more than any one sitting. Project deliverable; no bring-in restriction (it is take-home applied work).
Final exam timing: No traditional final exam. The 20% invigilated quiz (Safe Exam Browser) is held during the teaching period in S2 2026; approx Nov 2026 for any end-of-semester assessment, confirm against the official Monash timetable.. Confirm the exact date and venue on the official exam timetable.
How to actually pass it
A weekly rhythm, two checklists, and the traps to avoid
The unit rewards consistency over cramming, and practice over re-reading. Here is the loop that works, then what to have nailed before each exam.
The weekly loop
Before the mid-semester checklist
- Be fluent in the predictive chain: business case to charter to scope statement to WBS (and the 100% rule) to Gantt to cost baseline.
- Drill the critical-path forward and backward pass until total float = LF − EF and the zero-float path are instant.
- Practise the PERT three-point estimate, the four estimation methods, and the ROM, budgetary and definitive accuracy ranges.
- Rehearse the earned-value cluster with sign conventions: CV = EV − AC, SV = EV − PV, CPI = EV / AC, SPI = EV / PV, EAC = BAC / CPI, and the rule that negative means bad.
- Know the governance set cold: the probability times impact risk score, EMV, the threat and opportunity responses, and contingency versus management reserve.
Before the final heaviest topics
- Master the agile half end to end: the Agile Manifesto values and principles, Scrum roles, events and artifacts, the backlog hierarchy with INVEST user stories, and DoR versus DoD.
- Practise sprint planning and monitoring: team capacity, velocity and the sprints-to-finish forecast, and reading a burndown versus a burnup chart.
- Lock down the predictive-to-agile contrast (Gantt versus sprint board, earned value versus burndown, lessons learned versus retrospective) because the tailoring judgement is assessed.
- Rehearse the scaled and hybrid material (WSJF, the risk-adjusted backlog, Scrum of Scrums, the Cumulative Flow Diagram, lead and cycle time, and choosing a lifecycle with the Stacey logic).
- Make the Assignment 2 traceability table and live Scrum-board demo airtight: the board must match the written backlog, and you should be able to defend every prioritisation and sprint-allocation choice in the interview.
The mistakes that cost marks
Misreading the earned-value sign convention. Both CV = EV − AC and SV = EV − PV are earned value minus the other quantity, so a NEGATIVE result is the bad case (over budget or behind schedule). Reading a negative cost variance as under budget because the cost number looks smaller is the single most common EVM error and it cascades into a wrong CPI, SPI and EAC.
Confusing the scope statement, WBS and charter. The charter authorises the project and names the PM, the scope statement defines boundaries and deliverables, and the WBS decomposes scope into work packages under the 100% rule. Mixing them up (for example listing activities as WBS items, or putting requirements in the charter) is a recurring trap in both the quiz and Assignment 1.
Treating predictive and agile as the same toolkit. Earned value, Gantt and lessons-learned belong to the predictive world; burndown, the sprint board and the retrospective belong to the agile world. The unit grades the ability to pick and tailor between them, so blurring the two (or using a Gantt where a sprint board is expected) loses marks.
Confusing the closely paired agile and governance terms. Definition of Ready (can we start?) is not Definition of Done (can we deliver?); a risk (future uncertainty) is not an issue (already happening); contingency reserve (known unknowns, inside the baseline) is not management reserve (unknown unknowns, outside it). Map each pair before the quiz.
Teaching team
Who teaches FIT5057
The bios below are factual. The star ratings are not ours: they are impressions from students who have taken the unit, so you can hear from people who sat in the lectures.
Dr Sanaz Nikfalazar
Teaching fellow at the Department of Human-Centred Computing, FIT, Monash University, focused on digital technology and flexible teaching methods.
Dr Rumana Ahmed
An Information Systems academic with more than two decades of teaching experience, integrating technical, business, and human-centred perspectives in IT education.
Dr Sulaiman Al Sheibani
Experienced IT project manager with a passion for AI, known for high-quality publications and oversight of major IT projects.
Dr Monoar Hossain
Cross-disciplinary academic with extensive teaching and research experience in Information Systems and numerous project contributions.
Dr Tasdik Hasan
A global mental health researcher and public health physician specialising in digital mental health, and a PhD candidate at Monash.
Liza Khwaja
A PhD candidate and Assistant Lecturer at the Faculty of IT, Monash University, with a background in industrial, product and mechanical engineering and experience in public administration and project implementation.
Teaching team as listed in the unit materials reviewed. AskSia does not rate lecturers; star ratings are submitted by students who have taken FIT5057.
What students say
What students actually say about FIT5057
Recurring themes from student reviews, paraphrased in our own words.
- Described as broad rather than deep: the challenge is covering both a full predictive plan and a full agile build in one semester, plus the judgement to tailor between them.
- Manageable with steady weekly effort because there is no single high-stakes final exam; the pressure is spread across two large project assignments and a short invigilated quiz.
- Students consolidate the manual procedures (critical path, PERT, the earned-value family) and the framework lists (PMBOK domains, Scrum events) into their own quick-reference sheets, since the quiz is closed-book.
- Demand for worked walkthroughs of the quantitative pieces (critical-path passes and the EVM cluster) and for clear contrasts between the closely paired terms.
- Interest in concept-recognition practice for the short, time-pressured Safe Exam Browser quiz.
- Interest in rehearsing the agile pilot end to end (personas, backlog, sprints, traceability) before the live Scrum-board demonstration and interview.
Recurring student opinions, paraphrased and aggregated, not official course information.
Where it fits
Prerequisites, related units & why it matters
A postgraduate Faculty of IT unit in the Master of IT and related programs; enrolment is governed by the Monash handbook entry. No prior project-management experience is assumed: it builds the toolkit from the project-versus-operations distinction upward, then layers PMBOK and agile on top.
Your FIT5057 study toolkit
Study the unit with Sia, not just read about it
Each tool already knows FIT5057: your syllabus, your texts, and where the marks are. Grouped by how you study, from first contact to exam week.
FAQ
Frequently asked questions
Is there a final exam in FIT5057?
No traditional written final exam. The grade is two project assignments worth 40% each plus a 20% invigilated quiz sat under Safe Exam Browser. The quiz is the closest thing to an exam: it is closed-book with no bring-in, multiple-choice, select the most suitable answer, and time-pressured.
How is FIT5057 assessed?
Two applied projects at 40% each and a 20% invigilated quiz. Assignment 1 is a predictive plan (business case, charter, scope and WBS, Gantt schedule, cost baseline, risk, quality and stakeholders). Assignment 2 is an agile build of a pilot feature over four sprints (personas, backlog, sprints, a Scrum-board demo and an interview). You pass on a weighted average of at least 50%, with no single-component hurdle stated in the materials reviewed.
How much maths is in FIT5057?
A moderate amount, and it is procedural rather than abstract. You learn the full manual machinery for critical path (forward and backward pass, total and free float), PERT three-point estimating, and the earned-value family (CV, SV, CPI, SPI, EAC), plus risk scoring (probability times impact) and velocity forecasting. These are computed mainly in the workshops and Assignment 1 (often in ProjectLibre); the timed quiz tests the concepts and sign conventions rather than long hand calculations.
What frameworks does FIT5057 use?
PMBOK 7 is the primary lens (the 12 principles and 8 performance domains), with PMBOK 6 layered in for the mechanics (the 5 process groups, the 10 knowledge areas and the scheduling, cost and earned-value tools). The agile half uses the Agile Manifesto, Scrum (the Scrum Guide), Kanban, XP and scaled frameworks such as SAFe, plus hybrid models. Lecturers contrast PMBOK 7 (the why) with PMBOK 6 (the how) and ask you to use both.
Is FIT5057 a group unit?
Yes, in large part. The two project assignments include group components with peer evaluation, and Assignment 2's agile pilot is run as a team through sprints to a live Scrum-board demonstration and interview. Being a reliable, contributing team member matters, because peer evaluation feeds the mark.
What is the running case study?
The unit uses a Monash student-services style web application as a recurring scenario across the term (a student-wellbeing or student-services digital product). Assignment 1 plans it predictively, and Assignment 2 narrows it to a single pilot feature delivered over four sprints, so the same product carries through both the predictive and the agile halves.
Study FIT5057 with Sia
Work through organisational context, project planning: scope statement, from scope to schedule and the rest of the unit with a tutor that knows it and quizzes you on the topics the assessments weight most heavily.
Start studying with Sia