Topic · 16 notes
Basics
Short pages that give you the shared language the rest of the site relies on. If you are new to business analysis, read the BACCM, requirements classification and stakeholder pages first.
What Is a Business Analyst?
What a business analyst does, what they produce, and how the role differs from systems analyst, product owner and project manager.
iibaThe BABOK Guide and IIBA in Brief
What the BABOK Guide contains, who publishes it, and how to use it as a working reference rather than a rulebook.
baccmThe Business Analysis Core Concept Model (BACCM)
Six concepts (change, need, solution, stakeholder, value, context) that give any business analysis task a quick completeness check.
classificationRequirements Classification: Business, Stakeholder, Solution, Transition
The BABOK Guide's four requirement types: business, stakeholder, solution (functional and non-functional) and transition, with tips for tagging your own.
designRequirements vs. Designs
A requirement describes a need; a design describes a solution. How to tell them apart, why the line blurs, and how to use designs to find requirements.
stakeholdersStakeholder Roles in Business Analysis
The BABOK Guide's generic stakeholder roles, plus Tarasenko's four groups and silent stakeholders, as prompts for a complete stakeholder list.
elicitationThe "Why? What? How?" Principle
Elicit the reason for a product before what it should do or how it should work. A simple habit that turns requested solutions into real requirements.
competenciesUnderlying Competencies of a Business Analyst
The six competency categories in the BABOK Guide, compared with the BCS and Wiegers views, plus a simple way to assess and grow your own.
perspectivesBABOK Perspectives: Agile, BI, IT, Business Architecture, BPM
The five BABOK Guide perspectives and what each one changes about the analyst's focus, deliverables, techniques and key competencies.
careerA Skill Ladder for Analysts
A four-level career model for business and systems analysts, from junior to head of analysis, with other ways to think about growth.
surveyWhat Business Analysts Actually Do: Lessons from a 2020 Survey
Findings from a 2020 DataArt survey of 328 business analysts in Ukraine: techniques used, quality problems, root causes, and practical takeaways.
methodologiesBusiness Analysis Methodologies and ARIS
Three families of business analysis models, the ARIS views of an organization, and why modeling the problem domain protects your requirements.
agileProduct Owner vs. Proxy Product Owner
How to split work between a product owner and a proxy product owner, a role analysts often fill in agile teams, with a template you can copy.
lifecyclesSolution Delivery Lifecycles
Waterfall, V-model, incremental, spiral and agile delivery compared: where the analyst fits in each, how MoSCoW maps to increments, and buy vs. build.
process modelThe BCS Business Analysis Process Model
The BCS book's five-stage process (investigate, consider perspectives, analyse needs, evaluate options, define requirements) plus delivering change.
rupRUP in Brief
What the Rational Unified Process is, its principles and phases, and the analyst artifacts worth borrowing even if you never run RUP.
Main sources for this section#
- IIBA. A Guide to the Business Analysis Body of Knowledge (BABOK® Guide), v3. 2015.
- D. Paul, D. Yeates, J. Cadle (eds.). Business Analysis, 2nd ed. BCS, 2010.
- A. Pererva, V. Ivanova. The Analyst’s Path: A Practical Guide (in Russian).