Field inspectors complain that a new inspection app captures the wrong form fields after developers built from incomplete notes. What BA gap most likely caused the defect?
Select an answer to reveal the explanation.
Short Explanation
If inspectors never really talk through the form with builders, you get pretty screens that miss the checkbox that matters in the field. A BA liaison is the missing radio link.
Full Explanation
When field inspectors complain that a new inspection app captures the wrong form fields after developers built from incomplete notes, the dominant BA gap is missing liaison communication between inspectors and developers about real field needs. Notes alone rarely convey tacit workflow, edge cases, and mandatory checkboxes used on site. Without BA-facilitated dialogue, builders implement a plausible but incomplete form that fails operational use and delays civic inspections.
Excessive BA facilitation preventing developers from inventing fields freely fails conceptually because inventing fields without domain input is not a virtue; the defect came from under-communication, not over-facilitation. Over-documenting inspector workflows before any code was written fails as a diagnosis here because the scenario points to incomplete notes and missing liaison, not to harm from thorough analysis. Inviting inspectors to a single kickoff that somehow guaranteed perfect fields fails because one kickoff cannot replace ongoing clarification of form fields as designs evolve.
Exam caveat: Associates should recognize BA liaison as active translation between domain users and builders, not as a one-time kickoff checkbox. Operational check: convene inspectors and developers for a field-by-field review of the inspection form, update requirements and acceptance criteria for missing fields, and verify the next build against inspector walkthrough before wider rollout.