A city is configuring construction-permit software. On a predictive workstream the BA finishes a BRD and RTM before build; on an adaptive workstream the BA and product owner keep refining the backlog each sprint. What does this contrast show about BA work?

When a city configures construction-permit software with a predictive workstream where the BA finishes a BRD and RTM before build, and an adaptive workstream where the BA and product owner keep refining the backlog each sprint, the contrast shows that BA cadence and artifacts change with the delivery approach—early heavyweight specs in predictive, continuous refinement in adaptive. Business analysis remains essential in both civic streams; only the rhythm and document weight shift. Methodology choice reshapes when and how requirements stabilize, not whether analysis exists.

Claiming business analysis only belongs on predictive civic IT projects fails conceptually because adaptive streams still need elicitation, prioritization support, and acceptance clarity. Claiming adaptive teams must freeze a full BRD before the first sprint starts fails because that freezes predictive behavior onto an adaptive cadence. Claiming the RTM replaces the backlog in every adaptive municipal project fails because traceability and ordered delivery are different jobs; adaptive teams still need a backlog even when they also trace critical rules.

Exam caveat: CAPM associates should adapt BA artifacts to life cycle rather than forcing one document set onto every approach. Operational check: for the permit configuration, keep predictive BRD/RTM discipline on the predictive stream and sprint refinement on the adaptive stream, and brief stakeholders that both are legitimate BA work with different cadences.