20 Need Practice Questions & Answers

Every Need practice question from the ECBA Practice Test, with the correct answer and a short explanation.

1. A business analyst is preparing the first working session with a department that has never taken part in business analysis before. The invitation told them only the date and the room. What should the analyst do before the session?
- A.Circulate a draft set of requirements beforehand, so that the participants can approve them during the session
- B.Explain the purpose of the session and how the discussion will be run, so participants arrive ready to contribute✓ Answer
- C.Say nothing about the purpose beforehand, so that the participants' answers are not shaped by expectations
- D.Invite the sponsor to attend the session, so that any disagreement among the participants is settled at once
Preparing for elicitation includes preparing the stakeholders themselves, so they understand why the session is being held and how the chosen approach works. Participants who do not know the purpose contribute less and the session yields weaker information; withholding the purpose does not protect objectivity, it wastes the session.
Source: BABOK Guide — Prepare for Elicitation, preparing stakeholdersReport a problem with this question
2. An analyst must understand how a change in industry rules affects order handling. The detail sits in published rule sets and in the organisation's archived case files, not in anyone's day-to-day knowledge. Which kind of elicitation does this call for?
- A.Experimental elicitation, because the effect of the rules can be established only by a controlled trial
- B.Collaborative elicitation, because the answer depends on the experience and the judgement of the stakeholders
- C.Research elicitation, because the information is discovered by studying existing materials and records✓ Answer
- D.Collaborative elicitation, because a facilitated session must always precede any study of documents
Research elicitation covers information that is systematically discovered by studying materials and sources not directly held by the stakeholders involved in the change. Collaborative elicitation draws on stakeholder experience and judgement, and experimental elicitation produces information that cannot exist until a controlled test is run.
Source: BABOK Guide — Elicitation, types of elicitation (collaborative, research, experiments)Report a problem with this question
3. A warehouse team wants to know whether resequencing the picking route would cut handling time. Nobody has ever worked that way, and no records of such a route exist anywhere in the organisation. Which kind of elicitation fits?
- A.Collaborative elicitation, because experienced pickers can judge the effect from their own practice
- B.Collaborative elicitation, because a supervisor's estimate is enough when no records are available
- C.Research elicitation, because comparable handling times can be studied in the records already held
- D.Experimental elicitation, because the information appears only once a controlled trial has been carried out✓ Answer
Experiments are the elicitation type used when the information cannot be known without some form of controlled test, because it exists neither in stakeholders' experience nor in any record. Asking experienced staff or searching archives cannot produce information about a way of working that has never been tried.
Source: BABOK Guide — Elicitation, experiments as a type of elicitationReport a problem with this question
4. During an interview, an operations supervisor becomes guarded after the analyst repeatedly steers the conversation back to a prepared list of questions. What should the analyst do?
- A.Ask the supervisor's manager to join the remaining interviews so that the answers stay on the agreed topic
- B.Close the interview early and send the remaining questions in writing for the supervisor to answer
- C.Work through the prepared list to the end, so that the results stay comparable with the other interviews
- D.Listen to the concern the supervisor is raising, confirm it has been understood, then return to the list✓ Answer
Listening and building rapport are underlying competencies that make elicitation work: when a stakeholder raises something outside the script, it is usually information the analyst came for. Pressing on with the agenda protects the format at the cost of the content, and bringing in a manager to keep answers on topic damages the trust the interview depends on.
Source: BABOK Guide — Underlying Competencies, listening and trustworthiness in elicitationReport a problem with this question
5. An analyst has been given one hour with a group of stakeholders and a broad topic: problems with customer onboarding. What should the analyst settle first when preparing for the session?
- A.The scope of the session and the outcome expected from it, which then guide how the session is run✓ Answer
- B.The stakeholders whose answers will carry most weight, so that conflicting input can be set aside
- C.The requirements the session is expected to produce, drafted so the group can react to them
- D.The logistics of the session, since the room and the recording method shape what can actually be covered
Preparation begins by defining the scope of the elicitation activity and the outcome expected from it; those decisions then drive the choice of approach, the logistics and the supporting material. Logistics settled before scope tends to constrain the session, and drafting the requirements in advance replaces elicitation with confirmation of the analyst's own assumptions.
Source: BABOK Guide — Prepare for Elicitation, defining scope and expected outcomesReport a problem with this question
6. A team member has written up the notes from a workshop about how refunds are handled today. The notes have not yet been checked with anyone. What should happen next?
- A.Send the write-up to the sponsor for approval so that the analysis can continue without delay
- B.Pass the write-up to the delivery team, which will raise anything that looks inconsistent to it
- C.Review the write-up with the participants and check it against the records that it describes✓ Answer
- D.Treat the write-up as settled, since the participants were the ones who supplied the content
Confirming elicitation results has two elements: comparing the results against the source information, and comparing them against other elicitation results. It is a lightweight accuracy check done with the participants, and it is neither sign-off by the sponsor nor a job that can be handed to the delivery team.
Source: BABOK Guide — Confirm Elicitation Results, comparison against source informationReport a problem with this question
7. An analyst has compared session notes against the source documents and against the results of a second session, and the participants agree the notes are accurate. What has been achieved at this point?
- A.The requirements have been approved, since the participants who supplied them accept the written form
- B.The requirements elicited are confirmed accurate and consistent, but not approved or baselined✓ Answer
- C.The requirements have been verified as complete, since two separate sources produced the same content
- D.The requirements have been validated, since stakeholders agree that the notes reflect what they need
Confirming elicitation results establishes only that the captured information is accurate and consistent with its sources and with other results. Validation asks whether the requirements deliver the value the business needs, verification examines the quality of the artefact itself, and approval is a separate decision that an entry-level practitioner does not make.
Source: BABOK Guide — Confirm Elicitation Results compared with Verify, Validate and Approve RequirementsReport a problem with this question
8. Two sessions with different teams produced contradictory descriptions of the same step in the returns process. Both sets of notes are now in the analyst's hands. What should the analyst do?
- A.Carry both accounts forward and let the delivery team decide which one to build the process against
- B.Compare both accounts with the process records and go back to the participants to establish which holds✓ Answer
- C.Escalate the contradiction to the sponsor, who can rule on which team's description will be recorded
- D.Adopt the account given by the team that performs the step most often and note the other as an exception
Comparing results across elicitation activities is exactly how inconsistencies are meant to surface, and the way to settle a factual disagreement about how work is done today is to check both accounts against the source records with the people who gave them. Escalation is for conflicting needs that stakeholders must decide between, not for a question of fact the evidence can answer.
Source: BABOK Guide — Confirm Elicitation Results, comparison against other elicitation resultsReport a problem with this question
9. A team decides to leave the checking of its elicitation results until after the solution design is finished. Which consequence best explains why that checking is normally done sooner?
- A.Participants lose the right to change their statements once the design work has been completed
- B.Checking after the design is finished has to be repeated for every session held during the work
- C.An inaccuracy is then corrected only after other work has been built on it, adding cost and delay✓ Answer
- D.Requirements cannot be written in a shareable form until the elicitation results have been checked
The stated reason for confirming elicitation results early is that the longer an error goes undiscovered, the more costly it becomes: quality declines, work is redone and delivery slips, because later work has already been built on the faulty information. Nothing stops requirements being documented before confirmation, and stakeholders never lose the right to correct what they said.
Source: BABOK Guide — Confirm Elicitation Results, cost of undiscovered elicitation errorsReport a problem with this question
10. A department head opens a meeting by saying that the department needs a new customer records system, and asks the analyst to write up the requirements for it. What should the analyst do first?
- A.Work with the department head to state the problem or opportunity that the request is meant to address✓ Answer
- B.Write the request up as stated, since the department head is the stakeholder closest to the work
- C.Ask the sponsor to confirm the budget for a new system before any requirements work is started
- D.Compare the available records products, so the requirements can be written around a chosen one
A need is a problem or an opportunity to be addressed, and it is not the same thing as a solution. When a stakeholder states a solution, the analyst goes back to the underlying problem first, because requirements written around an unexamined solution can be delivered in full and still leave the problem in place.
Source: The Business Analysis Standard — Need as a core concept, need distinguished from solutionReport a problem with this question
11. Stakeholders keep misreading a written specification of an order process: they agree with each sentence, yet disagree about the order in which the steps occur. What should the analyst do?
- A.Record each stakeholder's reading separately, so that every understanding of the process is kept
- B.Hold the specification back until the stakeholders have agreed the order among themselves first
- C.Rewrite the text in shorter sentences, since ambiguous wording is what usually causes the disagreement
- D.Add a diagram of the activity flow alongside the text, since each format shows a different aspect✓ Answer
Requirements are specified and modelled in text, in matrices and in diagrams, and each format makes a different perspective visible: text carries detail, while a model of activity flow carries sequence. Sequence confusion in prose is a signal to add the matching model, not to preserve competing readings of the same text.
Source: BABOK Guide — Specify and Model Requirements, text, matrices and diagramsReport a problem with this question
12. A set of requirements has passed a quality review: each one is clear, testable and consistent with the others. A stakeholder then says that delivering them would not reduce the delays that prompted the work. What does this indicate?
- A.The requirements need a second quality review, because a sound set cannot conflict with the need
- B.The requirements were written poorly, since a testable requirement always delivers the value sought
- C.The stakeholder's objection belongs to a later stage, once the solution has been built and measured
- D.The requirements were written well, but their alignment with the business need is still unproven✓ Answer
Verification asks whether the requirements were defined right, judging the artefact against quality characteristics such as clarity, testability and consistency. Validation asks whether the right requirements were defined, by checking their alignment with the business need and the value expected; a set can pass the first check and fail the second.
Source: BABOK Guide — Verify Requirements compared with Validate RequirementsReport a problem with this question
13. Before a set of requirements moves forward, the analyst checks each one against the outcomes the business wants and the value it expects. Which question is this check answering?
- A.Whether the requirements can be built within the capability the delivery team has available
- B.Whether the requirements were defined right, judged against the agreed writing standards
- C.Whether the right requirements have been defined for the value the business is seeking✓ Answer
- D.Whether the requirements have been agreed by everyone who contributed information to them
Validating requirements means confirming that they align to the business requirements and support delivery of the value stakeholders expect, which is the question of whether the right requirements were defined. Checking them against writing standards is verification, and agreement by contributors is confirmation of what was captured rather than proof of value.
Source: BABOK Guide — Validate Requirements, alignment with business requirements and valueReport a problem with this question
14. Two department heads state needs that cannot both be met: one wants every refund reviewed by a supervisor, the other wants refunds issued without delay. The analyst works under guidance. What should the analyst do?
- A.Choose the position that fits a remark the sponsor made earlier and record it as the agreed need
- B.Document both positions with their effects and take the conflict to the decision maker for a ruling✓ Answer
- C.Hold both needs back until the two department heads have reached agreement between themselves
- D.Record both needs without comment and leave the delivery team to reconcile them during the build
At foundational level the practitioner flags conflicting needs for review rather than settling them: the decision belongs to the stakeholder with the authority to make it. Quietly choosing a side, leaving the contradiction for the delivery team, or waiting for the parties to agree all leave the conflict unresolved while work continues on an uncertain basis.
Source: IIBA ECBA Exam Blueprint — Need domain, flagging conflicts for reviewReport a problem with this question
15. The expected benefit of a requirement, fewer calls to the service desk, depends on customers choosing to use a new self-service channel. What should the analyst do with that dependency?
- A.Remove the benefit from the requirement, since a benefit outside the team's control cannot count
- B.Leave it unstated, since assumptions are recorded only once the solution has gone into use
- C.Record it as an assumption and define how the expected fall in calls is going to be measured✓ Answer
- D.Treat it as a risk owned by the service desk, which will report it if the calls fail to drop
Validating requirements involves identifying assumptions and defining measurable evaluation criteria, so that a benefit resting on behaviour nobody controls is stated openly and can later be tested against evidence. An unstated assumption does not disappear; it simply becomes visible only when the expected benefit fails to arrive.
Source: BABOK Guide — Validate Requirements, identify assumptions and define measurable evaluation criteriaReport a problem with this question
16. While reviewing the requirements, an analyst finds one that does not trace to any of the outcomes the business stated for the change. What should the analyst do?
- A.Leave it in place and let the priority given to it settle the matter during delivery
- B.Delete it, since a requirement without a stated outcome cannot deliver any value at all
- C.Keep it and write an outcome for it, so that every requirement traces to something
- D.Raise it for review against the stated outcomes before it is carried any further forward✓ Answer
Alignment is checked by comparing requirements with the outcomes and value the business is pursuing, and a requirement that aligns with none of them is flagged for review rather than quietly removed or quietly kept. Inventing an outcome to justify the requirement reverses the logic and hides the very gap the review exists to expose.
Source: BABOK Guide — Validate Requirements, evaluate alignment with solution scope and business objectivesReport a problem with this question
17. Every stakeholder group has marked its own items as the highest priority, and the resulting list is longer than the team can deliver. The analyst is supporting the prioritisation. What should the analyst do?
- A.Give each group an equal share of the capacity, so that no group's items are left out entirely
- B.Set out the trade-offs in value, urgency, cost and risk and have the stakeholders decide the order✓ Answer
- C.Deliver the items in the order they arrived, which avoids any appearance of favouring one group
- D.Rank the items personally using value and urgency, then circulate the ranking as the agreed order
The practitioner facilitates prioritisation and the stakeholders decide it, so the work is to make the trade-offs explicit in terms of value, urgency, cost, risk and dependencies and take them back for a decision. Ranking the list personally exceeds foundational authority, and splitting capacity evenly or working first-come-first-served substitutes a formula for the judgement the stakeholders owe.
Source: IIBA ECBA Exam Blueprint — Need domain, supporting stakeholders in prioritisingReport a problem with this question
18. One requirement carries little direct business benefit, but an external regulator obliges the organisation to meet it. How should this affect the way the requirement is prioritised?
- A.Required compliance is a basis for priority in itself and can outrank items with more benefit✓ Answer
- B.The item goes last, because work forced on the organisation was not chosen by the business
- C.The item is set aside from prioritisation and handled outside the ordered list of work
- D.Benefit decides priority, so the item sits below anything that returns value to the business
Requirements are prioritised on several bases at once, among them benefit, penalty, cost, risk, dependencies, time sensitivity, stability and regulatory or policy compliance. Compliance is therefore a legitimate reason to rank an item highly even when its direct benefit is small, and it is ranked within the same list rather than handled outside it.
Source: BABOK Guide — Prioritize Requirements, bases for prioritization including regulatory complianceReport a problem with this question
19. Priorities agreed at the start of the work are challenged halfway through, after a competitor launches a similar service. What is the appropriate response?
- A.Revisit the order with the stakeholders, since priorities are relative and shift with circumstances✓ Answer
- B.Hold the agreed order to the end of the release, since re-ordering wastes the analysis already done
- C.Re-order the items, and treat the earlier prioritisation as a failure to be reviewed afterwards
- D.Change the order only if the sponsor's original objectives have themselves been formally rewritten
Priorities are relative and not permanent: they change as stakeholder priorities change and as new information and dependencies emerge, so continuous re-prioritisation is normal practice. Freezing the order until the release ends ignores that, and treating a re-ordering as a failure discourages exactly the behaviour the practice expects.
Source: BABOK Guide — Prioritize Requirements, priorities are relative and change over timeReport a problem with this question
20. A backlog already holds more work than the team can complete, and a stakeholder submits a new request that they describe as urgent. What should be done with the new item?
- A.Place it in the list relative to the existing items, according to its value and its urgency✓ Answer
- B.Put it at the top of the list, since the stakeholder who submitted it has described it as urgent
- C.Add it to the end of the list, since items already analysed should be completed before new ones
- D.Hold it outside the list until it has been analysed in the same detail as the items already there
A backlog exists precisely because the volume of work exceeds the capacity to complete it, so new items are added and ordered relative to the items already there, with the highest value and highest priority work at the top. Only just enough analysis is done on an item while it waits, so demanding full detail before it can join the list stalls the request for no benefit.
Source: BABOK Guide — Backlog Management, ordering items relative to each otherReport a problem with this question

