HomeAgileBA Found.Practice questionsRequirements, User Stories and Modelling
AgileBA Found. · APMG · Requirements, User Stories and Modelling · Bank updated 2026-07-03

AgileBA Found. practice questions: Requirements, User Stories and Modelling

5 free questions from 35 on this area · answer and explanation for each · no sign-up

These 5 questions come from the Requirements, User Stories and Modelling section of our AgileBA Found. bank (35 questions on this area, which carries 25% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.

Start 6 free in study mode → All AgileBA Found. sample questions
1/5 · Requirements, User Stories and Modelling · easy
Which prioritisation technique does DSDM recommend for categorising requirements into Must Have, Should Have, Could Have and Won't Have This Time?
AMoSCoW
BThe Kano model
CRICE scoring
DWeighted Shortest Job First (WSJF)
Show answer & explanation
A is correct. MoSCoW prioritisation is central to DSDM's philosophy of fixing time and quality while flexing scope: requirements are labelled Must Have, Should Have, Could Have, or Won't Have This Time.
↗ the AgileBA Handbook (Agile Business Consortium, 2023 edition) + the APMG AgileBA Foundation syllabus — Requirements, User Stories and Modelling
2/5 · Requirements, User Stories and Modelling
Under the DSDM principle 'develop iteratively', how are requirements typically treated across the Evolutionary Development phase?
AThey are refined, elaborated and potentially adjusted increment by increment as feedback is gathered from the evolving solution
BThey are fixed in full detail during Foundations and must not change once Evolutionary Development begins
CThey are re-elicited entirely from scratch at the start of every timebox with no reference to prior work
DThey are frozen after the first working iteration to guarantee time predictability
Show answer & explanation
A is correct. 'Develop iteratively' recognises that requirements are rarely fully understood upfront; DSDM expects successive iterations to refine, elaborate and sometimes change requirement detail as feedback from working solutions is gathered and evaluated.
↗ the AgileBA Handbook (Agile Business Consortium, 2023 edition) + the APMG AgileBA Foundation syllabus — Requirements, User Stories and Modelling
3/5 · Requirements, User Stories and Modelling · easy
In the 'Card, Conversation, Confirmation' approach to writing user stories used in DSDM, what does the 'Card' represent?
AA test script prepared by the Solution Tester to prove the story has been implemented correctly.
BA short, written placeholder — often in the form 'As a <role>, I want <goal>, so that <benefit>' — that captures just enough detail to identify the story and prompt further discussion.
CA formal contract between the Business Sponsor and the Solution Development Team that fixes the scope of the story.
DA fully detailed functional specification that is agreed and signed off before any development work begins.
Show answer & explanation
B is correct. The 3 Cs describe how a user story matures: the Card is a brief placeholder, the Conversation elaborates detail collaboratively over time, and the Confirmation provides acceptance criteria that prove the story has been delivered as intended. The Card is deliberately minimal so detail is not locked in prematurely.
↗ the AgileBA Handbook (Agile Business Consortium, 2023 edition) + the APMG AgileBA Foundation syllabus — Requirements, User Stories and Modelling
4/5 · Requirements, User Stories and Modelling
Which statement best reflects the intended use of modelling techniques (for example process models or data models) in DSDM's approach to incremental delivery?
AModels replace the Prioritised Requirements List as the single source of scope and priority.
BModels must be finalised in full detail before Foundations closes so that no further modelling is needed during Evolutionary Development.
CModels are used as a lightweight way to explore, visualise and communicate requirements and options with stakeholders, evolving as understanding grows rather than being produced once and frozen.
DModelling is the sole responsibility of the Solution Tester and is not used during requirements discussions.
Show answer & explanation
C is correct. In DSDM, models (process flows, data models, prototypes, etc.) are communication and exploration tools that help stakeholders build a shared understanding of requirements incrementally. They evolve alongside the solution rather than being produced as a single, exhaustive artefact up front.
↗ the AgileBA Handbook (Agile Business Consortium, 2023 edition) + the APMG AgileBA Foundation syllabus — Requirements, User Stories and Modelling
5/5 · Requirements, User Stories and Modelling · hard
At the end of Foundations, the Prioritised Requirements List shows that 'Must Have' requirements are estimated to consume around 85% of the total development effort, with almost none allocated to 'Won't Have This Time'. Applying DSDM guidance on healthy prioritisation, what should most concern the Business Analyst about this distribution?
AThe main concern should be that too few requirements have been classified as 'Should Have', since DSDM requires 'Should Have' to always be the largest single category on any project.
BThe prioritisation is acceptable as it stands, because DSDM expects that, by the end of the project, all requirements will eventually be reclassified as 'Must Have'.
CNothing should concern the Business Analyst, since DSDM gives no guidance at all on the proportion of effort that should sit in each MoSCoW category.
DThe very high proportion of Must Haves leaves little room for lower-priority requirements to act as contingency, increasing the risk that scope cannot be flexed to protect the delivery timescale if estimates prove optimistic.
Show answer & explanation
D is correct. A core DSDM idea is fixing time, cost and quality while flexing scope, which only works if enough lower-priority requirements exist to be dropped or deferred under pressure. A Prioritised Requirements List dominated by Must Haves, with almost nothing left in reserve, removes this flexibility and puts the project's fixed delivery date at risk.
↗ the AgileBA Handbook (Agile Business Consortium / APMG) — Requirements, User Stories and Modelling
Practise all 35 Requirements, User Stories and Modelling questions - start free → See the whole AgileBA Found. bank

Other AgileBA Found. areas

The same kind of free sample for every other section of the AgileBA Found. bank:

Agile Fundamentals and the Agile BA Role35 qPrioritization and Timeboxing25 qRoles, Responsibilities and Stakeholders30 qAgile Business Case, Estimating and Benefits25 q

Study Requirements, User Stories and Modelling with instant feedback

6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.

Create your free account →
Read next
ECBA vs CCBA vs CBAP: Which IIBA Certification Fits Your Experience Level? (2026) ECBA, CCBA or CBAP? The eligibility gate that picks for you, what the 2026 ECBA rewrite changed, and each credential's three-year cost, verified against IIBA. PMI-PBA vs CBAP: The Business Analysis Certification Decision, Settled with Data PMI-PBA ($405-555, 36 months of experience) vs CBAP ($495-650 all-in, 7,500 hours plus references): eligibility, exam mechanics, three-year cost, salary data.
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by APMG. AgileBA Found. and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official APMG materials (as of August 2026); always confirm current details with the vendor before booking.