Question bank
AgileBA® Foundation
40 AgileBA® Foundation questions with the correct answer and a written explanation, organised across 5 exam domains.
- 40 questions
- 5 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Communication and Modelling
8 questions in this domain
- Question 1Single Choice
What is the standard format for expressing a User Story in Agile?
- AAs a [user role], I want [goal] so that [reason]Correct answer
- BGiven [context], When [event], Then [outcome]
- CTitle, Description, Acceptance Criteria, Priority
- DActor, Precondition, Main Flow, Postcondition
Why this is the answer
The standard user story format is 'As a [user role], I want [goal] so that [reason].' It is a placeholder for conversation and not a full specification. The other options describe other artefacts: Given-When-Then is for Gherkin, the third is a generic story card format, and the fourth is a use case structure.
- Question 2Multiple Select
Which of the following are considered visual communication techniques in AgileBA? (Select two)
- AWireframesCorrect answer
- BMind MapsCorrect answer
- CProduct Backlog
- DBurn-down Chart
Why this is the answer
Wireframes and mind maps are explicitly mentioned as visual communication techniques (section 5.2). The product backlog is a list, not a visual artefact. Burn-down charts are reporting metrics (section 5.3), not modelling techniques.
- Question 3Interactive
Refer to the code block. Which Agile modelling technique is being demonstrated?
- AUser StoryCorrect answer
- BUse Case
- CBusiness Process Model
- DPersona
Why this is the answer
The code block shows a user story in the standard 'As a...I want...So that...' format. Use cases are more structured and detailed. BPM shows flowcharts, and personas are user profiles.
- Question 4Single Choice
What does the term 'velocity' measure in Agile reporting?
- AThe amount of work (in story points) a team completes in one iterationCorrect answer
- BThe number of hours a team works per day
- CThe time taken from story creation to delivery
- DThe percentage of requirements delivered on time
Why this is the answer
Velocity is a team-specific metric that measures the amount of work (story points) completed in a single iteration. It is used for forecasting, not productivity comparison. The other options confuse velocity with cycle time, effort, or traditional metrics.
- Question 5Multiple Select
Which two roles are primarily responsible for effective handover and knowledge transfer in AgileBA?
- ABusiness AnalystCorrect answer
- BProduct OwnerCorrect answer
- CProject Manager
- DEnd User
Why this is the answer
The Business Analyst facilitates workshops and creates artefacts, while the Product Owner owns the backlog and provides business context. The Project Manager is not an AgileBA role. End users participate in elicitation but are not primarily responsible for handover.
- Question 6Interactive
The code block shows a simple representation of an artefact. What Agile visual communication technique does it represent?
- AWireframeCorrect answer
- BProcess Flow
- CMind Map
- DBurn-up Chart
Why this is the answer
The code block uses ASCII art to represent a low-fidelity wireframe with a header, navigation, and content areas. Wireframes focus on layout and structure without visual design. Process flows use arrows and decisions; mind maps use radial branches; burn-up charts are graphs.
- Question 7Single Choice
What is the primary purpose of a story map in Agile?
- AVisualise the full user journey from left to right and prioritise stories top to bottomCorrect answer
- BReplace the product backlog with a single horizontal timeline
- CDocument system architecture in a sequential diagram
- DProvide a detailed specification for each user story
Why this is the answer
A story map shows user activities (backbone) horizontally and detailed stories vertically. It helps identify MVPs and plan releases. It does not replace the backlog; it gives context. Architecture documentation is separate. It is not a detailed spec.
- Question 8Multiple Select
Which two chart types make scope changes visible to stakeholders?
- ABurn-up ChartCorrect answer
- BBurn-down Chart
- CCumulative Flow Diagram
- DRelease Burn-up ChartCorrect answer
Why this is the answer
Burn-up charts (including release burn-up) have two lines: total scope and completed work. When scope increases, the total line rises, making changes visible. Burn-down charts only show remaining work and can hide scope creep. Cumulative flow diagrams show work in progress distribution but not directly scope changes.
Elicitation and Collaboration
8 questions in this domain
- Question 9Single Choice
According to the Power-Interest Grid, what is the appropriate engagement strategy for a stakeholder with high power and low interest?
- AManage Closely
- BKeep SatisfiedCorrect answer
- CKeep Informed
- DMonitor
Why this is the answer
According to the Power-Interest Grid, a stakeholder with high power and low interest should be kept satisfied. This means providing sufficient attention to meet their needs without overwhelming them with excessive detail. Over-engaging (Manage Closely) would waste their time, while under-engaging (Keep Informed or Monitor) risks dissatisfaction.
- Question 10Multiple Select
Which of the following are correct statements about workshops as an elicitation technique? (Select two.)
- AWorkshops are best suited for one-on-one discussions on sensitive topics.
- BA neutral facilitator is essential to manage group dynamics and keep the session on track.Correct answer
- CWorkshops are typically timeboxed to ensure focused and efficient collaboration.Correct answer
- DWorkshops always produce a prioritized product backlog as the primary output.
Why this is the answer
Workshops require a neutral facilitator to guide discussions and ensure all voices are heard. They are also timeboxed to align with agile principles. Workshops are not ideal for sensitive one-on-one topics (interviews are better) and their outputs can vary (e.g., story maps, decisions) – not always a prioritized backlog.
- Question 11Interactive
Examine the acceptance criteria code block below. What does the 'Given' clause represent in this Given-When-Then scenario?
- AIt defines the expected outcome of the scenario.
- BIt defines the initial context or preconditions.Correct answer
- CIt defines the user action that triggers the outcome.
- DIt defines the user role associated with the story.
Why this is the answer
In the Given-When-Then format, the 'Given' clause sets the preconditions or initial state necessary for the scenario. The 'When' clause describes the action, and the 'Then' clause specifies the expected result. Understanding this structure is fundamental to writing testable acceptance criteria.
- Question 12Single Choice
What is the primary purpose of an Information Radiator in an agile project?
- ATo communicate project status exclusively to the project manager.
- BTo passively broadcast key project information to the whole team and stakeholders.Correct answer
- CTo generate a large quantity of creative ideas during a workshop.
- DTo document detailed acceptance criteria for user stories.
Why this is the answer
An information radiator is a visual display (e.g., Kanban board, burndown chart) that makes project information visible to everyone. It supports transparency and collaboration by allowing team members and stakeholders to self-serve status updates, unlike traditional reports that are distributed to a limited audience.
- Question 13Multiple Select
Which two statements correctly describe the RACI matrix in an agile context? (Select two.)
- AThe Business Analyst is typically Accountable for stakeholder satisfaction.
- BOnly one person can be designated as Accountable for a given task or decision.Correct answer
- C'Consulted' indicates two-way communication where input is sought before decisions.Correct answer
- D'Informed' means the stakeholder provides input before a decision is made.
Why this is the answer
In RACI, Accountability is singular – only one person is Accountable for each activity. 'Consulted' involves two-way communication; those consulted provide input before decisions. The BA is typically Responsible for facilitating engagement, but the Product Owner is Accountable for stakeholder satisfaction. 'Informed' is one-way notification after decisions.
- Question 14Interactive
The code block contains a list of interview questions. Which number corresponds to an open-ended question?
- AQuestion 1
- BQuestion 2Correct answer
- CQuestion 3
- DQuestion 4
Why this is the answer
Open-ended questions encourage detailed responses and cannot be answered with a simple 'yes' or 'no'. Question 2 ('How does the current process affect your team's productivity?') invites elaboration. Questions 1, 3, and 4 are closed-ended as they expect short, factual answers or binary responses.
- Question 15Single Choice
In the INVEST acronym for user stories, what does the letter 'N' represent?
- ANecessary
- BNegotiableCorrect answer
- CNon-functional
- DNarrow
Why this is the answer
The 'N' in INVEST stands for Negotiable. This means that a user story is not a fixed contract; it is an invitation for conversation and can be modified through discussion between the team and stakeholders before it is committed to a sprint. The other options are common distractors.
- Question 16Multiple Select
Which two statements accurately describe characteristics of a facilitated workshop? (Select two.)
- AIt is typically conducted with a single stakeholder to maintain focus.
- BThe facilitator remains neutral and does not contribute content.Correct answer
- CA scribe or note-taker is often present to capture outputs.Correct answer
- DThe agenda must be followed strictly with no room for adaptation.
Why this is the answer
In a facilitated workshop, the facilitator is neutral, ensuring balanced participation. A scribe captures decisions and action items. Workshops involve multiple stakeholders, not just one, and while an agenda is prepared, some flexibility is allowed to explore valuable discussion points.
Requirements Lifecycle Management
8 questions in this domain
- Question 17Single Choice
What is the primary purpose of requirements traceability in Agile Business Analysis?
- ATo create a comprehensive document for regulatory audits only
- BTo establish and maintain documented relationships between requirements and their origins, implementation, and verification artifactsCorrect answer
- CTo replace the need for face-to-face communication with stakeholders
- DTo track the number of requirements changes during a sprint
Why this is the answer
Requirements traceability establishes bidirectional links between requirements and their sources, implementation, and tests. It enables change impact analysis, transparency, and value delivery, not just documentation or auditing.
- Question 18Multiple Select
Which of the following are key concepts of requirements traceability in AgileBA? (Select two)
- ABidirectional traceabilityCorrect answer
- BChange impact analysisCorrect answer
- CFormal Change Control Board approval
- DConfiguration management of hardware assets
Why this is the answer
Bidirectional traceability ensures forward and backward links, while change impact analysis uses these links to assess effects of modifications. Formal CCB and hardware config management are not core traceability concepts.
- Question 19Interactive
Review the JSON snippet below representing a simple traceability matrix. How does the 'tests' field support validation?
- AIt lists all test cases that have been executed, regardless of pass/fail status
- BIt links each requirement to its corresponding test cases, enabling verification that every requirement is testedCorrect answer
- CIt stores the actual test scripts and automation code for each requirement
- DIt shows which stakeholder approved the testing scope
Why this is the answer
The 'tests' field in a traceability matrix links a requirement to its test artifacts. This ensures that every requirement has a corresponding verification mechanism, supporting validation and coverage analysis.
- Question 20Single Choice
How does agile change management differ from traditional change management?
- AChanges are formally approved by a Change Control Board before any analysis
- BChange is embraced as a continuous flow, evaluated collaboratively, and prioritised in the backlogCorrect answer
- CChanges are strictly forbidden once a sprint begins to protect the plan
- DAll changes must be documented with a formal change request number and stored separately
Why this is the answer
Agile change management treats change as natural and ongoing. The BA facilitates impact analysis, and the Product Owner prioritises changes in the backlog. Unlike traditional, it avoids rigid formalities and focuses on collaboration and value.
- Question 21Multiple Select
Which of the following are key activities of a Business Analyst during agile change management? (Select two)
- AConducting a rapid impact analysis to identify affected stories and effortCorrect answer
- BMaking the final decision on whether to include the change in the sprint
- CDocumenting the change rationale in an Impact Analysis LogCorrect answer
- DEscalating the change directly to the programme board for approval
Why this is the answer
The BA performs impact analysis and documents it (e.g., in an Impact Analysis Log). The Product Owner makes final prioritisation decisions, not the BA. Escalation to a board is a traditional practice.
- Question 22Interactive
The snippet shows a prioritisation log using MoSCoW categories. Based on the content, which requirement is critical for solution viability?
- AREQ-201 - User authenticationCorrect answer
- BREQ-202 - Profile picture upload
- CREQ-203 - Dark mode toggle
- DREQ-204 - Social media sharing
Why this is the answer
User authentication is classified as 'Must have.' Without it, the solution is unusable. The other features are 'Should have' or 'Could have' and are not critical for viability.
- Question 23Single Choice
Which MoSCoW category is assigned to requirements that are important but can be omitted if time runs out, often with an acceptable workaround?
- AMust have
- BShould haveCorrect answer
- CCould have
- DWon't have this time
Why this is the answer
Should have requirements are important and add significant value, but if necessary, a workaround can be accepted. They are not mandatory like Must haves, but more valuable than Could haves.
- Question 24Multiple Select
Which of the following correctly describe Kano model attributes? (Select two)
- ABasic attributes are taken for granted and cause dissatisfaction when missingCorrect answer
- BPerformance attributes directly correlate with satisfaction – more is betterCorrect answer
- CExcitement attributes cause dissatisfaction when present
- DBasic attributes are the same as 'Must have' in MoSCoW in every situation
Why this is the answer
Basic attributes are expected; their absence causes dissatisfaction. Performance attributes increase satisfaction linearly. Excitement attributes delight when present but do not cause dissatisfaction if absent. Basic attributes often map to Must haves but not always identically.
Strategy and Planning
8 questions in this domain
- Question 25Single Choice
Who is accountable for owning the business case in AgileBA?
- ASenior Responsible OwnerCorrect answer
- BBusiness Analyst
- CProject Manager
- DSponsor
Why this is the answer
The Senior Responsible Owner (SRO) is accountable for the business case. The BA facilitates its development.
- Question 26Multiple Select
Which two statements correctly describe the AgileBA business case?
- AIt is a living artefact that evolves iteratively.Correct answer
- BIt is created once at project initiation and never changed.
- CIt is reviewed at formal decision gates to justify continuation.Correct answer
- DIt is owned by the Business Analyst who develops it.
Why this is the answer
The business case is a living artefact, reviewed at gates. The SRO owns it, not the BA.
- Question 27Interactive
Refer to the code block. What should the BA do when the assumption about market share changes?
- AUpdate the business case with revised assumptions.Correct answer
- BIgnore the change and proceed with the original plan.
- CTerminate the project immediately.
- DAsk the Project Manager to decide alone.
Why this is the answer
In AgileBA, the business case is updated iteratively when assumptions change. The BA facilitates this update.
- Question 28Single Choice
In MoSCoW prioritization, what is the maximum effort allowed for Must-have requirements?
- A60%Correct answer
- B40%
- C80%
- D50%
Why this is the answer
AgileBA states that Must-haves should not exceed 60% of total effort to allow flexibility for Shoulds and Coulds.
- Question 29Multiple Select
Which two techniques are used for prioritization in AgileBA?
- AMoSCoWCorrect answer
- BKano ModelCorrect answer
- CWaterfall Gantt chart
- DCritical Path Method
Why this is the answer
MoSCoW and Kano Model are AgileBA prioritization techniques. Gantt and CPM are traditional project management tools.
- Question 30Interactive
Refer to the code block. Which planning level is being described?
- APortfolio planning
- BRelease planningCorrect answer
- CIteration planning
- DDaily stand-up
Why this is the answer
The description of a 2–6 month timeframe with feature prioritization using MoSCoW indicates release planning.
- Question 31Single Choice
In AgileBA, what is the purpose of rolling wave planning?
- ATo plan near-term items in detail and future items at a high level.Correct answer
- BTo create a fixed, detailed plan for the entire project at the start.
- CTo eliminate the need for iteration planning.
- DTo ensure all levels are planned with equal detail.
Why this is the answer
Rolling wave planning avoids wasted effort on speculative detail and adapts as new information emerges.
- Question 32Multiple Select
Which two statements about story point estimation in AgileBA are true?
- AStory points are a relative measure of effort.Correct answer
- BStory points can be converted to hours for better accuracy.
- CThe team collectively owns the estimates.Correct answer
- DThe Business Analyst is accountable for the accuracy of estimates.
Why this is the answer
Story points are relative and team-owned. Conversion to hours is discouraged in AgileBA; the BA facilitates, not owns.
The AgileBA® Mindset and Principles
8 questions in this domain
- Question 33Single Choice
Which Agile Manifesto value is most directly applied when a business analyst chooses to hold a face-to-face workshop instead of distributing a specification document?
- AIndividuals and interactions over processes and toolsCorrect answer
- BWorking software over comprehensive documentation
- CCustomer collaboration over contract negotiation
- DResponding to change over following a plan
Why this is the answer
The value 'Individuals and interactions over processes and tools' prioritises direct human communication over formal processes or tools like documents.
- Question 34Multiple Select
Which two of the following are responsibilities of the Business Analyst within the AgileBA® framework?
- AFacilitating requirements workshopsCorrect answer
- BPrioritising the product backlog
- CModelling business processesCorrect answer
- DControlling the project budget
Why this is the answer
The BA facilitates workshops and models processes. The Product Owner prioritises the backlog, and the Business Visionary controls the budget.
- Question 35Interactive
Read the following user story and acceptance criteria. Which Agile principle is NOT being followed?
- AEarly and continuous delivery of valuable software
- BWelcome changing requirements, even late in development
- CBusiness people and developers work together daily throughout the projectCorrect answer
- DSimplicity – the art of maximising the amount of work not done
Why this is the answer
The story was written in isolation without daily collaboration between business and developers, violating the principle of daily cooperation.
- Question 36Single Choice
In the AgileBA® framework, who is ultimately accountable for the project's return on investment?
- ABusiness Analyst
- BBusiness VisionaryCorrect answer
- CProject Manager
- DTechnical Coordinator
Why this is the answer
The Business Visionary is accountable for ROI and approves the Business Case, providing strategic direction.
- Question 37Multiple Select
Which two statements correctly describe the Agile Manifesto principle 'Welcome changing requirements, even late in development'?
- AChanges should be rejected if they occur after the design phase
- BThe business analyst should reprioritise the backlog to accommodate valuable changesCorrect answer
- CRequirements are expected to emerge as the team gains more insightCorrect answer
- DAll changes must be documented in a formal change request before being considered
Why this is the answer
Agile welcomes change by reprioritising the backlog and recognising that requirements emerge. Formal change requests are a traditional approach.
- Question 38Interactive
Examine the MoSCoW prioritisation of backlog items below. Which two items are correctly classified as 'Must have'?
- AUser login functionality (critical for security compliance)Correct answer
- BAdvanced search filter (nice-to-have convenience)
- CPayment processing (core business operation)Correct answer
- DColour theme customisation (delight feature)
Why this is the answer
Must have items are non-negotiable for the timebox. Login and payment are critical, while advanced search and colour themes are Could have or Won't have.
- Question 39Single Choice
Which statement best describes how requirements are elaborated in an agile business analysis context?
- AAll requirements are defined fully before the project starts
- BRequirements are detailed just-in-time as they are scheduled for developmentCorrect answer
- CRequirements are detailed only after the solution is deployed
- DRequirements are never written down, only verbally communicated
Why this is the answer
AgileBA uses just-in-time elaboration: requirements are detailed when they are about to be developed, avoiding waste from outdated documentation.
- Question 40Multiple Select
Which two of the following are phases in the AgileBA® lifecycle?
- APre-ProjectCorrect answer
- BIterative Development (Cycles)Correct answer
- CWaterfall Handover
- DPost-Implementation Review (PIR) Phase
Why this is the answer
The AgileBA lifecycle consists of Pre-Project, Iterative Development (Cycles), and Post-Project. Waterfall Handover is not an agile concept.
Frequently asked questions
Everything about the AgileBA® Foundation question bank and how to use it.