BCS BA Found. · BCS · Delivering the Requirements · Bank updated 2026-11-04
BCS BA Found. practice questions: Delivering the Requirements
5 free questions from 11 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Delivering the Requirements section of our BCS BA Found. bank (11 questions on this area, which carries 5% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 11 Delivering the Requirements questions and the full BCS BA Found. bank: $15 one-time.
1/5 · Delivering the Requirements · easy
Which delivery lifecycle approach requires each stage of development (such as requirements, design, build and test) to be completed and formally signed off before the next stage begins?
AThe linear (waterfall) approach
BThe iterative approach
CThe agile approach
DThe incremental approach
2/5 · Delivering the Requirements
A project sponsor states that the requirements are already fully understood and stable, insists that design must not start until requirements are formally agreed and signed off, and wants a single go-live date with maximum control over the final scope and budget. No particular concern is raised about how testing will be organised. Which delivery lifecycle approach best matches these requirements?
AThe linear (waterfall) approach
BAn incremental approach
CThe V-model
DAn iterative or agile approach
3/5 · Delivering the Requirements · hard
A business analyst is weighing up an iterative/agile approach against a linear (waterfall) approach for a project where the true business need is not yet fully understood at the outset. Which statement correctly describes a genuine trade-off between the two approaches?
AAn incremental approach offers the least control of any lifecycle approach because none of the requirements are defined until the final release
BThe V-model provides a faster overall pace of delivery than any other lifecycle approach because testing overlaps with development
CThe waterfall approach delivers working software at a faster pace than an iterative approach because no time is spent revisiting earlier decisions
DThe iterative/agile approach can achieve greater clarity of the real business need through early and frequent feedback, but typically gives less up-front control over the final overall scope, cost and timescale
4/5 · Delivering the Requirements · hard
During a MoSCoW prioritisation workshop, a stakeholder argues that any requirement placed in the 'Won't have this time' category has been permanently rejected and should be removed from all future consideration. Which response correctly reflects how this category is intended to be used?
A'Won't have this time' means the requirement is out of scope for the current delivery timebox but remains a legitimate candidate for a future release.
B'Won't have this time' is simply a lower-priority synonym for 'Could have', so the two categories can be merged without losing information.
CThe stakeholder is correct: once a requirement is placed in this category it is formally rejected and cannot be reconsidered later.
DThe category applies only to requirements that are technically infeasible with current technology, so feasible requirements cannot be placed there.
Answer: A. MoSCoW's fourth category is deliberately worded 'Won't have this time' - not simply 'Won't have' - to make clear that exclusion applies only to the current delivery timebox, leaving the requirement available for later re-prioritisation. Confusing this with permanent rejection, or collapsing it into 'Could have', is a documented misreading of the technique that the syllabus specifically guards against.
Source: the BCS Business Analysis Foundation syllabus - Delivering the Requirements
5/5 · Delivering the Requirements
An Agile development team is building the current increment from the product backlog. The business analyst is deciding where to spend the week. Which activity best reflects the analyst's contribution to the backlog at this point?
Aworking through the next items on the backlog to complete detailed technical designs for the team
Blooking ahead to future work packages and increments so new requirements are ready when the team needs them
Clocking the sequence of backlog items once the increment starts so that the team can work undisturbed
Dhanding responsibility for backlog changes to the developers because they understand the feasibility of each item
Answer: B. Technique 78 describes the analyst taking a step back from detailed development, looking ahead to future work packages and ensuring a constant stream of new requirements ready for the team. The backlog is constantly refined and maintained collaboratively, not locked or delegated.
Source: Paul, Cadle, Turner (eds), Business Analysis Techniques, 2nd ed., BCS, Technique 78: Product backlog, p. n/a
Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Investigating the Business Situation
Other BCS BA Found. areas
The same kind of free sample for every other section of the BCS BA Found. bank:
Practise BCS BA Found. with instant feedback
6 free questions in study mode · no card · full BCS BA Found. bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start BCS BA Foundation free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by BCS. BCS BA Found. and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official BCS materials (as of August 2026); always confirm current details with the vendor before booking.