25 Questions — PMI - CAPM : Certified Associate in Project Management - Domain 4 - Business Analysis Frameworks

Expand any question to reveal the correct answer and explanation.

1. 1 A Business Analyst (BA) is working in an adaptive environment and needs to ensure that the strategic milestones of the product align with the tactical iterations. Which artifact should be utilized to visualize this high-level mapping across multiple releases?

   Focus on the artifact that bridges the gap between the vision statement and the specific delivery cycles.

   Product Roadmap

   The roadmap serves as a strategic visual that maps milestones to incremental product releases over time.

   • ✗ Sprint Backlog

     This artifact is too granular, focusing only on tasks committed to for a single iteration rather than long-term strategic alignment.

   • ✗ Project Charter

     While it authorizes the project, it does not provide a time-phased visual of product features and strategic release milestones.

   • ✗ Work Breakdown Structure

     In adaptive environments, the WBS is typically translated into backlogs, and it lacks the temporal release-mapping function of a roadmap.

2. 2 During a project transition, a stakeholder asks how they can be certain that every identified business requirement has been accounted for in the final testing phase. Which tool provides this specific end-to-end evidence?

   Consider the document used to 'trace' a requirement's history and verification status.

   Requirements Traceability Matrix (RTM)

   The RTM links requirements from their origin through development and testing to final delivery.

   • ✗ Product Backlog

     While it contains the list of work, it does not inherently map specific test cases to initial business needs as effectively as a dedicated matrix.

   • ✗ Stakeholder Register

     This document identifies project participants and their interests but does not track the lifecycle of specific functional requirements.

   • ✗ Quality Management Plan

     This plan outlines the standards and methodologies for quality but is not the tracking document for individual requirement fulfillment.

3. 3 An organization is deciding between a predictive and adaptive approach for a new software deployment. If the primary constraint is a highly stable set of requirements with strict regulatory documentation needs, how does this influence the Business Analysis process?

   Think about the phase-gate nature of traditional project lifecycles.

   The BA will focus on detailed, upfront requirements documentation and formal baseline approval.

   Predictive methodologies favor comprehensive upfront planning and controlled change management for stable requirements.

   • ✗ The BA will perform continuous backlog grooming and allow requirements to emerge during iterations.

     This describes an adaptive approach, which is less suited for environments where requirements are already fixed and stable.

   • ✗ The BA role is eliminated in favor of a Product Owner who manages all stakeholder communication.

     The BA role remains critical in predictive environments for elicitation and documentation, even if some tasks overlap with other roles.

   • ✗ The BA will focus primarily on the 'Finish Project' phase to document lessons learned.

     Requirements work in predictive projects is heavily front-loaded in the 'Analysis' and 'Design' phases, not just at the end.

4. 4 To ensure that a delivered solution provides the expected business value, a BA must define specific, measurable conditions that the deliverable must satisfy. What is the correct term for these conditions?

   These are often discussed in the context of 'validating requirements' at the end of a lifecycle.

   Acceptance Criteria

   Acceptance criteria are the quantifiable standards used to verify that a deliverable meets the stakeholders' requirements.

   • ✗ Success Criteria

     Success criteria often refer to broader project goals (e.g., ROI) rather than the specific functional conditions for a single deliverable's approval.

   • ✗ Definition of Done (DoD)

     DoD usually refers to the team's internal checklist for quality standards rather than the client's specific requirement-based approval conditions.

   • ✗ Project Constraints

     Constraints are limitations (like budget or time) within which the project must operate, not the criteria for feature approval.

5. 5 A BA is facilitating a session where stakeholders are providing conflicting views on a proposed feature's priority. Which elicitation technique is most effective for reaching a consensus in real-time through collaborative discussion?

   Think of a synchronous, group-based technique used for intensive requirements gathering.

   Workshops

   Focused workshops bring key stakeholders together to resolve conflicts and define requirements collaboratively.

   • ✗ Surveys

     Surveys are useful for gathering data from large groups but do not allow for the interactive discussion needed to resolve conflicting viewpoints.

   • ✗ Observation

     Observation helps understand current workflows but is passive and does not facilitate active conflict resolution or negotiation.

   • ✗ Document Analysis

     Analyzing existing documents provides historical context but cannot address or resolve real-time disagreements between current stakeholders.

6. 6 In the context of the Business Analysis lifecycle, when does the 'Needs Assessment' typically occur?

   Consider the very first steps in a typical project lifecycle before a project manager is even assigned.

   During the pre-project 'Aspire' phase to justify a business case.

   Needs assessment occurs early to identify problems/opportunities and align project ideas with organizational strategy.

   • ✗ Immediately after the Project Charter is signed by the sponsor.

     Needs assessment usually informs the charter; once the charter is signed, the project has already been justified and authorized.

   • ✗ During the 'Execute Plan' phase to verify deliverables.

     Execution focuses on building the solution; checking needs at this stage is often too late to influence the core project direction.

   • ✗ During the 'Finish Project' phase to evaluate the ROI.

     Evaluation of the solution happens at the end, but the 'Needs Assessment' is the foundational step that initiates the lifecycle.

