An adaptive team is building a city grants portal. What BA focus best replaces a single frozen specification?
Select an answer to reveal the explanation.
Short Explanation
Adaptive BA is more chef than sculptor—keep slicing stories and refining the backlog so the team cooks what matters now, instead of guarding one frozen mega-spec.
Full Explanation
An adaptive team building a city grants portal replaces a single frozen specification with BA focus on facilitating story slicing and backlog refinement so requirements stay thin and current. Continuous analysis keeps civic grant workflows aligned with learning without pretending a one-time BRD can anticipate every need. Discipline remains: stories still need clarity, acceptance criteria, and ordering.
Publishing one final BRD and banning further story changes fails conceptually because that reimposes predictive freeze on an adaptive grants delivery model. Moving all analysis to the operations help desk after release one fails because product discovery and backlog refinement belong with the delivery team during adaptive development, not only after release. Requiring a signed 200-page use-case binder before sprint one fails because heavyweight upfront binders contradict adaptive just-enough analysis for a grants portal.
Exam caveat: Adaptive BA work emphasizes slicing and refinement, not the absence of analysis or a giant frozen binder. Operational check: establish a recurring refinement cadence for the grants portal, slice epics into valuable stories with acceptance criteria, and keep the backlog current instead of defending a single frozen specification.