The University of Manchester · FACULTY OF ENVIRONMENTAL SCIENCE

EART66001 Chap.1 Project Lifecycle and Scope

- one subject, every graph, every model, every mark
6 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 1 of 9 · EART66001

Project Lifecycle and Scope

Project Lifecycle and Scope turns an environmental concern into a bounded modelling project. The module treats modelling as part of a simulated research or consultancy lifecycle: define the problem, set the scope, plan the work, identify risks, acquire and inspect data, run scenarios, evaluate outputs and communicate recommendations.

A strong scope identifies the stakeholder, study area, environmental process, time horizon and decision indicator. It also states important exclusions. The aim expresses the overall purpose, while objectives create checkable products such as a baseline, controlled scenario comparison and uncertainty review. Changes remain legitimate when they are versioned and linked to the programme, risk register and model log.

The chapter therefore makes traceability a scientific control rather than an administrative extra.

Scope should be tested through counterexamples. Ask whether a proposed run answers the agreed question, whether a new dataset changes the boundary, and whether an attractive output belongs to an objective. These checks prevent software capability from determining project content.

A project may generate many maps and graphs, but the useful evidence set is the one that compares defined conditions for a named decision and receptor.

Programme and risk controls also shape scientific quality. Dependencies show when data review, baseline configuration and scenario analysis must occur. A risk entry should identify a possible event, consequence, owner and response rather than repeat a vague concern.

When an input or method changes, the record should show which later tasks, files and conclusions need review. This creates a recoverable project history and makes group handover possible without reconstructing decisions from folder dates.

Use two traceability directions. Work forward from each objective to a result and recommendation, then work backward from each claim to a logged scenario, model and source input.

Forward tracing exposes unused modelling; backward tracing exposes unsupported claims. Both are valuable before the technical note is drafted because they reveal whether the project needs another run, a narrower conclusion or simply clearer documentation.

In this chapter

What this chapter covers

  • 01

    Decision problem

  • 02

    Project boundary

  • 03

    Aim and objectives

  • 04

    Programme dependencies

  • 05

    Risk register

  • 06

    Evidence chain

Worked example · free

Rewrite a vague modelling request

Q [5 marks]. A client asks for a flood model and a map. Turn the request into a decision-ready scope. AskSia assigned these practice marks; they are not a University marking scheme.
The arrows move from a decision problem through scope, data, modelling and scenarios before limitations constrain the final advice.The arrows move from a decision problem through scope, data, modelling and scenarios before limitations constrain the final advice. ProblemScopeDataModelScenariosOutputsLimitsAdvice
The arrows move from a decision problem through scope, data, modelling and scenarios before limitations constrain the final advice.
  • 2Name the stakeholder, reach, receptors and event that define the boundary.
  • 2Define a baseline and intervention scenario with a common decision indicator.
  • 1State the principal model limitation and the decision the comparison can inform.
The finished scope asks whether a defined intervention changes a selected flood indicator at stated receptors under a common event, while acknowledging the model boundary. The weighting is an original practice aid, not a university marking scheme.
Sia tip — Write the comparison into the objective before choosing model settings.
Glossary

Key terms

Project scope
The defined boundary, outputs and decision that determine what work belongs in a project.
Objective
A checkable action that contributes evidence toward the project aim.
Risk register
A controlled record of project threats, consequences, owners and responses.
FAQ

Project Lifecycle and Scope FAQ

Why define scope before opening software?

Software can produce many outputs, but only a bounded question determines which inputs, scenarios and results matter. Scope prevents technically polished work from answering the wrong decision and gives the team a basis for selecting evidence.

How are aims and objectives different?

The aim states the overall project purpose. Objectives break that purpose into observable actions, such as checking data, configuring a baseline, comparing scenarios and evaluating uncertainty, so progress and evidence can be reviewed.

When is a project change acceptable?

A change is defensible when its reason, owner, version and consequences are recorded. Update affected tasks, risks, model files and conclusions rather than allowing new assumptions or scenarios to enter the project silently.

How can I test project traceability?

Trace each objective forward to a result and recommendation, then trace every important claim backward to its scenario, model file and input. The forward pass reveals work that never answers the question; the backward pass reveals conclusions without a reproducible evidence chain. Repair the missing link or narrow the claim before drafting the final note.

What makes a risk register useful?

A useful entry names a possible event, its project consequence, an owner, a response and a review point. Connect the response to programme dependencies and evidence creation. A list of vague concerns does not show how the team will protect modelling quality when data, time or coordination problems occur.

Study strategy

Assessment move

Start every topic by writing the environmental decision and the smallest model comparison that could inform it. Practise converting broad verbs such as investigate or assess into observable objectives with named outputs. Draw the lifecycle and trace each step into the next: scope determines data, data and process determine representation, the model creates scenario outputs, and uncertainty limits the recommendation.

Use a simple change log during practical work so you can distinguish a scientific revision from unrecorded drift. Rehearse project dependencies by asking what must exist before a task can start and what evidence demonstrates completion. When reviewing a case study, work backward from the recommendation to the output, scenario, model and objective.

A broken link is either a missing piece of evidence or a claim that needs narrowing. Before assessment, compare terminology across the project plan, risk register, model log, technical note and presentation. The same baseline and scenario labels should appear everywhere.

Do not treat planning documents as separate paperwork: they protect the consistency of the modelling argument and allow another person to reproduce the route from problem to advice.

Working through Project Lifecycle and Scope in EART66001? Sia is AskSia’s AI Environmental Science tutor — ask any EART66001 Project Lifecycle and Scope question and get a clear, step-by-step explanation grounded in how EART66001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 41 of your subjects at The University of Manchester, plus 1,000+ more Bibles across the AskSia library.
Sia - your EART66001 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works