BABOK Cheat Sheet 2026

The 30 highest-yield BABOK facts, distilled from real exam questions. Print it, save it as a PDF, or study it here — free, no sign-up.

1. Which of the following best describes 'passive observation' in elicitation? → The analyst watches without interacting with the worker
2. What is a key consideration when developing transition requirements during Strategy Analysis? → Identifying the changes needed to move from the current state to the future state
3. Which elicitation technique is most effective when the subject matter is complex and requires expertise from the stakeholder? → Interview
4. What is the purpose of 'Manage Stakeholder Collaboration' in BABOK? → To ensure stakeholders engage appropriately throughout the business analysis effort
5. What distinguishes a focus group from an interview in elicitation? → Focus groups involve multiple stakeholders discussing a topic together
6. What is the 'domain subject matter expert' (SME) stakeholder role in BABOK? → A stakeholder with deep knowledge of a specific topic relevant to the solution
7. Which metric type directly measures whether the solution is delivering the intended business outcomes? → Outcome metric
8. Which of the following is a type of stakeholder in BABOK? → Regulator
9. Which stakeholder classification technique uses two axes — power and interest — to help business analysts prioritize engagement efforts? → Power/interest grid
10. Which elicitation technique is most appropriate for gathering broad input from a large, geographically dispersed stakeholder group? → Surveys/Questionnaires
11. In the BACCM, what does 'Context' refer to? → The circumstances that influence, are influenced by, and provide understanding of a change
12. Non-functional requirements are also called: → Quality of service requirements
13. What does 'verify requirements' mean in BABOK? → Checking that requirements are well-formed, complete, consistent, and unambiguous
14. What does 'collaborative games' as an elicitation technique primarily encourage? → Creative thinking and engagement among stakeholders
15. Which of the following is a task within RADD? → Specify and Model Requirements
16. When should a business analyst recommend placing requirements under formal change control? → When requirements have been baselined and agreed upon by stakeholders
17. In BABOK, which task specifically focuses on ensuring requirements reflect the current needs of stakeholders and remain valid over time? → Maintain Requirements
18. According to BABOK, which stakeholder role is typically responsible for providing financial resources and formally approving the business case? → Sponsor
19. What role does risk analysis play in a business case? → It identifies potential challenges and their impact on the project
20. When planning stakeholder engagement, what is a key consideration? → Identifying and analyzing stakeholder needs and expectations
21. Which prioritization technique assigns numerical weights to requirements based on multiple criteria? → Weighted Ranking
22. Which type of requirement describes what a system must do — its behaviors and functions? → Functional requirement
23. What is the primary focus of the Solution Evaluation knowledge area in BABOK? → Assessing the performance of a solution and determining its value to the organization
24. According to BABOK v3, how is a stakeholder defined? → A group or individual who has an interest in, or is affected by, the outcome of a change
25. What are 'solution limitations' in BABOK? → Factors within the deployed solution that prevent it from achieving full business value
26. What is 'observation' as an elicitation technique also commonly called? → Job shadowing
27. Which underlying competency category specifically addresses the ability to communicate effectively in written and verbal forms? → Communication Skills
28. How does the Agile principle of "responding to change over following a plan" influence business analysis activities? → It promotes adaptability and responsiveness to feedback
29. When specifying requirements in BABOK, what does SMART stand for? → Specific, Measurable, Achievable, Relevant, Time-bound
30. What is a key benefit of using user stories in Agile business analysis? → They facilitate clear communication of requirements from the user's perspective