FIT5057 Project Management
FIT5057 Overview
- Monash University
- S2 2026
- 7 chapters
- Project Management
FIT5057 Project Management develops the judgement, tools and collaborative practices used to manage modern information technology projects. The Semester 2 2026 sequence begins with the reason a project should exist: stakeholder value, strategic fit, evidence and professional responsibility.
- Assessed by Project 1 40% · Project 2 40% · Quizzes 20% · Learning and Teaching Agreement Quiz — Learning and Teaching Agreement Quiz is a hurdle
- Key terms Business Case, Project Charter, Traceability Matrix, Scope Baseline
- Assessment move Study this unit as one evidence chain.
- Most asked Is there a final examination?
What you get in the full FIT5057 Study & Assessment Guide
- 7 chapters, 31 pages — every assessed topic, week by week
- 19 original practice questions, each with a model answer
- 7 worked examples, solved the way FIT5057 marks
- 7 computed figures, redrawn from the course’s own numbers
- Before-you-submit checklist for the Project 1 (40%) — what markers reward, what costs marks
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full study & assessment guide.
FIT5057 Course Changes in Semester 2 2026
Compared with Semester 1 2026
What's new
- ✅Quizzes20%
- ✅Learning and Teaching Agreement Quiz
What's removed
- ❌Quiz / Test20%
How FIT5057 is assessed in S2 2026
| Component | Weight | Format |
|---|---|---|
| Project 1 | 40% | Group project evidence with written submission and scheduled applied-class components. Published submission: 18 September 2026 at 11:55 PM. |
| Project 2 | 40% | Group Agile project with compiled written work and a scenario-based interview component. Published submission: 2 November 2026 at 11:55 PM. |
| Quizzes | 20% | Individual timed quizzes across the teaching period. Published details vary by quiz, so check each quiz's current instructions. |
| Learning and Teaching Agreement Quiz · hurdle | Zero-weight access hurdle. The current page requires 100% to unlock assessment materials and permits multiple attempts. |
From the course outline for Semester 2 2026 (as of 2026-10-30); dates and venues are subject to confirmation. Always check your own subject guide and LMS for the authoritative timetable. See how FIT5057 has been assessed over time
How FIT5057 has been assessed over time
2 teaching periods tracked. Open an earlier period to see its full assessment.
- Semester 2 2026 CurrentSee table above ↑
Semester 1 2026ShowHide
Component Weight Format Assignment 1 — Predictive Project 40% Business case → charter → scope & WBS → Gantt/CPM → cost → risk → governance Assignment 2 — Agile Project 40% Personas → backlog → sprints → Scrum-board demo + interview Quiz / Test 20% Safe Exam Browser · closed-book, invigilated · short MCQ block testing concept recognition across all 12 weeks — confirm the exact split in your unit guide Final exam: 20%. Source: course outline, as of 2026-06-13.
What other students are asking about FIT5057
- Where can I find lecture notes or study guides for FIT5057 at Monash?
- The FIT5057 study guide in AskSia Library covers Project Management in 7 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in FIT5057?
- No final exam is listed in the offering this AskSia Library guide is built from; FIT5057 is assessed by Project 1 40%, Project 2 40%, Quizzes 20%.
- What does FIT5057 cover on scope management?
- In AskSia Library's FIT5057 guide, the Scope Management chapter explains requirements, traceability, scope boundaries, work breakdown structures and change control.
- What does FIT5057 cover on schedule and cost management?
- In AskSia Library's FIT5057 guide, the Schedule and Cost Management chapter explains dependencies, critical paths, cost baselines, estimates and investment value.
- What does FIT5057 cover on risk and governance?
- In AskSia Library's FIT5057 guide, the Risk and Governance chapter explains risk ownership, governance authority, escalation and systems auditing.
What FIT5057 covers
Seven connected chapters move from project selection and predictive planning into Scrum delivery, release judgement and hybrid control.
Project Management Foundations
Value delivery, project selection, business cases, charters and professional judgementProject Management Foundations asks whether a proposed project should exist before a team commits delivery resources. It connects problems, options, business cases, project charters, stakeholder value and professional judgement.
- Projects compared with ongoing operations
- Outputs, outcomes, benefits and stakeholder value
- Weighted scoring for project alternatives
- Business cases and investment assumptions
- Project charters and formal authority
- Professional, ethical and sustainability judgement
Scope Management
Requirements, traceability, scope boundaries, work breakdown structures and change controlScope Management converts stakeholder needs into requirements, deliverables, work packages and acceptance evidence. This chapter shows how a requirements traceability matrix, scope statement and work breakdown structure form one control system.
- Functional and non-functional requirements
- Requirements sources, owners and priorities
- Scope inclusions, exclusions and assumptions
- Requirements traceability matrices
- Work breakdown structures and work packages
- Change requests and baseline control
Schedule and Cost Management
Dependencies, critical paths, cost baselines, estimates and investment valueSchedule and Cost Management connects activity dependencies with estimates, resources and approved spending.
- Activities, dependencies and milestones
- Precedence networks and critical paths
- Schedule compression trade-offs
- Hours, rates and basis of estimate
- Time-phased cost baselines
- Discounted cash flow and net present value
Risk and Governance
Risk ownership, governance authority, escalation and systems auditingRisk and Governance explains how uncertainty becomes owned action inside a clear authority structure. You will write cause-event-effect risk statements, rate probability and impact consistently, choose responses that change exposure, and record residual risk.
- Cause-event-effect risk statements
- Probability, impact and priority ratings
- Threat and opportunity responses
- Risk ownership, triggers and residual exposure
- Governance authority and escalation tolerances
- Systems auditing and corrective controls
Stakeholder and Quality Management
Engagement, communication, acceptance evidence, quality controls and resource capacityStakeholder and Quality Management joins engagement, communication, acceptance and resource capacity. Stakeholder analysis should change what evidence is communicated, when and by whom.
- Stakeholder identification and analysis
- Influence-interest engagement choices
- Communication purpose, cadence and feedback
- Quality assurance compared with quality control
- Acceptance criteria and evidence
- Resource loading and over-allocation
Agile Fundamentals
Empiricism, Scrum accountabilities, events, artefacts, user stories and DoneAgile Fundamentals introduces Scrum as an empirical framework for complex work. Transparency, inspection and adaptation operate through accountabilities, events, artefacts and their commitments.
- Transparency, inspection and adaptation
- Product Owner, Developers and Scrum Master
- Sprint Planning and Daily Scrum
- Sprint Review and Sprint Retrospective
- Product, Sprint and Increment commitments
- User stories, acceptance and Done
Advanced Agile
Sprint planning, burndown interpretation, servant leadership, reviews and hybrid deliveryAdvanced Agile applies Scrum under delivery pressure.
- Sprint Planning and capacity forecasts
- Burndown interpretation and goal risk
- Daily adaptation of the Sprint Backlog
- Scrum Master service under pressure
- Sprint Review and Retrospective evidence
- Hybrid delivery and governance integration
It then follows an approved idea into a business case and charter, requirements and scope, a work breakdown structure, scheduling, cost, risk, governance, stakeholder engagement, communication, quality and resource control.
The later teaching sequence moves into Scrum so students can compare predictive planning with adaptive delivery and explain when a tailored or hybrid approach is defensible.
The unit is practical because its artefacts depend on one another. A requirement should lead to an approved deliverable, a work package, scheduled activities, cost assumptions, risk responses and acceptance evidence.
If one item changes, the project manager must trace the effect through the rest of the plan and route the decision to the right authority. This guide therefore teaches connected reasoning rather than isolated templates.
Its original examples use new organisations and numbers, with each quantitative result printed step by step for checking.
The current assessment structure contains two Projects worth 40% each and a Quiz / Test component worth 20%. A separate Learning and Teaching Agreement Quiz is a zero-weight access hurdle that requires full completion before assessment materials unlock.
No final examination appears in the current assessment table. The most useful preparation is to rebuild the project evidence chain, practise short scenario judgements, verify calculations and audit the final submitted artefacts against the current task instructions.
Worked example · free
Choose a project option with visible criteria
- +2Portal score = 4 x 40 + 5 x 35 + 2 x 25 = 385 weighted points.
- +2Assisted score = 5 x 40 + 3 x 35 + 4 x 25 = 405 weighted points.
- +2Recommend Assisted on the stated criteria, then test whether its access advantage and risk score are supported by credible evidence.
Key terms
- Business Case
- A decision document that justifies investment by connecting project options with value, benefits, costs, risk and strategic fit.
- Project Charter
- A formal record of authorised purpose, direction, high-level scope, success criteria and delegated project authority.
- Traceability Matrix
- An audit trail linking stakeholder needs and requirements to deliverables, work and acceptance evidence.
- Scope Baseline
- The approved scope statement, work breakdown structure and supporting detail used to control project boundaries.
- Critical Path
- The longest controlling route through a dependency network, whose delay changes the planned project finish.
- Cost Baseline
- Approved project spending distributed across the periods when the scheduled work is expected to occur.
- Net Present Value
- The sum of discounted future net cash flows, including the initial project outflow, used to assess financial value.
- Risk Owner
- The accountable person who monitors a risk, maintains its response and escalates when action or authority is required.
- Quality Assurance
- Planned activity that improves or evaluates the process used to produce a conforming project result.
- Quality Control
- Inspection or testing that compares an actual deliverable with its requirement and acceptance criteria.
- Product Goal
- The longer-term objective that gives the Scrum Team a target for product planning and backlog decisions.
- Sprint Goal
- The single objective that gives coherence to the work selected for a Sprint and guides adaptation.
- Definition of Done
- The shared quality commitment that work must satisfy before it can become part of a usable Increment.
- Sprint Review
- A collaborative inspection of the Sprint outcome and changing environment that adapts future product work.
FIT5057 FAQ
How is the unit assessed?
The current structure has two Projects worth 40% each and a Quiz / Test component worth 20%. A separate Learning and Teaching Agreement Quiz carries no unit weight but is an access hurdle requiring full completion before assessment materials unlock.
Is there a final examination?
No final examination appears in the complete Semester 2 2026 assessment table captured for this guide. The assessed rows are two Projects and Quiz / Test. Check the current assessment instructions if the teaching team publishes an operational change.
Why does traceability matter across project artefacts?
Traceability shows why each deliverable and work package exists, what requirement it satisfies and how acceptance will be demonstrated. It also lets a project manager follow a change into the schedule, cost, risk, stakeholder and quality evidence that must be updated.
Which quantitative methods should I practise?
Practise weighted scoring, dependency and critical-path reasoning, hours-times-rate cost estimates, time-phased baselines, resource capacity checks, risk ratings and net present value. Print each input and intermediate step so the recommendation can be recomputed and challenged.
How should I prepare for the Scrum topics?
Learn the accountabilities, events, artefacts and commitments as a connected empirical system. Then practise scenarios involving Sprint Goal risk, an unplanned stakeholder request, an incomplete Definition of Done, Sprint Review evidence and a Retrospective improvement.
What should I check immediately before submission?
Open the live task, verify the required file and group process, recompute quantitative results, and audit identifiers across requirements, scope, WBS, schedule, cost, risk and acceptance evidence. Finally open the submitted file and confirm the platform records the required submission state.
Questions students ask in each FIT5057 chapter
- What is the difference between a business case and a project charter?
- A business case justifies investment by comparing options and expected value. A project charter records what has been authorised, establishes high-level direction and gives the project manager a formal basis for coordinating the work. Chapter 01 · Project Management Foundations
- What does a requirements traceability matrix do?
- It links each need or requirement to its source, owner, priority, deliverable and acceptance evidence. The links help the team detect missing work, unsupported features and the downstream effects of a proposed change. Chapter 02 · Scope Management
- Why is a Gantt chart not enough for schedule reasoning?
- A Gantt chart displays timing, but the dependency logic explains why activities start and finish when shown. The network also reveals which route controls the finish and where limited scheduling flexibility exists. Chapter 03 · Schedule and Cost Management
- What makes a risk response specific enough?
- It names the action, owner, timing or trigger and the exposure it is intended to change. A statement such as monitor closely is incomplete unless monitoring leads to a defined decision or response. Chapter 04 · Risk and Governance
- How should an influence-interest grid be used?
- Use it to choose an initial engagement posture, then verify the stakeholder's actual information needs, warning signs and decision role. Positions can change as the project moves between planning, testing and release. Chapter 05 · Stakeholder and Quality Management
- What are the three Scrum accountabilities?
- The Product Owner maximises value and manages the Product Backlog effectively. Developers create a usable Increment and own the Sprint Backlog. The Scrum Master serves the team and organisation through coaching, facilitation and impediment removal. Chapter 06 · Agile Fundamentals
- What does a burndown chart actually tell a team?
- It shows how remaining work changes over Sprint time. A line above the ideal trend prompts inspection, but it does not explain the cause or decide whether the Sprint Goal is at risk without backlog, blocker and quality evidence. Chapter 07 · Advanced Agile
How to prepare for the assessments
Study this unit as one evidence chain. Begin each session by choosing a project decision, such as authorising an option, accepting a scope change or deciding whether a Sprint Goal is at risk. Name the accountable role and the artefacts that provide evidence. Rebuild one quantitative example without notes, showing units, signs and assumptions.
Then trace one identifier across requirements, scope, WBS, schedule, cost, risk and quality evidence. For Scrum, use the Product Goal, Sprint Goal and Definition of Done to explain why a team adapts rather than reciting event definitions. Before either project submission, compare every artefact with the current task instructions, test internal percentages within the correct 40% component, and run a full exported-file review.
Short scenario answers should finish with a recommendation that states the evidence, trade-off, authority and next action. This routine matches the unit's emphasis on professional judgement, connected project controls and defensible communication.
Your AI Project Management tutor for FIT5057
Stuck on a hard FIT5057 question? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Project Management 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.