How to build a project management course: a complete guide for lecturers

Central question: What makes a project different from routine operations, and who decides whether it is successful?

Begin by separating temporary project work from continuing operations and by making success broader than time and cost. Lecturers can frame a project as a temporary organisational system for creating a defined change, governed through sponsors, decision rights, constraints and explicit success criteria.

What this concept covers

• Projects, programmes, portfolios and operations.
• Project sponsors, project managers, teams, customers and governance bodies.
• The iron triangle and its limits: time, cost and scope versus value, outcomes and stakeholder acceptance.
• Project constraints, assumptions, dependencies and decision rights.
• Success criteria agreed at initiation and revisited through delivery.

Learning outcomes

By the end of this concept, students should be able to:

• Distinguish projects from programmes, portfolios and operations.
• Map governance roles and decision rights.
• Define measurable project success criteria beyond schedule and budget.
• Identify constraints and assumptions that shape delivery.
• Explain how project success can differ across stakeholders.

Supports Course Outcomes 1 to 2.

How to teach it

• Open with three activities and ask which are projects and why.
• Give groups the same project but different stakeholder briefs, then compare their success criteria.
• Build a simple governance map showing sponsor, project manager, team and escalation points.
• Ask students to rewrite vague success statements as measurable acceptance criteria.

Case-style example

Northstar University plans a £2.4 million student-service platform for September. The sponsor prioritises launch date, IT prioritises security, students want a fast mobile experience, and Finance requires payback within four years. Students define five measurable success criteria, rank the competing constraints and propose who owns each decision. One group may protect the fixed launch date; another may delay for security. Students discover that project success is negotiated before it is measured.

Where students struggle

Students often treat project success as synonymous with finishing on time and on budget. That misses benefits, quality, adoption and stakeholder trade-offs.

Reading and a quick check

Use PMBOK Guide Eighth Edition sections on value delivery, governance and performance domains. Quick check: ask students to name one project that could meet its schedule and budget yet still fail.

Where it leads

The next step is choosing a delivery approach that fits the uncertainty, work type and governance context.

Central question: When should a project use predictive, adaptive or hybrid delivery, and what should be tailored rather than copied?

Project management should not be taught as one universal sequence. Students need to recognise predictive, adaptive and hybrid lifecycles, then justify an approach from uncertainty, regulatory constraints, feedback speed, dependency structure and stakeholder needs.

What this concept covers

• Predictive, iterative, incremental, adaptive and hybrid lifecycles.
• Stage gates, sprints, releases and rolling-wave planning.
• Tailoring methods to uncertainty, risk, governance and product characteristics.
• Decision cadence and feedback loops.
• The difference between agility as responsiveness and agile methods as specific practices.

Learning outcomes

By the end of this concept, students should be able to:

• Compare predictive, adaptive and hybrid lifecycles.
• Select a delivery approach for a defined context.
• Justify tailoring decisions using project characteristics.
• Explain how governance changes across lifecycle choices.
• Design an appropriate review and feedback cadence.

Supports Course Outcomes 1 to 3.

How to teach it

• Contrast a regulated construction project with a digital-service build.
• Ask teams to place project features on an uncertainty-versus-change matrix.
• Have students design a hybrid lifecycle with named gates and iteration points.
• Debate where tailoring becomes undisciplined improvisation.

Case-style example

Helix Bank must deliver a new fraud-monitoring platform in nine months. Regulatory controls and the go-live date are fixed, but detection rules and user workflows will evolve through testing. Students choose a lifecycle, specify four governance gates and decide which work should iterate. A predictive team may maximise auditability; a hybrid team may protect controls while iterating workflows. Students discover that method choice is a governance decision, not a label.

Where students struggle

Students often equate predictive with old-fashioned and agile with faster. The useful distinction is how uncertainty, feedback and irreversible commitments are managed.

Reading and a quick check

Use PMBOK Guide Eighth Edition material on tailoring plus the 2025 hybrid-project-management scoping review. Quick check: give one sentence of project context and ask which delivery approach they would reject first.

Where it leads

Once the delivery approach is clear, students can decide which projects deserve scarce organisational resources.

Central question: Which projects should an organisation authorise, and what evidence makes a business case defensible?

