Certified Associate in Project Management (CAPM) Business Analysis Frameworks and Practices Syllabus

Business Analysis Frameworks and Practices syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Business Analysis Frameworks and Practices in Certified Associate in Project Management (CAPM), not a summary of it.

1. 1

   Business Analysis Foundations

   5 topics

   • Role of the business analyst
     • BA vs. project manager responsibilities
     • Collaboration with the project team and sponsor
   • Business analysis across the project life cycle
   • Needs assessment and identifying the business problem
   • Situation statements and root cause analysis
   • Defining business goals and objectives
2. 2

   Stakeholder Engagement in Business Analysis

   4 topics

   • Stakeholder identification and analysis
     • Stakeholder register and personas
     • Power/interest grid and salience model
   • Eliciting requirements
     • Interviews, workshops, and focus groups
     • Surveys, observation, and document analysis
     • Prototyping and brainstorming
   • Communicating and confirming elicitation results
   • Managing stakeholder expectations and conflict
3. 3

   Requirements Analysis and Documentation

   4 topics

   • Categories of requirements
     • Business, stakeholder, and solution requirements
     • Functional vs. non-functional requirements
     • Transition requirements
   • Modeling requirements
     • Process models and use cases
     • Data and context diagrams
   • Prioritizing and validating requirements
     • Requirements traceability matrix
     • Verifying and approving requirements baselines
   • Managing requirements changes
4. 4

   Solution Evaluation and Product Roadmaps

   5 topics

   • Validating solutions against requirements
   • Evaluating solution performance and acceptance criteria
   • Obtaining solution sign-off and supporting transition
   • Product roadmaps and backlog management for BAs
   • Measuring business value delivered by the solution

Business Analysis Frameworks and Practices flashcards for Certified Associate in Project Management (CAPM)

25 of 57 cards from the Business Analysis Frameworks and Practices deck — real questions with worked answers.

1. What is the primary role of a business analyst (BA) on a project?

   To work with stakeholders to elicit, analyze, document, and manage requirements, ensuring the delivered solution meets the business need and solves the right problem. The BA acts as a bridge between stakeholders and the project/development team.

2. How does the business analyst's involvement span the project life cycle?

   BAs are involved across all phases: defining the business need and case before initiation, eliciting and analyzing requirements during planning, supporting solution development and change control during execution, and validating/evaluating solution performance during transition and closing.

3. What is a needs assessment in business analysis?

   A pre-project (or early) evaluation of the current state, the business problem or opportunity, and the desired future state, used to determine whether a project is justified and to inform the business case.

4. What is the purpose of identifying the business problem before defining a solution?

   To ensure the team solves the actual underlying problem rather than a symptom, preventing wasted effort on a solution that does not deliver real business value.

5. What is a situation statement in business analysis?

   A concise, objective description of a problem or opportunity that captures the issue, its effects/impact, and the resulting consequences—without proposing a solution.

6. What three elements does a well-formed situation statement typically contain?

   The problem or opportunity, the effect it has on the organization (impact), and the consequence(s) of not addressing it.

7. What is root cause analysis and why do BAs use it?

   A structured technique to identify the underlying source of a problem rather than its symptoms, ensuring the chosen solution addresses the true cause so the problem does not recur.

8. Name two common root cause analysis techniques used by business analysts.

   The Five Whys (repeatedly asking 'why') and the Fishbone/Ishikawa (cause-and-effect) diagram. Pareto analysis is also commonly used to find the vital few causes.

9. What is a fishbone (Ishikawa) diagram used for?

   A cause-and-effect diagram that visually groups potential causes of a problem into categories (e.g., people, process, materials, equipment, environment) to identify root causes.

10. What is the difference between a business goal and a business objective?

    A goal is a broad, high-level statement of a desired end state; an objective is a specific, measurable, time-bound target that supports achieving the goal.

11. What does the SMART acronym stand for when writing objectives?

    Specific, Measurable, Achievable (Attainable), Relevant, and Time-bound.

12. What is a stakeholder in business analysis?

    Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project or its solution.

13. What is the purpose of stakeholder identification and analysis?

    To identify all relevant stakeholders and assess their interests, influence, attitude, and requirements so they can be appropriately engaged and their needs incorporated into the solution.

14. What is a power/interest grid used for in stakeholder analysis?

    To classify stakeholders by their level of authority (power) and level of concern (interest), guiding the engagement strategy (e.g., manage closely, keep satisfied, keep informed, monitor).

15. In a power/interest grid, how should you engage a stakeholder with high power and high interest?

    Manage them closely—engage fully, collaborate, and keep them highly satisfied because they are key decision-makers with strong interest.

16. What is a stakeholder register?

    A document that records the identification, assessment, and classification information about project stakeholders, including their roles, interests, influence, and engagement requirements.

17. What is requirements elicitation?

    The activity of drawing out, exploring, and identifying requirements and related information from stakeholders and other sources, rather than simply collecting them.

18. Name five common requirements elicitation techniques.

    Interviews, workshops/facilitated sessions, surveys/questionnaires, observation (job shadowing), document analysis, brainstorming, focus groups, and prototyping.

19. When is observation (job shadowing) a useful elicitation technique?

    When stakeholders cannot fully articulate their work or requirements verbally, and watching them perform actual tasks reveals real processes, exceptions, and tacit needs.

20. What is a facilitated workshop and why is it valuable for elicitation?

    A structured, facilitated session bringing key stakeholders together to define requirements; it is valuable because it builds consensus quickly, surfaces conflicts, and produces shared understanding in less time.

21. After eliciting requirements, what does 'confirming elicitation results' involve?

    Reviewing and validating the captured requirements with stakeholders to ensure they are accurate, complete, and correctly understood before they are baselined.

22. Why must elicitation results be communicated back to stakeholders?

    To confirm shared understanding, correct misinterpretations, fill gaps, and gain agreement, ensuring the documented requirements truly reflect stakeholder needs.

23. What are common sources of stakeholder conflict on a project?

    Competing priorities, scarce resources, differing requirements or interests, ambiguous goals, scope disagreements, and personality or communication differences.

24. What is the role of the BA in managing stakeholder expectations?

    To proactively communicate scope, constraints, and progress; clarify what the solution will and will not do; and negotiate trade-offs so stakeholder expectations stay realistic and aligned.

25. Which conflict-resolution approach generally produces the best long-term outcome?

    Collaborating (problem-solving/confronting)—working together to find a win-win solution that satisfies the legitimate concerns of all parties.

See more Business Analysis Frameworks and Practices flashcards →

Planning Business Analysis Frameworks and Practices for Certified Associate in Project Management (CAPM)

Business Analysis Frameworks and Practices (Certified Associate in Project Management (CAPM)) FAQ