7. 7 A project team is using an adaptive approach and needs to prioritize the product backlog. Which technique involves stakeholders using a 'fixed budget' to buy the features they value most?

   This method uses a playful analogy to force trade-offs in a resource-limited scenario.

   Monopoly Money

   This technique gives stakeholders a set amount of 'currency' to allocate to the requirements they consider highest priority.

   • ✗ MoSCoW

     MoSCoW categorizes items as Must-have, Should-have, Could-have, or Won't-have, rather than using a currency-based allocation.

   • ✗ Dot Voting

     Dot voting allows stakeholders to place 'dots' on a list of items to show preference, but it doesn't simulate a budget-constrained environment.

   • ✗ Kano Model

     The Kano model classifies features based on customer satisfaction and functionality rather than direct budgetary prioritization.

8. 8 When validating requirements through product delivery, a BA uses the SMART acronym to evaluate acceptance criteria. What does the 'A' in SMART typically represent in this context?

   Think about how criteria should lead directly to a verifiable activity or test.

   Action-oriented

   SMART criteria should be Specific, Measurable, Action-oriented, Realistic, and Time-limited to be effective.

   • ✗ Achievable

     While 'Achievable' is common in goal-setting, the source material specifically identifies 'Action-oriented' within the SMART framework for requirements validation.

   • ✗ Adaptive

     Requirements should be specific rather than adaptive; the 'A' focuses on the clarity of the action to be performed.

   • ✗ Assigned

     Acceptance criteria define 'what' must be done, not necessarily 'who' it is assigned to, which is a project management task.

9. 9 A Business Analyst is comparing the 'Current State' of a business process with the 'Future State' to identify gaps. This activity is a core component of which Business Analysis domain?

   This domain is often the starting point for justifying why a project should even exist.

   Needs Assessment

   Assessing current versus future states is essential to define the business problem or opportunity during needs assessment.

   • ✗ Solution Evaluation

     Evaluation happens after the solution is built/deployed to see if it works, whereas gap analysis often happens before the project starts.

   • ✗ Traceability and Monitoring

     This domain focuses on managing requirements throughout the project lifecycle rather than the initial strategic gap analysis.

   • ✗ Requirements Elicitation

     Elicitation is the act of gathering requirements from stakeholders, which is informed by the gap analysis but is a distinct step.

10. 10 Which role is primarily responsible for bridging the gap between the business problems and the technical project deliverables by ensuring solution value?

    This individual focuses on the 'why' and 'what' of the product rather than the 'how' or 'when' of the project management.

    Business Analyst

    The BA bridges this gap by identifying stakeholder needs and ensuring the solution delivers the expected business value.

    • ✗ Project Manager

      The PM focuses on delivery constraints (time, budget, scope) rather than the deep functional alignment of requirements to business value.

    • ✗ Scrum Master

      The Scrum Master facilitates the process and removes impediments but does not own the requirements-to-value alignment.

    • ✗ Process Manager

      A process manager oversees ongoing operations, while the BA is focused on the change initiated by the project.

11. 11 A BA needs to document the data requirements for a new database. Which model should they use to show the relationships between data entities and their attributes?

    Think of a diagram that specifically focuses on nouns and the lines connecting them to show cardinality.

    Entity Relationship Diagram (ERD)

    ERDs are the standard modeling tool for visualizing data structures and the relationships between different data entities.

    • ✗ Use Case Diagram

      Use cases focus on user interactions with the system, not the underlying data structure or entity relationships.

    • ✗ Context Diagram

      Context diagrams show the system's boundary and external actors but do not provide detail on internal data entities.

    • ✗ Process Flow Diagram

      These diagrams model the sequence of activities in a process rather than the structure of the data itself.

12. 12 What is the primary difference between 'Validation' and 'Verification' in the context of Business Analysis?

    One is about satisfying the customer's intent, the other is about following the blueprints.

    Validation checks if the right product is built; Verification checks if the product is built correctly.

    Validation ensures the solution meets business needs, while verification confirms it meets technical specifications.

    • ✗ Validation is done by the project team; Verification is done by the client.

      The client typically performs validation (acceptance), while the team performs verification (quality control), but these roles can overlap.

    • ✗ Verification happens at the end of the project; Validation happens during planning.

      Validation is often the final step in the delivery cycle, while verification occurs throughout the building process.

    • ✗ There is no difference; they are interchangeable terms in the PMBOK Guide.

      PMI maintains a strict distinction between these terms, as they serve different purposes in the quality and value-delivery spectrum.