Projects compete for money, people and executive attention. This concept connects strategy to project initiation by requiring students to articulate the problem, options, expected benefits, costs, risks and evidence behind an investment recommendation.

What this concept covers

• Strategic alignment and project selection criteria.
• Business cases, options analysis and project charters.
• Financial and non-financial benefits.
• NPV, IRR, payback and capital rationing as decision inputs.
• Benefits ownership and the difference between output delivery and value realisation.

Learning outcomes

By the end of this concept, students should be able to:

• Build a concise project business case.
• Compare competing projects against strategic and financial criteria.
• Interpret investment appraisal measures without treating one metric as decisive.
• Identify a benefits owner and measurable benefit profile.
• Recommend whether to authorise, defer, redesign or reject a project.

Supports Course Outcomes 2 to 4.

How to teach it

• Give three projects competing for one budget and require a ranked recommendation.
• Separate strategic scoring from financial appraisal before combining them.
• Ask students to write the project charter only after the business case is challenged.
• Use sensitivity questions to reveal which benefits are assumptions rather than evidence.

Case-style example

Aster Retail has £10 million for three initiatives: a £6 million warehouse automation project with NPV £2.1 million, a £4 million loyalty platform with NPV £1.8 million, and a £5 million energy retrofit with NPV £1.5 million plus a 24% emissions reduction. Students allocate the budget, name the benefits owner and write an authorisation recommendation. Different portfolios can be defensible. Students discover that capital constraints force strategy into the decision.

Where students struggle

Students often write business cases as advocacy documents and confuse forecast benefits with guaranteed benefits.

Reading and a quick check

Pair the PMBOK value-delivery discussion with a capital-appraisal refresher. Quick check: ask what evidence would make them cancel an attractive project before launch.

Where a simulation fits

The Capital Budgeting Simulation fits here after students know basic appraisal logic. It turns selection into a constrained CFO decision across competing projects, which is useful for discussing portfolio choice and the limits of metric-only ranking.

Where it leads

Authorised projects then need governance and stakeholder arrangements that make decisions and escalation workable.

Central question: How should a project manager build support, surface conflict and keep decisions moving across stakeholders with different interests?

Stakeholder management is not a communications calendar. It is the design of relationships, information flows, participation and escalation around a temporary change effort. Students should learn to distinguish influence, interest, impact and accountability.

What this concept covers

• Stakeholder identification, salience and influence-impact analysis.
• Sponsor responsibilities and executive decision-making.
• Engagement strategies and communication planning.
• Escalation routes, decision logs and information needs.
• Resistance, conflict and ethical treatment of affected stakeholders.

Learning outcomes

By the end of this concept, students should be able to:

• Analyse stakeholder influence and impact.
• Design a targeted engagement and communication plan.
• Specify sponsor and escalation responsibilities.
• Adapt messages to different stakeholder decisions.
• Respond to legitimate resistance without treating it as a communications failure.

Supports Course Outcomes 3 to 5.

How to teach it

• Map stakeholders from a contentious transformation case.
• Ask each group to produce one decision-ready update for a different audience.
• Role-play a sponsor escalation where time, quality and cost conflict.
• Compare a stakeholder register with an actual engagement strategy.

Case-style example

CivicLink is moving 1,200 council employees to a shared service centre. The sponsor wants £3 million annual savings, unions are concerned about roles, service managers fear disruption, and residents expect no fall in response times. Students map influence and impact, draft a sponsor escalation on a proposed three-month acceleration and design two stakeholder messages. Students discover that communication quality depends on the decision each audience must make.

Where students struggle

Students frequently produce generic stakeholder lists and broadcast-style communication plans rather than designing engagement around decisions and consequences.

Reading and a quick check

Use a contemporary stakeholder-engagement chapter or PMBOK performance-domain material. Quick check: ask which stakeholder should receive more attention - the most powerful or the most affected - and force a conditional answer.

Where it leads

Clear stakeholders make it possible to define what the project will and will not deliver.

Central question: How do project teams convert an ambiguous need into a controlled, deliverable scope?

Scope management is where strategy becomes executable work. Students should move from outcomes and requirements to deliverables, acceptance criteria and a work breakdown structure, while learning that more detail is not automatically better.

What this concept covers

• Problem statements, objectives and scope boundaries.
• Requirements elicitation, prioritisation and traceability.
• Deliverables, acceptance criteria and definition of done.
• Work breakdown structures and work packages.
• Scope baseline, assumptions, exclusions and change implications.

