Clerks describe permit pain points in office jargon that engineers misread as technical defects. How does BA communication add value?
Select an answer to reveal the explanation.
Short Explanation
Clerks speak “counter talk”; engineers speak tickets. The BA is the interpreter who turns counter pain into backlog items that actually ship the right fix.
Full Explanation
Clerks describe permit pain points in office jargon that engineers misread as technical defects. BA communication adds value by translating clerk language into backlog items engineers can understand and implement. That translation preserves the civic problem’s meaning while expressing it as actionable delivery work, preventing builds that fix the wrong thing or ignore counter realities.
Forcing clerks to write SQL-level acceptance criteria before any conversation fails conceptually because domain experts should not be required to speak engineering dialects to be heard; that barrier suppresses elicitation. Discarding clerk language and letting engineers invent the backlog alone fails because it severs requirements from operational reality at the counter. Storing jargon in a glossary and never converting it into work items fails because glossaries aid understanding but do not themselves create prioritized, implementable backlog items.
Exam caveat: Translation into backlog items is the value; glossaries and raw jargon are inputs, not substitutes for work definition. Operational check: take the latest clerk pain statements, convert each into a candidate backlog item with clear outcome language, review the translations with both clerks and engineers, and order the agreed items in the permitting backlog.