13. 13 A BA is working on an adaptive project and the team is frequently changing requirements based on customer feedback. How should the BA handle these changes to maintain traceability?

    Look for a term that implies a continuous, iterative refinement of a list.

    Continuously update and groom the Product Backlog.

    In adaptive environments, the backlog is a living document that is refined and re-prioritized to reflect changing requirements.

    • ✗ Strictly follow the formal Change Control Board (CCB) process.

      Formal CCB processes are characteristic of predictive environments and can hinder the agility of adaptive projects.

    • ✗ Freeze the requirements until the next version release.

      Adaptive projects welcome change mid-project, so freezing requirements would contradict the core agile principles.

    • ✗ Only document changes that affect the project budget.

      Requirements traceability requires tracking all functional changes, not just those with immediate financial impact.

14. 14 Which elicitation technique is best suited for gathering requirements from a large, geographically dispersed group of stakeholders where time and budget are limited?

    Think of an asynchronous method for collecting data.

    Surveys

    Surveys are a cost-effective way to gather quantitative data from many stakeholders simultaneously without travel.

    • ✗ Interviews

      Interviews are time-consuming and expensive to conduct individually with a dispersed group of stakeholders.

    • ✗ Focus Groups

      Focus groups require scheduling synchronous sessions which can be difficult across many time zones and locations.

    • ✗ Observation

      Observation requires being physically present where the work is performed, making it impractical for widely dispersed groups.

15. 15 A BA is creating a 'Situation Statement' during the Needs Assessment. What is the primary purpose of this document?

    This document helps stakeholders agree on 'what' is being solved before 'how' is discussed.

    To clearly identify the business problem or opportunity that needs to be addressed.

    A situation statement articulates the current state problem or the opportunity that justifies the project's inception.

    • ✗ To list the technical specifications for the proposed solution.

      Technical specs are part of solution design, which occurs much later in the lifecycle than the situation statement.

    • ✗ To define the roles and responsibilities of the project team.

      Roles are typically defined in the project charter or a RACI matrix, not in a situation statement.

    • ✗ To provide a detailed cost-benefit analysis for the project.

      While related, the cost-benefit analysis is usually part of the Business Case, which the situation statement supports.

16. 16 Which component of a Product Roadmap defines the specific features or capabilities that will be included in the next major deployment?

    This is a more tactical version of the roadmap.

    Release Plan

    The release plan translates the roadmap's strategy into a specific set of features scheduled for a particular release.

    • ✗ Vision Statement

      A vision statement provides the overall goal but does not detail the specific components of individual releases.

    • ✗ Task Board

      Task boards track the progress of specific activities within an iteration, not the high-level release content.

    • ✗ RTM

      The RTM tracks the status and fulfillment of requirements but is not a planning tool for release content.

17. 17 A BA is documenting a requirement that states: 'The system must be available $99.9\%$ of the time.' In which category does this requirement belong?

    This type of requirement describes 'how' the system should behave rather than 'what' it should do.

    Non-functional Requirements

    Non-functional requirements describe the quality attributes or environmental conditions under which the system must operate.

    • ✗ Business Requirements

      Business requirements are high-level goals for the organization, while system availability is a specific quality attribute.

    • ✗ Transition Requirements

      Transition requirements are temporary needs (like training or data migration) required to move to a new state.

    • ✗ Stakeholder Requirements

      Stakeholder requirements focus on what a specific user needs to do, whereas availability is a system-wide constraint.

18. 18 When performing 'Solution Evaluation,' which activity is intended to determine if a solution should be withdrawn from the market or replaced?

    Think about the phases of a product lifecycle like 'maturity' and 'decline'.

    Evaluating the deployed solution's performance and maturity.

    Post-deployment evaluation tracks the product through its lifecycle phases, including maturity and decline, to decide on its future.

    • ✗ Gathering requirements for Version 2.

      Eliciting new features focuses on growth rather than the decision to decommission or withdraw a product.

    • ✗ Validating the initial project charter.

      The charter is a startup document; evaluation at the end of the lifecycle focuses on the actual outcome, not the initial authorization.

    • ✗ Performing a quality audit during execution.

      Audits ensure processes are followed during the project; solution evaluation determines the product's long-term viability in the market.