Learning outcomes

By the end of this concept, students should be able to:

• Translate objectives into deliverables and acceptance criteria.
• Prioritise and trace requirements.
• Construct a deliverable-oriented WBS.
• Identify scope exclusions and assumptions.
• Evaluate whether a proposed scope change belongs in the baseline.

Supports Course Outcomes 4 to 6.

How to teach it

• Give a vague project brief and ask students to identify hidden requirements.
• Build a WBS from deliverables rather than departmental tasks.
• Run a scope-boundary debate using 'in', 'out' and 'later' categories.
• Ask teams to test whether every requirement has an acceptance route.

Case-style example

Beacon Health is launching a patient-booking portal in 20 clinics. The brief says 'make appointments easier' and budgets £650,000 for six months. Students define six deliverables, write acceptance criteria for online booking and cancellation, create a two-level WBS and decide whether automated insurance verification belongs in scope. Including it may improve value but threaten timing. Students discover that scope control begins with explicit boundaries, not change forms.

Where students struggle

Students often write task lists instead of deliverable structures and leave acceptance criteria too vague to support later control.

Reading and a quick check

Use PMBOK material on scope and planning models. Quick check: ask students to distinguish a requirement, deliverable, work package and activity in one example.

Where it leads

A controlled scope provides the work that must now be sequenced and scheduled.

Central question: What determines the earliest credible finish date, and where does management attention actually change it?

Scheduling should be taught as dependency logic rather than software operation. Students need to understand activity networks, critical path, float, milestones, estimation uncertainty and the consequences of changing sequence or resources.

What this concept covers

• Activity definition, precedence and network logic.
• Duration estimation and three-point thinking.
• Critical path and total float.
• Milestones, baselines and rolling-wave detail.
• Fast-tracking, crashing and schedule-risk trade-offs.

Learning outcomes

By the end of this concept, students should be able to:

• Construct and interpret a precedence network.
• Calculate critical path and float.
• Identify activities where delay changes the finish date.
• Evaluate schedule-compression options.
• Explain why a visually busy Gantt chart can still hide weak logic.

Supports Course Outcomes 4 to 6.

How to teach it

• Build the network on paper before opening scheduling software.
• Give groups the same network with one ambiguous dependency and compare finish dates.
• Ask students to crash one activity under a fixed acceleration budget.
• Use a schedule update to distinguish variance from forecast impact.

Case-style example

Luma Events must open a conference venue in 18 weeks. Design takes 4 weeks, permits 3 after design, fit-out 7 after permits, AV installation 3 after fit-out, while recruitment takes 6 weeks and can start after design. Students draw the network, calculate critical path and float, then spend at most £40,000 to accelerate either permits by one week for £15,000 or fit-out by two weeks for £35,000. Students discover that shortening non-critical work may create no finish-date value.

Where students struggle

Students commonly identify the longest activity rather than the longest dependent path, or assume every delay matters equally.

Reading and a quick check

Use a scheduling chapter plus the A-Media case later in the course. Quick check: ask what happens to the critical path when a non-critical activity uses all its float.

Where it leads

A schedule becomes credible only when costs and resources are reconciled with it.

Central question: How should a project manager build a credible cost baseline and make trade-offs when funds are constrained?

Budgeting connects estimating, uncertainty, resource choices and investment discipline. Students should distinguish project cost from project value and learn how reserves, baseline changes and constrained allocation affect decisions.

What this concept covers

• Analogous, parametric and bottom-up estimating.
• Cost baselines, management reserve and contingency reserve.
• Time-phased budgets and cash needs.
• Capital budgeting, opportunity cost and constrained allocation.
• Cost-quality-schedule trade-offs and estimate confidence.

Learning outcomes

By the end of this concept, students should be able to:

• Select an appropriate estimating method.
• Build a simple time-phased project budget.
• Distinguish contingency from management reserve.
• Evaluate project funding under capital constraints.
• Defend cost trade-offs without confusing the cheapest option with the best option.

Supports Course Outcomes 5 to 7.

How to teach it

• Give teams early and late-stage information and ask how estimate confidence should change.
• Separate estimate, contingency and management reserve in a budget exercise.
• Run a capital-allocation exercise across projects before discussing portfolio consequences.
• Ask students which cost overrun should trigger reforecasting rather than blame.

