CIVL1810 Chap.1 Construction Projects, Stakeholders and the Life Cycle
Construction Projects, Stakeholders and the Life Cycle
Week 1 sets the vocabulary the rest of the unit assumes. A project is work with an end date, run once, to produce something that did not exist before, and it never comes without uncertainty.
Around that definition sit the management triangle of cost, time, quality and scope; the wide definition of a stakeholder as anyone actively involved or whose interests may be positively or negatively affected; the five process groups; and the phase, gate and gate decision structure that decides whether a project may commit more resources.
The most recent past paper opens here, with short definition questions on the project life cycle and on why monitoring and controlling matters.
What this chapter covers
- 01
What a project is: unique purpose, temporary, resourced from various areas, and involving uncertainty
- 02
Project management as a process: initiating, planning, executing to the approved plan, controlling, handing over and closing
- 03
The management triangle: cost, time, quality and scope, and why pulling one pushes another
- 04
Stakeholders defined as anyone actively involved or whose interests may be positively or negatively affected by performance or completion
- 05
The dimensions along which construction projects vary, from size and scope through to regulatory requirements
- 06
Project delivery methods, the factors that influence them, and their direct impact on contracting strategy
- 07
Five process groups: initiation, planning, execution, monitoring and controlling, and closing
- 08
Phases, gates, the three questions a gate asks, and the four gate decisions of go, no go, hold and recycle
- 09
Pre project documents: the business case as a documented economic feasibility study, and the benefits management plan
- 10
The project charter as the document that formally authorises a project and empowers the project manager
- 11
The construction project management plan, and the requirement that it be bought into, approved, realistic and formal
Placing a gate decision
- +1Recall the three questions a gate puts. Is the previous stage genuinely finished, does the case still hold on the numbers and on judgement, and is there a credible plan for meeting the objectives.
- +1Test the scenario against those questions. The technical work is complete, so the checklist is satisfied, but the business case has failed on its own criteria and nothing external is expected to change.
- +1Choose and justify. The decision is no go: it does not authorise movement to the next stage and eliminates the project from further review. Hold is wrong because hold waits on technical, marketing or environmental change and none is expected. Recycle is wrong because it sends the team back to refine deliverables, and the deliverables are not deficient. Go is wrong because resources committed now cannot be recovered.
Key terms
- Project
- Work with an end date, done once, to bring into being something that did not exist before, whether a product, a service, an outcome or a better way of working. Four attributes define it: a purpose of its own, fixed start and finish, resources drawn from several places, and uncertainty.
- Stakeholder
- Any person or organisation actively involved in a project, or whose interests may be positively or negatively affected by its performance or completion. The second half of the definition is what includes the neighbour, the regulator and the future user.
- Gate
- A go or no go decision point preceding each stage. It asks whether the previous stage is complete, whether the project still makes business sense on quantitative and qualitative criteria, and whether there is a plan to meet the objectives.
- Gate decision
- One of four outcomes. Go authorises movement to the next stage; no go eliminates the project from further review; hold pauses it pending technical, marketing or environmental change; recycle returns it to the previous stage for refinement and resubmission.
- Project charter
- The document that brings a project formally into being and hands the project manager the right to commit the organisation's resources to it. What it buys is a visible line from this job to what the organisation is trying to achieve.
- Assumption log
- The record of every factor treated as true, real or certain, often without proof or demonstration, together with the project's constraints, maintained across the whole life cycle.
Construction Projects, Stakeholders and the Life Cycle FAQ
Why is monitoring and controlling described as critical?
Because it is the only process group that produces forward looking information. It tracks, reviews and regulates progress against the objectives set in the plan, and its benefit is that stakeholders can see the current state, the steps taken and the budget, schedule and scope forecasts.
Without those forecasts a gate meeting has nothing to decide on, so a project that no longer makes sense keeps consuming resources, and commitment rises with every stage entered.
What is the difference between a phase and a stage gate?
A phase is a set of parallel activities carried out to move the work forward, and its job is to produce the information a decision meeting needs. The gate is the decision point that precedes the next stage. So the phase generates evidence and the gate consumes it. Life cycles differ from industry to industry, which is why the shape matters more than any particular list of phase names.
How much detail does a project charter need?
Enough to authorise the work and to give the project manager authority over organisational resources.
It typically carries the project description and justification, high level requirements and risks, scope and major deliverables, a timeline with milestones, a summary budget with its funding source, assumptions and constraints, key stakeholders, the assigned team with responsibility and authority levels, and the name and authority of whoever authorised it.
Who authorises a construction project?
Someone external to the project itself: a sponsor, a project management office, or a portfolio steering committee. They may write the charter or delegate writing it to the project manager, but the authority originates outside the delivery team. That separation is what makes a gate decision meaningful rather than a self assessment.
Exam move
Learn this chapter as definitions plus consequences, because that is how the short opening questions are marked. Write the project definition with its four attributes on one line, then the stakeholder definition with both halves, then the five process groups, then the four gate decisions.
Practise saying what follows from each: uncertainty is why contingency and gates exist, the external authoriser is why a gate is not a self assessment, and the resource ramp is why stopping early is cheap. Then test yourself with scenarios rather than recall: given a described situation, which gate decision applies and why are the other three wrong. That elimination habit is worth several marks on its own.
Working through Construction Projects, Stakeholders and the Life Cycle in CIVL1810? Sia is AskSia’s AI Engineering tutor — ask any CIVL1810 Construction Projects, Stakeholders and the Life Cycle question and get a clear, step-by-step explanation grounded in how CIVL1810 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
