Choosing a development method for a user profile
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. A school club's committee meets weekly, loves giving feedback and keeps changing what the app should do. Which development method fits best?
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?
3. Which user profile is a strong reason to choose agile?
4. Users say, 'We will know what we want when we see it.' Which method is the better choice?
5. Which statement is the best justification for choosing a development method?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Users unsure what they want, available weekly, needs keep changing | AThis picks agile even though stable requirements and low user involvement point to waterfall. The method does not match the profile. | |
| 2Users give a full, signed-off list of requirements, rarely available, needs fixed | BThis picks waterfall even though engaged users and changing needs point to agile. The method does not match the profile. | |
| 3Justify the choice by linking the method to the user profile: how clear, how involved, how often changing | CWaterfall suits this profile because stable requirements can be planned once and built in sequence | |
| 4A justification for waterfall points to stable requirements and limited user availability | DWaterfall chosen: the council fixed all requirements in its tender and cannot attend meetings | |
| 5Choose waterfall because the users are keen to give feedback every week and their needs keep changing | EAgile suits this profile because frequent user feedback in short sprints can shape changing requirements | |
| 6Choose agile because the users are only available once and have given a final, fixed requirements list | FAgile chosen: the club manager can test each sprint and her needs change often |
C
Definitions
development method
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
usersEngaged ← TRUE
IF usersEngaged THEN method ← "_____"
2.
reqsStable ← TRUE
IF reqsStable THEN method ← "_________"
3.
needsChange ← "often"
IF ___________ = "often" THEN
method ← "agile"
4.
IF usersEngaged ___ needsChange THEN
method ← "agile"
ENDIF
5.
IF reqsStable THEN method ← "waterfall"
____ method ← "agile"
ENDIF
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
IF requirements = changing
B
method ← waterfall
C
ELSE method ← agile
Question 2
A
IF users = engaged
B
method ← waterfall
C
ELSE method ← waterfall
Question 3
A
client ← available weekly
B
needs ← changing
C
method ← waterfall
Question 4
A
requirements ← fixed
B
users ← unavailable
C
changes ← rare
D
method ← agile
Question 5
A
users ← engaged
B
method ← agile
C
reason ← no feedback needed
Answer Key
Choosing a development method for a user profile
Section A: Quick Questions
Q1
A — Agile, because engaged users can review each iteration
Q2
B — Waterfall, because stable requirements can be planned once
Q3
A — Users can join regular reviews and their needs often change
Q4
B — Agile, because the users can't state requirements clearly yet
Q5
A — It links the choice to the users' availability and how often needs change
Section B: Match the Pairs
Q1
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
Q2
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
Q3
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
Q4
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
Q5
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.
Q6
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.
Section C: Definitions
Q1
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.Section D: Fill in the Blanks
Q1
usersEngaged ← TRUE
IF usersEngaged THEN method ← "agile"Q2
reqsStable ← TRUE
IF reqsStable THEN method ← "waterfall"Q3
needsChange ← "often"
IF needsChange = "often" THEN
method ← "agile"Q4
IF usersEngaged AND needsChange THEN
method ← "agile"
ENDIFQ5
IF reqsStable THEN method ← "waterfall"
ELSE method ← "agile"
ENDIFSection E: Spot the Error
Q1
A — Waterfall suits stable requirements. The condition should be IF requirements = stable, otherwise waterfall would be chosen for changing needs.
Q2
B — Engaged users can give regular feedback, which suits agile. Line 2 should be method ← agile.
Q3
C — A client who is available weekly and has changing needs suits agile. Line 3 should be method ← agile.
Q4
D — Fixed requirements, unavailable users and rare changes all point to waterfall. Line 4 should be method ← waterfall.
Q5
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.