Case-style example

Orchid Foods is planning a new packaging line. Base work is estimated at £1.9 million, identified-risk contingency is £180,000, and executives hold £120,000 management reserve. A supplier offers a £140,000 automation upgrade expected to save £70,000 annually for four years. Students build the cost baseline, separate reserves and recommend whether to add the upgrade under a £2.2 million funding cap. Students discover that baseline control and investment logic answer different questions.

Where students struggle

Students often add every reserve into the baseline, treat estimates as commitments and assume cost minimisation is the objective.

Reading and a quick check

Use Larson and Gray on estimating plus PMBOK planning guidance. Quick check: ask which reserve belongs in the performance baseline and why.

Where a simulation fits

The Capital Budgeting Simulation is the closest direct fit. Students act as CFO, appraise projects with NPV, IRR, profitability index and payback, then allocate a fixed budget across competing investments. Use the debrief to connect corporate capital choice to project authorisation.

Where it leads

Cost and schedule plans must then be made feasible through people, equipment and organisational capacity.

Central question: How should project leaders secure scarce resources and create a team capable of delivering under temporary authority?

Project managers rarely control every person or asset they need. This concept joins resource loading and capacity decisions with leadership, role clarity, team development and conflict management.

What this concept covers

• Resource requirements, calendars, loading and constraints.
• Responsibility assignment and role clarity.
• Team formation, psychological safety and conflict.
• Leadership across functional and project authority.
• Resource levelling, smoothing and prioritisation.

Learning outcomes

By the end of this concept, students should be able to:

• Identify and resolve resource conflicts.
• Create clear responsibility assignments.
• Evaluate resource levelling choices.
• Select leadership responses for different team conditions.
• Explain how incentives and organisational structure affect project delivery.

Supports Course Outcomes 6 to 8.

How to teach it

• Give two projects competing for the same specialist and require a negotiated allocation.
• Use a RACI-style exercise only after decision rights are discussed.
• Run a team-conflict role-play around a missed milestone.
• Compare levelling a schedule with simply asking the team to work harder.

Case-style example

Mosaic Energy has two simultaneous projects but only one data engineer, available 30 hours a week. Project Alpha needs 20 hours weekly for six weeks; Project Beta needs 18 and has a fixed regulatory deadline. Students propose a resource plan, revise one schedule and define escalation rights. Prioritising Beta protects compliance but delays Alpha; splitting time preserves both starts but increases coordination risk. Students discover that resource plans are strategic commitments, not staffing tables.

Where students struggle

Students often assume named resources are available and treat leadership as a separate soft-skill topic rather than a delivery mechanism.

Reading and a quick check

Use Larson and Gray on managing project teams and resources. Quick check: ask when resource levelling should legitimately move the project finish date.

Where a simulation fits

The Managerial Accounting Simulation can support a resource-allocation workshop because students must interpret operating economics and allocate scarce funds among competing opportunities. Frame it as an adjacent managerial decision, not as a project-management simulation.

Where it leads

With resources committed, teams still need to decide how much uncertainty to accept, mitigate or reserve for.

Central question: Which uncertainties deserve active management, and how should responses change the plan before problems occur?

Risk teaching becomes useful when students move beyond a register. They should connect uncertainty to objectives, prioritisation, response ownership, reserves and decision triggers, while distinguishing known risks from broader ambiguity.

What this concept covers

• Risk identification, causes, events and effects.
• Qualitative probability-impact analysis and quantitative thinking where appropriate.
• Threat and opportunity responses.
• Risk owners, action owners, triggers and residual risk.
• Contingency, reserves and escalation of emerging uncertainty.

Learning outcomes

By the end of this concept, students should be able to:

• Write decision-useful risk statements.
• Prioritise risks against project objectives.
• Design proportionate threat and opportunity responses.
• Assign ownership and response triggers.
• Connect risk exposure to schedule and cost contingency.

Supports Course Outcomes 7 to 9.

How to teach it

• Ban one-word risks and require cause-event-effect statements.
• Have teams rank the same risks using different stakeholder priorities.
• Convert top risks into funded actions with owners and trigger dates.
• Use a premortem to surface risks before a baseline is approved.

