How Agile is Influencing the Traditional Business Analyst Role: Part 1

Agile presents special requirements challenges. Current lore about representing requirements as user stories does not directly address nonfunctional requirements (e.g., quality attributes and design and implementation constraints). Sharp business analysts can provide crucial help in eliciting and analyzing those important requirements.

Furthermore, agile projects need folks with the ability to, as F Scott Fitzgerald said, “hold two opposed ideas in mind at the same time and still retain the ability to function.” While the delivery team is doing heads-down, short-term development (focusing on what I refer to as the “now-view”), other team members need to help them drive the project community toward what I call the “big-view” and “pre-view.”
(Link: How Agile is Influencing the Traditional Business Analyst Role: Part 1)