Beyond “requirements elicitation”
In her last article for Bridging the Gap, Adriana Beal explained why she don’t see any benefit in moving beyond the term “requirements” when describing the key activities performed by a business analyst. Today our lead consultant heads to the opposite direction, discussing terms frequently used in the literature we at 2wtx don’t particularly like to use to describe the BA work: requirements gathering, capture, elicitation, and trawling.
Read the article and join the discussion at Bridging the Gap:
Subscribe in a reader