MGTS7527 Project Management
MGTS7527 Overview
- Semester 2, 2026
- St Lucia
- UQ Business School
- Postgraduate course
- Weekly three-hour seminar
What the course is about
Project Management at the University of Queensland is a postgraduate course from the UQ Business School that introduces the principles and practices of managing projects and the stakeholder relationships around them.
- Assessed by A group project plan and an in-semester exam at 30% each, then a group stakeholder presentation and an individual reflection report at 20% each.
- Hardest step Making scope, schedule, cost, risk and quality agree with each other in one integrated plan, rather than writing five separate sections.
- How to prepare Learn each seminar's distinctions in pairs, such as risk and issue or verification and validation, and practise applying them to a case.
How MGTS7527 is assessed
| Component | Weight | Format |
|---|---|---|
| Team Project Plan | 30% | Group report of up to 3,500 words for groups of five or six, with a Microsoft Project schedule; due Week 6, Friday 4 September 2026, 5:00 pm; a peer assessment may adjust individual marks |
| In-Semester Exam | 30% | Closed-book exam on the key concepts, principles, frameworks and tools of Weeks 1 to 7; Week 8, 16 September 2026, in person during scheduled class time |
| Stakeholder Presentation | 20% | Same group and project as the plan, with a stakeholder register, a detailed communication plan and a concise project overview; Week 11, 14 October 2026, in person during class time |
| Reflection Report | 20% | Individual reflective paper of 1,700 words on leadership, ethics and organisational dynamics; due Week 13, Friday 30 October 2026, 5:00 pm |
The four tasks in the Semester 2, 2026 assessment summary total 100%. Team membership is set by random sampling, and a peer assessment after the Team Project Plan may affect individual scores for that task. The plan brief applies a late penalty of 10% per day; extension applications are made online before the due date and are decided by the UQ Business School Examinations team. Check Learn.UQ for any change.
Current MGTS7527 dates
| Date | Item | Control |
|---|---|---|
| 4 September 2026, 5:00 pm | Team Project Plan | Week 6; report, .mpp file, team agreement and individual cover sheets |
| 16 September 2026 | In-Semester Exam | Week 8; in person during scheduled class time |
| 14 October 2026 | Stakeholder Presentation | Week 11; in person during scheduled class time |
| 30 October 2026, 5:00 pm | Reflection Report | Week 13; individual submission |
Dates are as published in the Semester 2, 2026 assessment summary and the Team Project Plan brief. Confirm exact deadlines and submission settings in the live LMS.
What MGTS7527 covers
Twelve chapters follow the seven seminar weeks, from what a project is through initiation, planning, scheduling, cost, risk, quality and safety to monitoring, control, closure and standards.
Projects, the Iron Triangle and the Life Cycle
What makes work a project · the Iron Triangle · key terms · the five life-cycle phases · team principlesWhy the course starts with a definition
The first seminar defines a project the way the Project Management Institute did in 2025: a temporary effort, set in a unique context, that is undertaken to create value.
- The PMI definition of a project
- Four characteristics of a project
- Projects in practice and project management theory
- The Iron Triangle and the triple constraint
- Key project management terms
- The five life-cycle phases
Projects Inside the Permanent Organisation
Temporary and permanent organising · the four tensions · organisational and institutional context · projects across sectorsA temporary team inside a lasting organisation
Week 2 treats every project as a temporary organisational arrangement created by a permanent one.
- Temporary and permanent ways of organising
- Time, task, team and transition
- What each side provides and receives
- Four tensions between project and organisation
- Projects inside business practice
- Organisational and institutional context
Procurement and Project Contracts
Procurement through the life cycle · strategic procurement questions · contract types and risk · emerging contract trends · closing contracted workBuying in capability is a planned activity
Week 2 shows that procurement is woven through every phase.
- Why projects cannot simply start buying
- Procurement actions in each phase
- Purchasing and strategic procurement questions
- What a project contract establishes
- Fixed-price, cost-reimbursable, time and materials, target-cost
- Emerging trends in contract management
Initiation, the Project Charter and Scope
Business need and business case · the project charter · assumptions, constraints and requirements · scope boundaries · WBS and scope creepWhy before what
Week 3 opens with two questions. Initiation asks why the project is being done and whether it should be authorised; scope management asks what the project must deliver and what work that takes.
- Initiation and scope management questions
- Business need, business value and business case
- What the project charter records
- Assumptions, constraints and requirements
- Eliciting clear requirements
- Product scope and project scope
Integrated Planning and Task Assignment
What planning determines · the planning process · stakeholder engagement · the integrated plan · RACI and validating assignmentsPlanning answers eight questions
The second part of Week 3 defines planning as working out the route by which a project reaches its objectives and produces value: what is delivered, how, when, with what resources, at what cost, with whom, what could affect it, and how it will be governed.
- Eight questions planning answers
- Confirming direction and development approach
- The planning chain from scope to cost
- Planning stakeholder engagement
- Integrating the plan
- Progressive and rolling-wave planning
Schedule Logic and the Critical Path
Why schedules matter · scheduling terms · dependency types · the critical path method · float, forecasts and compressionA date needs logic behind it
Week 4 argues that schedule management is about making delivery logic visible: who hands what to whom, when resources are needed, and which dates are realistic.
- Why schedule management matters
- From scope to a working schedule
- Activities, milestones, leads, lags and float
- Finish-to-start and the other dependency types
- Finding the critical path
- Near-critical paths and float
Cost Estimates, Budgets and Earned Value
Why project finance matters · cost and budget terms · cost classifications · estimating techniques · earned valueSpending deliberately, not just spending less
The cost part of Week 4 frames project finance as estimating, securing, allocating, monitoring and forecasting the money needed to deliver value.
- Why project finance matters
- Cost estimate, budget and cost baseline
- Contingency reserve and management reserve
- Direct, indirect, fixed and variable costs
- Analogous, parametric, bottom-up and three-point estimates
- Building an approved budget
Risk Statements, Responses and the Risk Register
Risk, issue, assumption and constraint · the risk cycle · cause, event and impact · response strategies · a working registerFour words that are not interchangeable
The risk part of Week 4 starts by separating a risk, an uncertain event that could affect objectives, from an issue that has already happened, an assumption that is not yet confirmed and a constraint that limits options.
- Risk, issue, assumption and constraint
- The continuous risk cycle
- Cause, uncertain event and impact
- Risk breakdown structure categories
- Avoid, transfer, mitigate and accept
- Rating likelihood and impact
Quality, Time Pressure and Rework
What quality is and is not · requirement to evidence · assurance and control · verification and validation · cost of quality · time pressureA definition that rules things out
Week 5 defines quality as conformance to agreed requirements, fitness for the intended purpose, evidence that the deliverable works, and preventing defects as well as finding them.
- What quality is and is not
- Requirement, acceptance criteria and tolerance
- From requirement to quality evidence
- Quality assurance and quality control
- Verification, validation and acceptance
- Cost of conformance and nonconformance
Health and Safety in Project Execution
Why safety belongs in project management · hazard, exposure and residual risk · controls in order of strength · leading and lagging indicatorsSuccess includes how the work was done
The second half of Week 5 argues that health and safety is part of accountable delivery.
- Six reasons safety belongs in project management
- Hazard, exposure and health and safety risk
- Incidents, near misses and stop-work
- Integrating safety into execution
- Controls in order of strength
- Pressure signals and leadership responses
Monitoring, Control and Project Closure
Purposes of monitoring · the control loop · variance, trend and forecast · dashboards and control responses · closure and lessons learnedInformation first, then decisions
Week 6 separates monitoring, which produces information, from controlling, which uses it to keep decisions aligned with objectives and governance.
- Visibility, comparison, forecasting and decisions
- The six-step control loop
- Monitoring and controlling questions
- Baseline, current plan and forecast
- Variance, trend and forecast
- Dashboards with thresholds
Standards, PMBOK and Delivery Approaches
Why standards exist · standards, bodies of knowledge and certification · PMBOK and ISO 21500 · professional bodies · predictive, adaptive and hybrid deliveryA shared language that must be tailored
The last part of Week 2 explains why the profession uses standards: they give common terminology, shared principles, recognised practices and consistency across organisations.
- Why project management needs standards
- Standard, body of knowledge and certification
- The PMBOK Guide eighth edition
- The ISO 21500 family
- PMI and ISO compared
- Professional bodies and their roles
It follows the project life cycle, from initiation and planning through execution, monitoring and control to closure, and presents project management as both a strategic and an operational capability for cross-functional work, for example a new process, a system rollout or a redesigned supply chain.
Teaching runs as a weekly three-hour seminar that combines a lecture with an interactive workshop, with readings set before class and guest lectures from industry practitioners.
How the seven seminar weeks build
Week 1 defines a project, the Iron Triangle and the life cycle.
Week 2 places projects inside permanent organisations and their institutional context, and covers procurement, contracts, standards and professional bodies. Week 3 moves from business need to charter, requirements, scope and the work breakdown structure, then to integrated planning and RACI assignment. Week 4 covers time, cost and risk: the critical path, estimating, budgets, earned value and the risk register.
Week 5 covers quality, the pressure between time and quality, and health and safety.
Week 6 covers monitoring, control and closure, and Week 7 compares agile frameworks with the PMBOK framework.
What the assessment rewards
The Team Project Plan asks groups to act as a consultancy and produce one integrated plan, scheduled in Microsoft Project, for a case project; its rubric weights four sections equally and rewards precise, significant and well-justified choices over long definitions.
The closed-book In-Semester Exam tests the concepts, frameworks and tools of Weeks 1 to 7. The Stakeholder Presentation and the Reflection Report then turn to communication, leadership, ethics and team dynamics. This guide gives each topic its own chapter, with an original worked example and practice items, so the distinctions the course draws can be rehearsed and applied.
Worked example · free
What happens when the kitchen module slips in the food-truck network
- 1Route through the kitchen: 3 + 7 + 4 + 2 + 1 = 17 days.
- 1A-B-D-F-G is unchanged at 16 days and A-B-E-F-G at 14 days, because neither passes through C.
- 1The longest route is now A-C-D-F-G, so it becomes critical and the finish moves from 16 to 17 days.
- 1The old critical path now has 17 minus 16 = 1 day of float, so it is near-critical and still needs watching.
Key terms
- Triple Constraint
- The balance a project keeps between time, cost and scope while still meeting its quality and value targets.
- Business Value
- The net quantifiable benefit a project or other business endeavour produces, tangible, intangible or both.
- Stakeholder
- Any person, group or organisation that can affect a project, be affected by it, or see itself as affected.
- Product Scope
- What the finished product, service or result will be like: its features and properties.
- Project Scope
- The work required to create a project's product, service or result.
- Dependency
- A logical relationship that sets the order in which two schedule activities can occur.
- Budget at Completion
- The whole approved budget that a project's performance measurement baseline adds up to.
- Actual Cost
- The cost actually incurred for the work completed by a status date.
- Mitigation
- A risk response that reduces the likelihood of a threat, its consequences, or both.
- Verification
- Checking a deliverable against its specifications, requirements and design to confirm it was built right.
- Control Loop
- The repeating cycle of comparing status with a baseline, diagnosing, forecasting and deciding on action.
- Responsibility Assignment Matrix
- A project tool that maps tasks against team roles so ownership of each piece of work is clear.
- Professional Body
- An organisation that supports a profession through membership, standards, certification and development.
MGTS7527 FAQ
How is project management assessed at UQ in Semester 2, 2026?
Four tasks make up the grade. The Team Project Plan and the In-Semester Exam are worth 30% each, and the Stakeholder Presentation and the Reflection Report 20% each. The plan and the presentation are group work in the same randomly sampled team; the exam and the reflection are individual.
What does the In-Semester Exam cover?
The assessment summary describes it as a closed-book exam on the key project management concepts, principles, frameworks and tools covered in Weeks 1 to 7. It is held in person during scheduled class time in Week 8, on 16 September 2026, so every chapter of this guide is within its scope.
What goes into the Team Project Plan?
One integrated professional report of up to 3,500 words in four sections: project definition, scope and stakeholders; requirements, schedule and resources; cost, quality and risk; and responsible delivery with a final recommendation. Groups also submit the Microsoft Project file, a team agreement and individual cover sheets.
Do I need Microsoft Project for this course?
Yes, for the Team Project Plan. The brief lists Microsoft Project as required software, asks for a schedule showing activities, dependencies, milestones, supplier lead times, resources and the critical path, and requires the .mpp file to be submitted alongside the PDF report.
What is the Stakeholder Presentation?
A Week 11 presentation, delivered in person during class time by the same group that wrote the project plan, on the same project. It must include a stakeholder register, a detailed communication plan and a concise project overview, so the engagement planning ideas from Week 3 are central.
What should the Reflection Report discuss?
It is an individual paper of 1,700 words answering three guiding topics: your own leadership style and contribution, the ethical considerations that arose in your project work and how you responded, and how team dynamics, responsibilities, communication and any conflict shaped the experience.
What happens if a project plan is submitted late?
The Team Project Plan brief applies a penalty of 10% per day for late submissions. Extensions are requested online before the due date and are decided by the UQ Business School Examinations team rather than course staff, and a technology failure will not usually count as a good reason.
Questions students ask in each MGTS7527 chapter
- How does the course define a project?
- It uses the Project Management Institute's 2025 definition: a temporary effort, set in a unique context, that is undertaken to create value. Temporary means it has a beginning and an end; unique context means its goals, stakeholders, approach and conditions set it apart from routine work. Chapter 01 · Projects, the Iron Triangle and the Life Cycle
- Why can a project not succeed on its own?
- Because it depends on the permanent organisation for staff, funding, authority and decisions, and must hand its output back to people who will run it. Projects struggle when staff are withheld, sponsors decide slowly, or the team builds something operations cannot maintain. Chapter 02 · Projects Inside the Permanent Organisation
- When should procurement planning begin?
- In initiation, when the team identifies whether external capability may be needed, looks at the supplier market and estimates initial costs. Detailed procurement planning follows in the planning phase, before suppliers are selected and engaged. Chapter 03 · Procurement and Project Contracts
- What is the difference between a project charter and a project plan?
- The charter authorises the project at a high level: why it exists, its objectives, expected value, major stakeholders, initial assumptions and constraints, and who has authority. The project management plan comes later and sets out the detailed approach to delivery. Chapter 04 · Initiation, the Project Charter and Scope
- Why must scope be planned before cost and schedule?
- Because resource and financial plans have to rest on the work that actually needs doing. The course's chain runs from scope to activities to resources to costs, so a missing work package always reappears later as a missing cost or a late date. Chapter 05 · Integrated Planning and Task Assignment
- Does critical mean the most important activity?
- No. Critical means the activity sits on the longest path, so any delay to it moves the project finish date unless recovered. An activity off the critical path can still matter a great deal for quality or safety. Chapter 06 · Schedule Logic and the Critical Path
- Is the cost baseline the same as the project budget?
- Not necessarily. The cost baseline includes the work estimates and contingency for identified risks; the project budget can also include management reserve held outside the baseline for unforeseen work, which is released only through governance. Chapter 07 · Cost Estimates, Budgets and Earned Value
- How do I write a good risk statement?
- Name the cause, the uncertain event and the impact on objectives in one sentence: because something is true, something may happen, which could affect a named objective. A label such as weather risk gives the owner nothing to monitor. Chapter 08 · Risk Statements, Responses and the Risk Register
- What is the difference between verification and validation?
- Verification asks whether the deliverable was built right, checking it against specifications, requirements and design. Validation asks whether the right thing was built, checking it works for the intended use, users and operating context. A deliverable can pass one and fail the other. Chapter 09 · Quality, Time Pressure and Rework
- Why is health and safety part of project management rather than a separate function?
- Because project decisions about schedule, sequence, staffing and suppliers create or remove hazards, and accountable leaders must make unsafe trade-offs visible. The course treats project success as including how the work was done, not only what was delivered. Chapter 10 · Health and Safety in Project Execution
- Why should the baseline not simply be moved when a project slips?
- Because the baseline is the approved reference for judging performance. Moving it silently makes the project look on track while hiding the variance. A new baseline needs an authorised change; the forecast is where the latest expected dates belong. Chapter 11 · Monitoring, Control and Project Closure
- What is the difference between PMBOK and ISO 21500?
- The PMBOK Guide is PMI's professional standard and body of knowledge, with principles, performance domains, practices and tools tied to PMI certification. The ISO 21500 family is a set of international consensus standards giving high-level concepts and guidance across countries and organisations. Chapter 12 · Standards, PMBOK and Delivery Approaches
How to prepare for the assessments
Work through the course in three passes. First, for each seminar week, write the distinctions the course draws in pairs: project and operation, assumption and constraint, product and project scope, responsibility and accountability, risk and issue, contingency and management reserve, verification and validation, corrective and preventive action.
Say each half aloud with an example; the closed-book exam rewards that kind of precise recall.
Second, take one case project, ideally the one your group plans, and run it through every chapter in order: write its charter, a first-level work breakdown structure, a RACI for five tasks, a small network with its critical path, a budget build-up with contingency and reserve, five risks in cause, event and impact form, and a closure checklist.
Checking that these pieces agree with each other is exactly what the rubric rewards. Third, before the presentation and the reflection, reread the stakeholder engagement and team material, and collect specific moments from your group work that you can explain with a course idea.
Your AI Project Management tutor for MGTS7527
Stuck on a hard MGTS7527 question? Sia is AskSia’s AI Project Management tutor — ask any MGTS7527 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.