BA Basic frameworks

Question 1

A stakeholder says, ‘This isn’t the problem we were trying to solve.’

Answer 1

1 – Requirements Elicitation (alignment on intent)

Question 2

Teams disagree on what outcome success actually means.

Answer 2

1 – Requirements Elicitation (right problem, right outcome)

Question 3

A solution works, but leadership says it missed the original goal.

Answer 3

1 – Requirements Elicitation (misaligned intent)

Question 4

Scope keeps shifting because goals were never clearly defined.

Answer 4

1 – Requirements Elicitation (alignment failure)

Question 5

Stakeholders assumed different objectives from the start.

Answer 5

1 – Requirements Elicitation (shared understanding)

Question 6

A requirement exists but no one identified all necessary components.

Answer 6

2 – Requirements Decomposition (missing elements)

Question 7

Engineering asks what data fields are required after build starts.

Answer 7

2 – Requirements Decomposition (data not identified)

Question 8

No one defined which systems were involved.

Answer 8

2 – Requirements Decomposition (tasks/components missing)

Question 9

A feature description lacks inputs or outputs.

Answer 9

2 – Requirements Decomposition (data gap)

Question 10

Something feels incomplete, but no one can say what.

Answer 10

2 – Requirements Decomposition (objective completeness test)

Question 11

A feature works for most cases but breaks under specific conditions.

Answer 11

3 – Business Rules (if/then logic)

Question 12

Eligibility criteria were never clarified.

Answer 12

3 – Business Rules (conditions)

Question 13

Edge cases were not handled.

Answer 13

3 – Business Rules (exceptions)

Question 14

Users can perform actions they shouldn’t be allowed to.

Answer 14

3 – Business Rules (constraints)

Question 15

Errors occur only in certain scenarios.

Answer 15

3 – Business Rules (conditional behavior)

Question 16

Teams have different interpretations of how work flows.

Answer 16

4 – Process Modeling (visualize flow)

Question 17

No one knows who hands off work to whom.

Answer 17

4 – Process Modeling (handoffs)

Question 18

Approval steps were skipped unintentionally.

Answer 18

4 – Process Modeling (workflow gaps)

Question 19

Different teams assume different sequences.

Answer 19

4 – Process Modeling (order of steps)

Question 20

Problems occur at the seams between steps.

Answer 20

4 – Process Modeling (decisions & exceptions)

Question 21

Stakeholders say, ‘This technically works, but it’s not what I expected.’

Answer 21

5 – User Stories & Acceptance Criteria (clear intent + proof)

Question 22

Success was never clearly defined.

Answer 22

5 – User Stories & Acceptance Criteria (definition of done)

Question 23

Users disagree on whether the feature is complete.

Answer 23

5 – User Stories & Acceptance Criteria (subjective success)

Question 24

Acceptance criteria were vague or missing.

Answer 24

5 – User Stories & Acceptance Criteria (testability)

Question 25

The team built something, but no one agrees it solved the problem.

Answer 25

5 – User Stories & Acceptance Criteria (value confirmation)

Question 26

Developers are confused about what to build.

Answer 26

6 – Backlog Refinement (definition of ready)

Question 27

A dependency surfaces mid-sprint.

Answer 27

6 – Backlog Refinement (readiness failure)

Question 28

Engineering has to guess during implementation.

Answer 28

6 – Backlog Refinement (ambiguity)

Question 29

Work entered development before questions were resolved.

Answer 29

6 – Backlog Refinement (last gate before build)

Question 30

Stories were pulled before they were ready.

Answer 30

6 – Backlog Refinement (readiness check)

Question 31

Someone says, 'I didn’t understand that.'

Answer 31

10 – Communication (transfer of understanding)

Question 32

Stakeholders were surprised by the outcome.

Answer 32

10 – Communication (right info, right time)

Question 33

Engineering interpreted the requirement differently.

Answer 33

10 – Communication (misalignment)

Question 34

Too many follow-up questions after meetings.

Answer 34

10 – Communication (format/timing issue)

Question 35

Information was sent but not absorbed.

Answer 35

10 – Communication (delivery vs understanding)

Question 36

Issues only appear after release.

Answer 36

11 – UAT Coordination (real-world validation)

Question 37

Users use the system differently than expected.

Answer 37

11 – UAT Coordination (actual usage)

Question 38

Business signs off, but problems surface later.

Answer 38

11 – UAT Coordination (false confidence)

Question 39

Edge cases weren’t tested with real users.

Answer 39

11 – UAT Coordination (scenario coverage)

Question 40

Testing didn’t reflect real conditions.

Answer 40

11 – UAT Coordination (business validation)

Question 41

Someone asks, 'Why does this requirement exist?'

Answer 41

14 – Documentation & Traceability (rationale)

Question 42

Different documents say different things.

Answer 42

14 – Documentation & Traceability (source of truth)

Question 43

No one remembers who made a decision.

Answer 43

14 – Documentation & Traceability (decision trail)

Question 44

Changes weren’t updated everywhere.

Answer 44

14 – Documentation & Traceability (trace gaps)

Question 45

New team members can’t follow the history.

Answer 45

14 – Documentation & Traceability (continuity)