Prioritising requirements

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A school canteen app must let students place an order. Which priority is this?

A Must-have

B Nice-to-have

2. Which statement about must-have requirements is correct?

A The solution fails without them, so they are built first

B They can be dropped first if time runs short

3. A study planner app could let users pick a dark mode theme. Which priority fits best?

A Must-have

B Nice-to-have

4. Which describes a should-have requirement?

A Essential, because the solution cannot work without it

B Important and adds a lot of value, but the solution still works without it

5. Your team has two weeks left and the budget is almost gone. What should you do?

A Finish the must-haves and drop some nice-to-haves

B Add every nice-to-have and leave a must-have unfinished

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1Must-have: students can log in securely		ALabelling every requirement as must-have means no real prioritising or trade-offs happen when time or budget is limited
2Nice-to-have: dark mode theme		BBudget cut: drop 'nice-to-have' badges to finish 'must-have' login
3Should-have requirements are important and add real value, but the solution can still work without them for now		CShould-have: send a reminder before homework is due
4A trade-off means giving up one requirement to keep within limited time or budget so higher priorities are finished		DA nice-to-have feature (mascot) is ranked above a must-have (saving data), so the most important need is built later
5Priority 1: animated mascot. Priority 2: saving user data		EAn extra feature that adds value but is dropped first if time or budget runs out
6Everything is a must-have, so nothing gets cut		FA requirement the solution cannot work without, so it is built first

Definitions

prioritising requirements

Fill in the Blanks

Complete each line of code by filling in the missing parts.

Users must log in to use the app: _________

Dark mode is a bonus feature: ____________

Feature: Email reminders Important but not vital: ___________

Budget is low, so we make __________

Rank: must-have > ___________ > nice-to-have

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A App: Canteen ordering

B Nice: Pay for an order

C Should: Save favourite meals

D Nice: Dark mode theme

Question 2

A Project: Quiz website

B Must: Students can log in

C Should: Show scores

D Must: Fun avatars

Question 3

A Order: Nice, Should, Must

B 1. Build all Must items

C 2. Then add Should items

D 3. Nice items only if time

Question 4

A Sprint 1: Must-have items

B Sprint 2: Should-have items

C Sprint 3: Must-have items

Question 5

A Time is short: trade-off

B Rank all requirements

C Drop Nice-to-have items first

D Drop Must-have items next

Answer Key

Prioritising requirements

Section A: Quick Questions

A — Must-have

A — The solution fails without them, so they are built first

B — Nice-to-have

B — Important and adds a lot of value, but the solution still works without it

A — Finish the must-haves and drop some nice-to-haves

Section B: Match the Pairs

Must-have: students can log in securely → A requirement the solution cannot work without, so it is built first

Nice-to-have: dark mode theme → An extra feature that adds value but is dropped first if time or budget runs out

Should-have requirements are important and add real value, but the solution can still work without them for now → Should-have: send a reminder before homework is due

A trade-off means giving up one requirement to keep within limited time or budget so higher priorities are finished → Budget cut: drop 'nice-to-have' badges to finish 'must-have' login

Priority 1: animated mascot. Priority 2: saving user data → A nice-to-have feature (mascot) is ranked above a must-have (saving data), so the most important need is built later

Everything is a must-have, so nothing gets cut → Labelling every requirement as must-have means no real prioritising or trade-offs happen when time or budget is limited

Section C: Definitions

prioritising requirements — Ranking requirements as must-have, should-have or nice-to-have so the most important needs are built first, and trade-offs are made when time or budget is limited.

Section D: Fill in the Blanks

Users must log in to use the app: must-have

Dark mode is a bonus feature: nice-to-have

Feature: Email reminders
Important but not vital: should-have

Budget is low, so we make trade-offs

Rank: must-have > should-have > nice-to-have

Section E: Spot the Error

B — The app cannot work without paying for an order, so it is a must-have. It should be 'Must: Pay for an order'.

D — Fun avatars are decoration and the quiz works without them, so they are a nice-to-have. It should be 'Nice: Fun avatars'.

A — The most important requirements are built first. The order should be Must, Should, Nice, not the reverse.

C — Must-have items are built in Sprint 1. The last sprint is for nice-to-have items, so it should read 'Sprint 3: Nice-to-have items'.

D — In a trade-off you protect the must-have items and cut the lowest priority items. It should be 'Protect Must-have items'.