There seems to be different opinions regarding the role of the business analyst and searching the web one finds countless definitions. IIBA defines 6 key competencies i.e.
- Business Analysis Planning and Monitoring
- Elicitation
- Requirements Management and Communication
- Enterprise Analysis
- Requirements Analysis
- Solution Assessment and Validation
The question is where is the business analyst located in the organization structure? This depends on the role of the business analyst i.e. business architect, business process analyst or IT business analyst. The devil is in the details and when looking at the tasks of the different roles it becomes clearer that although all qualify as “business analysts” there is a difference. The attached class model attempts to explain these differences.
Six Reasons Why EA Should NOT be Assigned to the IT Department
6. EA ≠ IT Architecture
5. True EA leads to redistribution of authority, which is beyond CIO jurisdiction.
4. EA value proposition (i.e. standardization vs. innovation) is solely business realizable.
3. The primary goal of EA is to build coherent enterprises, not better IT systems.
2. Synthesis takes precedence over analysis.
1. EA failure is an organization failure, not an IT failure