Practice questions based on the IIBA ECBA Exam Blueprint, The Business Analysis Standard and the BABOK Guide. ECBA, IIBA and BABOK are marks of the International Institute of Business Analysis; this site is not affiliated with or endorsed by IIBA. The exam was restructured around nine domains, so older preparation material organised by the previous knowledge areas is out of date — study the current blueprint on IIBA's site. IIBA publishes no passing score, so the threshold used here is our own practice target, not an official one. Based on the IIBA ECBA Exam Blueprint

1. A business analyst is preparing the first working session with a department that has never taken part in business analysis before. The invitation told them only the date and the room. What should the analyst do before the session?

2. An analyst must understand how a change in industry rules affects order handling. The detail sits in published rule sets and in the organisation's archived case files, not in anyone's day-to-day knowledge. Which kind of elicitation does this call for?

3. A warehouse team wants to know whether resequencing the picking route would cut handling time. Nobody has ever worked that way, and no records of such a route exist anywhere in the organisation. Which kind of elicitation fits?

4. During an interview, an operations supervisor becomes guarded after the analyst repeatedly steers the conversation back to a prepared list of questions. What should the analyst do?

5. An analyst has been given one hour with a group of stakeholders and a broad topic: problems with customer onboarding. What should the analyst settle first when preparing for the session?

