Business Analyst
Requirements elicitation questions
104 questions on Requirements elicitation for business analysts, easiest first.
Easy 33
- Spot the non-functional requirementeasy
- 'We need a new dashboard'easy
- Which requirement is testableeasy
- Spot the business requirementeasy
- Spot the transition requirementeasy
- When to observe userseasy
- When to use a surveyeasy
- Asking an open questioneasy
- Actors in use case diagramseasy
- What a BRD containseasy
- Wireframes in elicitationeasy
- The risk with focus groupseasy
- Why it is called elicitationeasy
- When a closed question helpseasy
- Starting with existing documentseasy
- Preparing for a stakeholder intervieweasy
- Repeating back what you heardeasy
- The main rule of brainstormingeasy
- Paper prototypes early oneasy
- Spot the stakeholder requirementeasy
- A constraint, not a requirementeasy
- Why record assumptionseasy
- What scope creep iseasy
- What a context diagram showseasy
- Why keep a project glossaryeasy
- The project sponsoreasy
- Spot the leading questioneasy
- Interface analysiseasy
- Baselining requirementseasy
- One requirement, one thingeasy
- Requirement or designeasy
- After the intervieweasy
- A Likert scale questioneasy
Medium 40
- Conflicting requirementsmedium
- Requirements traceabilitymedium
- 'Just add an Excel export'medium
- Verification vs validationmedium
- Modelling a status lifecyclemedium
- Include vs extendmedium
- One voice dominates a workshopmedium
- Fixing a vague requirementmedium
- Where requirements livemedium
- Classifying a business rulemedium
- Modelling complex rulesmedium
- What 99.9% availability allowsmedium
- Finding the missed stakeholdersmedium
- Interview alone or in a groupmedium
- Asking "why" to go up a levelmedium
- Getting ideas from quiet participantsmedium
- The Delphi techniquemedium
- Card sorting for a new websitemedium
- Contextual inquirymedium
- Margin of error for a surveymedium
- Calculating a response ratemedium
- The 100-dollar testmedium
- Comparing every pairmedium
- Attributes to track per requirementmedium
- Before approving a changemedium
- "Transactions for the last month"medium
- Two requirements that clashmedium
- Needs users do not mentionmedium
- Using a CRUD matrixmedium
- Event-response tablesmedium
- Stakeholders in Dubai and Punemedium
- The parking lot in a workshopmedium
- Requirements volatilitymedium
- Eliciting a report requirementmedium
- Learning from support ticketsmedium
- Reviewing requirements with stakeholdersmedium
- Benchmarking competitorsmedium
- Not forgetting quality requirementsmedium
- Mapping the customer journeymedium
- Learning a job by doing itmedium
Hard 31
- A regulatory change before UAThard
- A manager bypasses the processhard
- Signed off, but users are unhappyhard
- Using AI to draft requirementshard
- Hidden rules in a legacy systemhard
- Security vs usability trade-offhard
- Questioning a simple rulehard
- Agile in a regulated bankhard
- Fit-gap for an off-the-shelf CRMhard
- Interviews contradict the datahard
- "It looks done, ship it"hard
- The sponsor's favourite solutionhard
- A requirement that helps one team, hurts anotherhard
- Marketing wants pre-ticked boxeshard
- Security joins three weeks before go-livehard
- Only unhappy users repliedhard
- The team adds an extra featurehard
- New requests on a fixed-price projecthard
- Juniors who will not contradict managershard
- Requirements copied from a vendor demohard
- Turning daily volume into a peak ratehard
- What backups every 4 hours meanhard
- The only expert is leavinghard
- What "real time" really meanshard
- The spreadsheet nobody mentionedhard
- "Everything is a must-have"hard
- Where the data may be storedhard
- How wrong can the chatbot behard
- Observing staff without telling themhard
- "Users must be satisfied"hard
- How much detail upfronthard