← Years 9–10 Data & Information

Identifying project risks

Something that might go wrong and harm a project plan, such as a late deadline, a tool failing or a team member being absent. Risks are listed before they happen.

Part of: 9-10 Digital Technologies: Project management — Module 7

Understanding Identifying project risks in Years 9–10 Data & Information

What it does: Running out of time is a time risk, and writing it down early lets the team add extra days to the plan. The risk is recorded in week 1, before it has happened, which is the point of identifying project risks. Risks are listed before they happen so the team can prepare a response and avoid surprises. Data loss and device or tool failure are technical risks. Backing up files to a shared drive helps reduce them. Team risks involve people, such as absence, conflict or one person holding all the skills. A Wi-Fi outage is a technical risk. A good risk statement is specific. It says what might go wrong and what harm it could cause to the plan.

Common mistakes: A risk is something that might go wrong in the future. A laptop that already failed is a problem, not a risk. It should read 'Risk: Laptop may fail'. Risks must be listed before they happen so the team can plan for them. It should read 'Listed: before it happens'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Identifying project risks to a class →

This module's key terms are also in a printable crossword (Modules 83–132) and word search (Modules 6–132).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
Which of these is a project risk?
Our team leader might get sick the week before the deadlineOur team leader got sick last week and we are already behind
Matches
Risk: Our app crashed yesterday and we lost our work
↓
This describes a problem that has already happened, not a risk. A risk is something that might go wrong and is listed before it happens.
Applying
Meanings
Term
project risk
Meaning
Something that might go wrong and harm a project plan, such as a late deadline, a tool failing or a team member being absent. Risks are listed before they happen.
Practice
Project risks identified:
Testing
Gaps
Type:
Check Answer
Spots
1Risk: Laptop failed yesterday
2Type: technical

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Elephant' badge — OOP Heavyweight, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. Which of these is a project risk?
A. Our team leader got sick last week and we are already behind
B. Our team leader might get sick the week before the deadline ✓
A risk is something that MIGHT go wrong and is listed before it happens. Once it has happened it is no longer a risk, it is a problem to deal with.
2. When should a team identify project risks?
A. Only after something has gone wrong
B. Early in planning, before the problems happen ✓
Risks are listed before they happen so the team can prepare a response and avoid surprises.
3. Your group is building a game, and the laptop with all the files might break or be lost. What type of risk is this?
A. Technical risk ✓
B. Team risk
Data loss and device or tool failure are technical risks. Backing up files to a shared drive helps reduce them.
4. Which one is a time risk?
A. Testing might take longer than planned and we could miss the deadline ✓
B. The coding software might crash while we are working
Time risks are about tasks taking longer than expected or deadlines being missed. A crashing tool is a technical risk.
5. Which one is a team risk?
A. The only person who knows how to build the database might be absent ✓
B. The school Wi-Fi might go down during the upload
Team risks involve people, such as absence, conflict or one person holding all the skills. A Wi-Fi outage is a technical risk.

Match the Pairs

Risk: Teammate sick on due date → A team risk: a member being absent could leave a task unfinished
Risk: Laptop crashes, files lost → A technical risk: a tool failing or data being lost could stop the project
A time risk is something that could make the project run late, so it is listed before the deadline arrives → Risk: Testing may take longer than planned
A risk is something that might happen, so it is written down before it occurs rather than after → Risk log (week 1): Wi-Fi may drop during upload
Risk: Our app crashed yesterday and we lost our work → This describes a problem that has already happened, not a risk. A risk is something that might go wrong and is listed before it happens.
Risk: Nothing will go wrong with our project → This is not a risk because it names no specific thing that might go wrong. Teams need to identify time, technical or team risks.

Key Term

project risk
Something that might go wrong and harm a project plan, such as a late deadline, a tool failing or a team member being absent. Risks are listed before they happen.

Fill in the Blanks

1. Risk: Deadline is missed Type: time
Hint: Type the risk category for a problem with deadlines or running out of schedule.
2. Risk: Laptop crashes and files are lost Type: technical
Hint: Type the risk category for a tool or data failure.
3. Risk: Team member is away sick Type: team
Hint: Type the risk category for a problem involving the people in the group.
4. risks ← [] ADD "Wi-Fi outage" TO risks
Hint: Type the name of the list variable created on the first line.
5. Risk: Tool stops working Status: listed before it happens
Hint: Type the word that shows when a risk should be listed compared with when it happens.

Spot the Error

Question 1
A Risk: Laptop failed yesterday
B Type: technical
C Listed: before it happens
Line A — A risk is something that might go wrong in the future. A laptop that already failed is a problem, not a risk. It should read 'Risk: Laptop may fail'.
Question 2
A Risk: Deadline may be missed
B Type: time
C Cause: tasks take too long
D Listed: after it happens
Line D — Risks must be listed before they happen so the team can plan for them. It should read 'Listed: before it happens'.
Question 3
A Risk: Member may be absent
B Type: technical
C Listed: before it happens
Line B — A team member being absent is a team risk, not a technical risk. It should read 'Type: team'.
Question 4
A Project: School app
B Risk: Wi-Fi may drop out
C Type: time
Line C — Wi-Fi dropping out is a technical risk because it is about equipment or tools failing. It should read 'Type: technical'.
Question 5
A Risk: Software may crash
B Cause: old school computer
C Type: team
Line C — A software crash caused by an old computer is a technical risk, not a team risk. It should read 'Type: technical'.

Student with a class code? Join your class →