Business Analysis 101: BA Foundations BA Competencies Analytical Communication Tools

What This Is

BA Competencies are the blend of analytical thinking, communication mastery, and tool fluency that enable a Business Analyst to move a project from “just an idea” to a validated, value‑adding solution. In a CRM‑implementation project, the BA must dissect the sales‑team’s pain points (analytical), translate them into clear user stories and stakeholder‑friendly presentations (communication), and capture the models in a tool such as Lucidchart or JIRA (tools). These competencies are the engine that powers every BABOK® Knowledge Area.

Key Terms & Techniques

• Root‑Cause Analysis (RCA) – A systematic way to drill down to the underlying problem (e.g., “5 Whys”). Knowledge Area: Requirements Analysis & Design Definition. Deliverable: RCA diagram / problem statement.
• SWOT Analysis – Evaluates Strengths, Weaknesses, Opportunities, Threats of a proposed solution. Knowledge Area: Strategy Analysis. Deliverable: SWOT matrix.
• Stakeholder Map – Visual classification of stakeholders by influence and interest. Knowledge Area: Business Analysis Planning & Monitoring. Deliverable: Stakeholder map (grid).
• RACI Matrix – Defines who is Responsible, Accountable, Consulted, Informed for each activity. Knowledge Area: Business Analysis Planning & Monitoring. Deliverable: RACI chart.
• MoSCoW Prioritization – Must, Should, Could, Won’t – ranks requirements. Knowledge Area: Elicitation & Collaboration / Requirements Life Cycle Management. Deliverable: Prioritized backlog.
• User Story (INVEST) – Short, testable description of a need (Independent, Negotiable, Valuable, Estimable, Small, Testable). Knowledge Area: Requirements Life Cycle Management. Deliverable: User‑story backlog.
• Use‑Case Diagram (UML) – Shows actors, system boundaries, and interactions. Knowledge Area: Requirements Analysis & Design Definition. Deliverable: Use‑case diagram.
• Process Flowchart (BPMN) – Standard notation for business processes. Knowledge Area: Requirements Analysis & Design Definition. Deliverable: BPMN diagram.
• Wireframe / Mock‑up – Low‑fidelity visual of UI screens. Knowledge Area: Requirements Analysis & Design Definition. Deliverable: Wireframe set (e.g., in Axure, Figma).
• Requirements Traceability Matrix (RTM) – Links each requirement to its source, design, test, and status. Knowledge Area: Requirements Life Cycle Management. Deliverable: RTM spreadsheet.
• JIRA/Confluence – Agile work‑tracking (JIRA) and collaborative documentation (Confluence). Knowledge Area: Solution Evaluation (monitoring) & Requirements Life Cycle Management. Deliverable: Epics, stories, sprint boards, meeting notes.
• Power BI / Tableau Dashboard – Visual analytics for solution evaluation. Knowledge Area: Solution Evaluation. Deliverable: KPI dashboard.

Step‑by‑Step Process Flow (Applying the Competencies)

1. Plan & Identify – Build a stakeholder map, RACI, and a high‑level scope document (BA Planning).
2. Elicit & Analyze – Run workshops, interviews, and “5 Whys” sessions; capture findings in RCA, SWOT, and user stories.
3. Model & Prioritize – Draft BPMN process maps, use‑case diagrams, and wireframes; apply MoSCoW to rank the backlog.
4. Validate & Baseline – Review models with stakeholders, resolve conflicts, and baseline the RTM and prioritized backlog.
5. Implement & Evaluate – Track work in JIRA, document decisions in Confluence, and measure outcomes with Power BI dashboards; feed lessons back into the solution‑evaluation loop.

Common Mistakes

Certification Exam Tips

Quick Check Questions

1. Scenario: After a requirements workshop, the sales manager says the new CRM must be delivered in 3 months, but the IT architect warns that the integration will take 6 months. Which technique should the BA use to resolve the conflict?
   Answer: MoSCoW Prioritization – it clarifies what is truly “Must” versus “Should” and helps negotiate realistic delivery expectations.

2. Scenario: The BA needs to show the finance team how a proposed claim‑processing workflow will change. Which diagram notation is most appropriate?
   Answer: BPMN (Business Process Model and Notation) – it provides a clear, standardized visual of the end‑to‑end process that finance stakeholders can easily read.

3. Scenario: A stakeholder asks for a quick visual of the new screen layout before any coding begins. Which artifact should the BA deliver?
   Answer: Wireframe / Mock‑up – low‑fidelity UI representation that communicates layout and navigation without detailed design.

Last‑Minute Cram Sheet (10 One‑Liners)

1. ⚠️ “Elicitation” = activity; “requirements” = output.
2. Stakeholder analysis → Stakeholder map (grid) → RACI matrix (roles).
3. Root‑Cause Analysis (5 Whys) lives in Requirements Analysis & Design Definition.
4. MoSCoW, Weighted Scoring, and Kano are prioritization techniques (RA & CLM).
5. BPMN = process‑flow; UML Use‑Case = functional interaction.
6. User Story must be INVEST; it lives in the Requirements Life Cycle Management backlog.
7. RTM links Requirement ↔ Source ↔ Design ↔ Test ↔ Status (traceability).
8. JIRA = backlog & sprint tracking; Confluence = collaborative documentation.
9. Solution Evaluation outputs: KPI dashboard, lessons learned, recommendation report.
10. Strategy Analysis → SWOT → Business Case → Approval (the first three Knowledge Areas).