Case-style example

Vela Pharma is transferring a laboratory before a licence expires in 24 weeks. The specialist freezer has a 20% chance of four-week delivery delay, validation failure has a 10% chance of two-week rework, and a temporary lab costs £18,000 per week. Students quantify simple exposures, choose mitigations within a £70,000 contingency allowance and set escalation triggers. Different response bundles can be rational. Students discover that risk management changes today's plan, not tomorrow's explanation.

Where students struggle

Students often confuse issues with risks, rank everything 'high' and write responses that do not alter probability, impact or preparedness.

Reading and a quick check

Use the A-Media case and PMBOK uncertainty guidance. Quick check: ask students to rewrite 'supplier risk' as a cause-event-effect statement with an owner.

Where it leads

Risk responses often create procurement, quality or scope changes, which need disciplined control during execution.

Central question: How should a project decide what to buy, what quality means and which changes deserve approval?

Execution creates requests, defects, supplier dependencies and changing information. Students need a joined-up view of procurement strategy, quality criteria and integrated change control rather than three disconnected administrative processes.

What this concept covers

• Make-buy decisions and procurement strategy.
• Contract incentives, supplier selection and interfaces.
• Quality planning, assurance, control and acceptance.
• Change requests, impact analysis and change authority.
• Configuration, baselines and traceability of approved change.

Learning outcomes

By the end of this concept, students should be able to:

• Choose an appropriate procurement approach.
• Define measurable quality and acceptance criteria.
• Analyse the schedule, cost, risk and benefit effects of a change.
• Design a proportionate change-control route.
• Explain how contract incentives can transfer or create project risk.

Supports Course Outcomes 8 to 10.

How to teach it

• Compare fixed-price and time-and-materials procurement under uncertain scope.
• Give students a late change and require quantified impact before approval.
• Use defect data to distinguish prevention, assurance and inspection.
• Map which baseline artefacts must change after approval.

Case-style example

Arbor Hotels is refurbishing 40 rooms before peak season. A supplier proposes imported smart locks that add £52,000, save £9,000 annually in key-management costs and need six extra installation days. The contract charges £12,000 for each week of late opening. Students prepare a change-impact analysis, recommend approve, defer or reject, and identify contract and acceptance updates. Students discover that a small feature request can become a schedule, procurement and benefits decision.

Where students struggle

Students often view change control as bureaucracy rather than a mechanism for making trade-offs visible and authorised.

Reading and a quick check

Use PMBOK material on project work, delivery and measurement. Quick check: ask what minimum information a change authority needs before approving a scope addition.

Where it leads

Once work is moving, the project manager needs evidence that separates normal variance from a failing forecast.

Central question: How do project teams know whether delivery is genuinely on track, and what should they do when it is not?

Monitoring is valuable only when it changes a decision. Students should combine milestone evidence, cost and schedule variance, forecasting, benefits indicators and qualitative signals into a concise control view.

What this concept covers

• Baselines, actuals, forecasts and trend information.
• Milestone health, earned-value concepts and forecast-to-complete.
• Dashboards, status reports and decision thresholds.
• Issue management, corrective action and recovery planning.
• Performance measurement beyond plan-versus-actual logic.

Learning outcomes

By the end of this concept, students should be able to:

• Interpret schedule and cost performance evidence.
• Distinguish variance reporting from forecasting.
• Design a decision-focused status update.
• Recommend corrective action and recovery options.
• Identify when rebaselining is legitimate and when it conceals poor performance.

Supports Course Outcomes 9 to 10.

How to teach it

• Give students a 'green' dashboard with deteriorating forecasts and ask them to challenge it.
• Use simple earned-value data to focus on interpretation rather than arithmetic.
• Require every status report to end with decisions needed, not only updates.
• Run a recovery board where teams choose between scope, time and cost interventions.

Case-style example

Pulse Logistics is eight months into a £5 million systems project. Planned value is £3.2 million, earned value £2.8 million and actual cost £3.1 million. A critical integration milestone is also three weeks late, but the sponsor wants the dashboard left amber. Students calculate CPI and SPI, forecast likely implications, propose two recovery options and draft a one-page status update. Students discover that transparent forecasting matters more than cosmetically stable reporting.

Where students struggle

Students often report past variance without explaining forecast consequences or the decision required from governance.

