Business Analyst

Intro

A Business Analyst elicits and analyses needs to improve processes, systems, and outcomes. In EA, BAs bridge stakeholders, requirements, and design.

Key points:

• Translates business goals into actionable requirements
• Supports prioritisation and validation with stakeholders
• Common use cases: discovery workshops, user stories, process mapping, acceptance criteria, benefits tracking
• Pitfall: solutioning too early without understanding the problem

Examples:

• Facilitating process redesign workshops
• Documenting requirements and acceptance criteria
• Mapping impacts across applications and data

In practice:

Connect BA deliverables with Business Architecture and EA artefacts.

Related terms: Stakeholder; Process; Requirements

FAQs:

Q: Where do BAs and architects overlap?
A: In requirements shaping, process modelling, and option evaluation.

Q: How to keep requirements clear?
A: Use plain language, acceptance criteria, and traceability.

‍