← QCE Digital Solutions Unit 3

Choosing a development method for a user profile

Choosing the approach by weighing how clearly users state requirements, how involved they can be and how often needs change: agile if engaged, waterfall if stable.

Part of: QCE Digital Solutions Unit 3 — Interactions Between Users, Data and Digital Systems — Module 128

Understanding Choosing a development method for a user profile in QCE Digital Solutions Unit 3

What it does: The justification names user involvement and changing needs, so it supports choosing agile. Fixed requirements and low involvement are the reasons given, which supports waterfall. Stable, clearly stated requirements are the key sign for waterfall. There is little need to revisit earlier stages. When users struggle to state requirements, early working versions help them react and refine. Waterfall needs clear requirements at the start. Engaged users with unclear or shifting needs match agile, where each iteration is reviewed and improved.

Common mistakes: Waterfall suits stable requirements. The condition should be IF requirements = stable, otherwise waterfall would be chosen for changing needs. Engaged users can give regular feedback, which suits agile. Line 2 should be method ← agile.

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 Choosing a development method for a user profile to a class →

This module's key terms are also in a printable crossword (Modules 128–176) and word search (Modules 15–176).

Take this worksheet further — free with Cloodit

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

Learning
Duo
A school club's committee meets weekly, loves giving feedback and keeps changing what the app should do. Which development method fits best?
Agile, because engaged users can review each iterationWaterfall, because all the steps are planned up front
Matches
Choose waterfall because the users are keen to give feedback every week and their needs keep changing
↓
This picks waterfall even though engaged users and changing needs point to agile. The method does not match the profile.
Applying
Meanings
Term
development method
Meaning
Choosing the approach by weighing how clearly users state requirements, how involved they can be and how often needs change: agile if engaged, waterfall if stable.
Practice
IF involvement = "high" AND change = "often" THEN
Testing
Gaps
IF usersEngaged THEN method ← ""
Check Answer
Spots
1IF requirements = changing
2 method ← waterfall

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

The 'Dolphin' badge — Reef Streak, 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. A school club's committee meets weekly, loves giving feedback and keeps changing what the app should do. Which development method fits best?
A. Agile, because engaged users can review each iteration ✓
B. Waterfall, because all the steps are planned up front
Engaged users who can give frequent feedback and whose needs keep changing suit agile. Each sprint gets reviewed and the next one adjusts.
2. A council gives a fixed, signed-off list of requirements for a permit form and says it will not change. Which method suits this user profile?
A. Agile, because every project should use sprints
B. Waterfall, because stable requirements can be planned once ✓
Stable, clearly stated requirements are the key sign for waterfall. There is little need to revisit earlier stages.
3. Which user profile is a strong reason to choose agile?
A. Users can join regular reviews and their needs often change ✓
B. Users are unavailable and requirements are fixed in writing
Agile relies on ongoing user involvement and copes well with changing needs. Unavailable users with fixed requirements point to waterfall.
4. Users say, 'We will know what we want when we see it.' Which method is the better choice?
A. Waterfall, because it gathers all requirements at the start
B. Agile, because the users can't state requirements clearly yet ✓
When users struggle to state requirements, early working versions help them react and refine. Waterfall needs clear requirements at the start.
5. Which statement is the best justification for choosing a development method?
A. It links the choice to the users' availability and how often needs change ✓
B. It says the method is popular with developers
A justification must refer to the user profile: how clearly they state requirements, how involved they can be and how stable their needs are.

Match the Pairs

Users unsure what they want, available weekly, needs keep changing → Agile suits this profile because frequent user feedback in short sprints can shape changing requirements
Users give a full, signed-off list of requirements, rarely available, needs fixed → Waterfall suits this profile because stable requirements can be planned once and built in sequence
Justify the choice by linking the method to the user profile: how clear, how involved, how often changing → Agile chosen: the club manager can test each sprint and her needs change often
A justification for waterfall points to stable requirements and limited user availability → Waterfall chosen: the council fixed all requirements in its tender and cannot attend meetings
Choose waterfall because the users are keen to give feedback every week and their needs keep changing → This picks waterfall even though engaged users and changing needs point to agile. The method does not match the profile.
Choose agile because the users are only available once and have given a final, fixed requirements list → This picks agile even though stable requirements and low user involvement point to waterfall. The method does not match the profile.

Key Term

development method
Choosing the approach by weighing how clearly users state requirements, how involved they can be and how often needs change: agile if engaged, waterfall if stable.

Fill in the Blanks

1. usersEngaged ← TRUE IF usersEngaged THEN method ← "agile"
Hint: Type the development method that suits users who are actively involved and keep giving feedback.
2. reqsStable ← TRUE IF reqsStable THEN method ← "waterfall"
Hint: Type the development method that suits requirements that are clear and will not change.
3. needsChange ← "often" IF needsChange = "often" THEN method ← "agile"
Hint: Type the variable set on the first line that records how often user needs change.
4. IF usersEngaged AND needsChange THEN method ← "agile" ENDIF
Hint: Type the logical keyword that requires both conditions to be true.
5. IF reqsStable THEN method ← "waterfall" ELSE method ← "agile" ENDIF
Hint: Type the keyword that gives the alternative method when the requirements are not stable.

Spot the Error

Question 1
A IF requirements = changing
B method ← waterfall
C ELSE method ← agile
Line A — Waterfall suits stable requirements. The condition should be IF requirements = stable, otherwise waterfall would be chosen for changing needs.
Question 2
A IF users = engaged
B method ← waterfall
C ELSE method ← waterfall
Line B — Engaged users can give regular feedback, which suits agile. Line 2 should be method ← agile.
Question 3
A client ← available weekly
B needs ← changing
C method ← waterfall
Line C — A client who is available weekly and has changing needs suits agile. Line 3 should be method ← agile.
Question 4
A requirements ← fixed
B users ← unavailable
C changes ← rare
D method ← agile
Line D — Fixed requirements, unavailable users and rare changes all point to waterfall. Line 4 should be method ← waterfall.
Question 5
A users ← engaged
B method ← agile
C reason ← no feedback needed
Line C — The justification must match the choice. Agile is chosen because engaged users give feedback each sprint, so the reason should be reason ← feedback each sprint.

Student with a class code? Join your class →