Business Analyst

BRD & FRD Writing

Perché: You can keep requirements consistent through change requests and version control, so the document still matches what the team is actually building.

User Stories & Acceptance Criteria

Perché: You can write stories that meet INVEST and acceptance criteria in Given-When-Then, so QA can test a story without asking you what it meant.

BPMN Process Modeling

Perché: You can break a large process into subprocesses and model exceptions and events, covering the rejected-order path that the happy-path diagram left out.

Gap Analysis

Perché: You can recommend how to close each gap, choosing between a process change, a new capability or a tool, rather than only listing what is missing.

Data Modeling (ERD)

Perché: You can draw an ERD with entities and cardinality, catching that a customer can have many addresses before the database is built with only one.

SQL Querying for Analysis

Perché: You can query the data with joins and aggregation to check a stakeholder's claim, such as how many orders are actually delayed, without waiting for an engineer.

Stakeholder Mapping

Perché: You can map stakeholders by power and interest and plan communication for each, so the sponsor who can veto the project is not learning about it late.

Facilitation Techniques

Perché: You can run a workshop with MoSCoW prioritization and handle a conflict between two departments, leaving with a ranked list instead of an argument.