6. A team member has written up the notes from a workshop about how refunds are handled today. The notes have not yet been checked with anyone. What should happen next?

7. An analyst has compared session notes against the source documents and against the results of a second session, and the participants agree the notes are accurate. What has been achieved at this point?

8. Two sessions with different teams produced contradictory descriptions of the same step in the returns process. Both sets of notes are now in the analyst's hands. What should the analyst do?

9. A team decides to leave the checking of its elicitation results until after the solution design is finished. Which consequence best explains why that checking is normally done sooner?

10. A department head opens a meeting by saying that the department needs a new customer records system, and asks the analyst to write up the requirements for it. What should the analyst do first?

11. Stakeholders keep misreading a written specification of an order process: they agree with each sentence, yet disagree about the order in which the steps occur. What should the analyst do?

12. A set of requirements has passed a quality review: each one is clear, testable and consistent with the others. A stakeholder then says that delivering them would not reduce the delays that prompted the work. What does this indicate?

13. Before a set of requirements moves forward, the analyst checks each one against the outcomes the business wants and the value it expects. Which question is this check answering?

14. Two department heads state needs that cannot both be met: one wants every refund reviewed by a supervisor, the other wants refunds issued without delay. The analyst works under guidance. What should the analyst do?

15. The expected benefit of a requirement, fewer calls to the service desk, depends on customers choosing to use a new self-service channel. What should the analyst do with that dependency?

16. While reviewing the requirements, an analyst finds one that does not trace to any of the outcomes the business stated for the change. What should the analyst do?

17. Every stakeholder group has marked its own items as the highest priority, and the resulting list is longer than the team can deliver. The analyst is supporting the prioritisation. What should the analyst do?

18. One requirement carries little direct business benefit, but an external regulator obliges the organisation to meet it. How should this affect the way the requirement is prioritised?

19. Priorities agreed at the start of the work are challenged halfway through, after a competitor launches a similar service. What is the appropriate response?

20. A backlog already holds more work than the team can complete, and a stakeholder submits a new request that they describe as urgent. What should be done with the new item?