Reading and a quick check

Assign Maylor et al. (2023) on performance beyond plan-execute logic. Quick check: ask why a project can be 'on budget' and still require urgent intervention.

Where a simulation fits

The Startup Creation Simulation can be used as an adjacent capstone environment across Sessions 9-12. Add lecturer-defined project artefacts such as a milestone plan, risk log, decision log and status update so students practise control around a live, evolving venture task.

Where it leads

The final concept asks how to close responsibly and whether the intended benefits actually survive delivery.

Central question: When is a project finished, who owns the benefits after handover and what should the organisation learn?

Closing a project is not merely archiving documents. It involves acceptance, transition, contractual closure, release of resources, benefits ownership and learning that can change future project decisions.

What this concept covers

• Formal acceptance, handover and transition to operations.
• Contract and financial closure.
• Benefits transition, measurement and post-project review.
• Lessons learned and knowledge transfer.
• Team release, stakeholder closure and ethical treatment of unfinished work.

Learning outcomes

By the end of this concept, students should be able to:

• Design a project closure checklist around acceptance and transition.
• Assign benefit ownership beyond project completion.
• Evaluate project success against original and revised criteria.
• Conduct a useful retrospective or post-project review.
• Translate lessons into actions for future projects.

Supports Course Outcomes 9 to 10.

How to teach it

• Give students a project that delivered every output but weak adoption and ask whether it is successful.
• Require a benefits-transition plan with owners and measurement dates.
• Run a retrospective that produces actions rather than generic lessons.
• Ask students what evidence should be retained for future portfolio decisions.

Case-style example

Harbour College finishes a £900,000 virtual-learning project two weeks early and £30,000 under budget. All 12 deliverables are accepted, but only 42% of lecturers use the new tools against a 70% benefits target. Students decide whether the project should close, assign post-project benefit actions and design a 90-day review. One view protects formal closure; another extends transition support. Students discover that output completion and benefit realisation are separate accountabilities.

Where students struggle

Students often stop at delivery and leave benefits, adoption and lessons ownerless.

Reading and a quick check

Use PMBOK value-delivery material and PMI Pulse work on business acumen. Quick check: ask who should own a benefit that matures six months after the project team disbands.

Where a simulation fits

Use the Startup Creation Simulation debrief as a retrospective if it has run as the capstone. Students compare intended milestones and decisions with actual progress, then identify what they would change in a second delivery cycle.

Where it leads

This closes the lifecycle and gives students an integrated basis for the final project recommendation and individual defence.

10-week course structure

A 10-session version combines adjacent planning topics while preserving authorisation, integrated planning, control and closure.

14-week course structure

A 14-session version separates complex planning and control topics and gives more space to applied workshops, capstone reflection and individual defence.

The Startup Creation Simulation is the closest approved fit for Project Management, but it should be positioned accurately. It is a 6 to 10 hour entrepreneurship simulation, not a dedicated PM simulation. Startup teams develop an opportunity and business model while Venture Capital teams set investment criteria; the experience then moves into pitch creation, live pitching, funding negotiation and reflection. For this course, the lecturer adds the Project Management layer around that live work.

Why it fits here

By Session 9 students already know project framing, governance, scope, schedule, cost, resources and risk. That lets the simulation become a temporary delivery environment in which students can practise mobilisation, milestone management, team roles, change decisions, status reporting and retrospective learning without pretending the platform itself teaches WBS or critical path.

What students do

• Startup teams: identify an opportunity, define the problem, solution and value proposition, size the market and complete a Business Model Canvas.
• Venture Capital teams: define an investment thesis, establish screening criteria and build an Investment Process Document.
• Pitch creation: Startup teams prepare an investor pitch while investor teams review the ventures and prepare questions.
• Pitch and negotiation: teams meet live, answer questions and negotiate investment amount and equity ownership, which determine post-money valuation.
• Reflection: teams compare funding, ownership and valuation outcomes across the cohort.
• Project Management overlay: the lecturer requires a charter, team responsibilities, milestone plan, risk and decision logs, one status update and a closing retrospective.

Recommended course placement

• Launch at the end of Session 9 after teams and leadership.
• Continue through Sessions 10 and 11 while students encounter change and control topics.
• Close in Session 12 with benefits/learning reflection and an individual defence.
• Use a shorter split if contact hours are tight, but preserve the project-management artefacts and debrief.

