The Business Analyst Problem
Lately I have become more and more weary of the role “Business Analyst”, aka BA. The role has somehow become the term that nobody in the organization can tell what its specialty is.
I am too lazy to give out examples. What I want to point out is, BAs should stop repeating the requirements from users to the developers already. They need to digest them first, foreseen the potential impact to the system in future. BAs should be a group of people that have most of domain knowledge in the field, not the developers. If BAs only know how to CC emails from users, everybody can be the role.
That is what I want to say.