19. 19 A BA is using a 'Wireframe' to elicit feedback from users. What is the primary advantage of this type of prototyping?

    This tool is often called a 'blueprint' for the screen.

    It provides a low-fidelity visual that focuses on layout and functionality rather than aesthetics.

    Wireframes are simple diagrams that allow stakeholders to focus on the structure and requirements without getting distracted by design details.

    • ✗ It is a fully functional version of the system that can be used for final testing.

      Wireframes are non-functional mockups; a fully functional version would be an evolutionary prototype or a pilot.

    • ✗ It provides the technical architecture for the database developers.

      Wireframes are user interface (UI) tools and do not provide details on the backend database or system architecture.

    • ✗ It serves as the formal project contract between the client and the vendor.

      A wireframe is a requirements elicitation tool, not a legal or contractual document.

20. 20 In a project following the 'Waterfall' lifecycle, which phase involves the Business Analyst conducting a detailed needs analysis and documenting functional specifications?

    This phase comes after Feasibility but before technical Design.

    Requirements Gathering

    In the Waterfall (SDLC) model, this specific phase is dedicated to detailed needs analysis and documentation of specifications.

    • ✗ Feasibility

      Feasibility is the earlier phase where high-level requirements are elicited just to see if the project is viable.

    • ✗ Analysis

      The analysis phase in Waterfall often focuses on designing the solution based on already gathered requirements.

    • ✗ Design

      Design focuses on architecture and technical concepts, occurring after the functional requirements have been documented.

21. 21 Which artifact is used in adaptive projects to prioritize tasks and track success based on 'Definition of Ready' and 'Definition of Done'?

    This is the primary document owned by a Product Owner.

    Product Backlog

    The backlog contains prioritized items that must meet a 'Definition of Ready' before being moved into an iteration.

    • ✗ WBS

      A WBS is a hierarchical decomposition of work in predictive projects and does not use 'Done' or 'Ready' definitions in the same way.

    • ✗ Risk Register

      While it tracks uncertainties, the risk register does not serve as the primary task prioritization tool for value delivery.

    • ✗ Schedule Baseline

      The schedule baseline is a predictive tool used to measure variances in project timing, not for task prioritization in adaptive cycles.

22. 22 A Business Analyst is identifying stakeholders for a new project. Why is it critical to identify stakeholders early in the project lifecycle?

    Consider the impact of discovering a powerful stakeholder's needs halfway through the build.

    To ensure that all requirements are identified before design begins and to manage expectations.

    Early identification prevents 'missing' requirements later and ensures stakeholders are aligned with the project's vision.

    • ✗ To assign them specific tasks in the project schedule.

      While some stakeholders may have tasks, the BA's primary interest is in their requirements and influence on the project outcome.

    • ✗ To calculate the total project budget based on their salaries.

      Budget calculation is a project management function, and stakeholder identification is about influence and needs, not just cost.

    • ✗ To prevent them from requesting any changes once the project starts.

      Change is inevitable; early identification is about managing those changes properly, not preventing them entirely.

23. 23 Which type of requirement describes the temporary needs required to migrate from an old system to a new system?

    Think about the 'bridge' needed to move from the 'As-Is' to the 'To-Be' state.

    Transition Requirements

    Transition requirements are short-term needs like data conversion or user training that disappear once the project is finished.

    • ✗ Solution Requirements

      Solution requirements describe the permanent features of the product itself, not the temporary steps to get there.

    • ✗ Business Requirements

      Business requirements are high-level organizational goals that the project is intended to achieve.

    • ✗ Environmental Requirements

      This isn't a standard PMI requirement category; typically, these fall under non-functional requirements.

24. 24 A BA is creating a 'Context Diagram.' What is the specific value of this model for stakeholders?

    This diagram looks at the system as a 'black box'.

    It shows the boundaries of the system and how it interacts with external entities.

    Context diagrams clarify scope by visualizing what is inside the system and what is outside, along with the data flows between them.

    • ✗ It provides a detailed breakdown of the internal software modules.

      Context diagrams are high-level and intentionally ignore the internal complexity of the system.

    • ✗ It shows the critical path for the project schedule.

      The critical path is a scheduling tool (Domain 2), while context diagrams are a scope modeling tool (Domain 4).

    • ✗ It identifies the cost-variance for the project budget.

      Variance analysis is an EVM technique, whereas a context diagram is used for requirements elicitation and scope definition.

25. 25 In an adaptive project, who is ultimately responsible for the Product Backlog and ensuring that it accurately reflects stakeholder value?

    This role is often considered the 'voice of the customer' in Scrum.

    Product Owner

    The Product Owner is the single individual responsible for managing the backlog and maximizing the value delivered by the team.

    • ✗ Business Analyst

      The BA often supports the Product Owner in backlog grooming, but the accountability for the backlog itself resides with the Product Owner.

    • ✗ Project Manager

      In pure agile frameworks like Scrum, the PM role is often replaced by the Product Owner and Scrum Master responsibilities.

    • ✗ Scrum Master

      The Scrum Master facilitates the team's process but does not decide which features are in the backlog or their priority.