Knowledge students should have before the simulation

• Project charter and success criteria.
• Scope and milestone planning.
• Basic cost and resource constraints.
• Risk response and escalation.
• Team roles, stakeholder communication and change-control logic.

Delivery format

Suggested debrief questions

• Which milestone or dependency was least credible at the start?
• Where did new information change your plan, and how did you record that change?
• Which risk became an issue, and was your response trigger early enough?
• How did team roles or stakeholder incentives affect execution?
• What did your status report predict correctly, and what did it miss?
• Which lesson should become a concrete change in the next project rather than a generic observation?

The Capital Budgeting Simulation is a short, single-player finance simulation in which every student takes the role of CFO. Students first analyse three projects using NPV, IRR, profitability index and payback, select one and explain their reasoning. They then receive a fixed $10 million budget and choose a portfolio from eight independent projects. In Project Management, the value is the authorisation and constraint decision, not the calculation alone.

Why it fits here

Project managers need to understand why projects are selected, deferred or constrained before detailed planning begins. This simulation provides a clean capital-rationing decision that can be extended with strategic alignment, capacity, risk and benefits questions.

What students do

• Review three project briefs, discount rates, expected cash flows and qualitative risks.
• Calculate and interpret NPV, IRR, profitability index and payback.
• Select the strongest project and submit a reasoned justification.
• Review the documented outcome and compare calculation or interpretation differences.
• Allocate a fixed $10 million budget across eight projects to maximise portfolio NPV within the constraint.
• Compare portfolio value and the optimal allocation, then explain how strategic or delivery considerations might change a finance-only recommendation.

Recommended course placement

• After Session 3 as a project-selection and authorisation workshop.
• After Session 7 if you want to connect the exercise to budget constraints and resource allocation.
• Use the output as evidence for a short individual business-case or assumptions note.

Knowledge students should have before the simulation

• Basic cash-flow and discount-rate concepts.
• NPV, IRR, profitability index and payback at introductory level.
• The idea that project selection combines strategic, risk and financial evidence.

Delivery format

Suggested debrief questions

• Where did NPV, IRR and other measures point in different directions?
• What non-financial evidence could justify rejecting the highest-NPV project?
• What project-delivery risks are invisible in a portfolio score?
• How would resource capacity change the allocation?
• Which assumptions should a sponsor test before authorisation?

Grading with the Startup Creation Simulation

Startup Creation involves team-based venture analysis, business-model development, pitch preparation, live investor questioning and negotiated funding. For Project Management, assess only the PM overlay and the reasoning it generates rather than pretending funding outcome is a project-management score.

• Quality of the lecturer-defined charter, milestones and role allocation.
• Risk, issue and decision-log discipline across stages.
• How the team revised its plan when new information or negotiation changed priorities.
• Quality of the status report and retrospective.
• Individual defence of one project decision and one rejected alternative.

Grading with the Capital Budgeting Simulation

Students work individually as CFOs, calculate appraisal measures, select a project and allocate a fixed $10 million budget across eight projects. It is strongest as evidence for selection and constrained funding.

• Accuracy and interpretation of NPV, IRR, profitability index and payback.
• Quality of the project-selection justification.
• Capital-allocation reasoning under the fixed budget.
• Ability to explain what strategic, resource or delivery evidence could overturn the finance-only result.

Grading with the Managerial Accounting Simulation

Students individually compare three products, interpret managerial-accounting and investment measures, then allocate a $100 million budget through CFO, COO, CMO and CEO perspectives.

• Accuracy and interpretation of calculations.
• Quality of written product-selection reasoning.
• How well the student reconciles financial, operational and market priorities.
• Translation of allocation choices into resource or project constraints.

Evidence limitation: The platform records what each team decided, the terms they agreed and comparative outcomes across groups. That evidence supports your academic judgement; it does not replace it, and it does not establish which individual student made which argument. For individual simulations, use the participant-level calculations, decisions and written reasons described on the relevant live product page, but still apply your own marking criteria and moderation.

To control free-riding in group work, combine explicit role/contribution records with an individual assumptions note or short viva. Moderate group marks only where your regulations and evidence permit it. Do not convert a simulation leaderboard directly into grades.