Free PMI-PBA Practice Test

The purpose of the meeting is to perform requirements validation. Validation is the process of confirming that the requirements and the proposed solution will meet the stakeholders' needs and deliver the expected business value. By walking the client team (stakeholders) through use cases and screen mockups (representations of the solution), the business analyst is checking if the team is building the right product. This ensures the solution is aligned with the actual business and stakeholder requirements before development proceeds further.

A. Verification, not validation, checks if the system is built correctly according to specifications and quality requirements. This meeting is about business need alignment.
B. Transition requirements focus on the activities needed to move from the current state to the future state, which is not the focus of use cases and mockups.
D. The documents (use cases, mockups) are representations of the solution requirements; the goal is to validate them against the higher-level stakeholder and business needs.

1. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 6.4, Validate the Solution, p. 127. "Validation is the process of checking to ensure that the solution or its components meet business needs and provide value to stakeholders."

2. Wiegers, K., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press. Chapter 14, "Validating the Requirements," describes reviews and walkthroughs with customers as a primary technique for ensuring requirements will satisfy user needs.

Force-field analysis is a decision-making tool used to identify and analyze the forces for (driving forces) and against (restraining forces) a proposed change or initiative. When stakeholders disagree on the value, this tool facilitates a structured discussion by visualizing the pros and cons. It helps the group understand the sources of disagreement and work towards a consensus by identifying ways to strengthen driving forces and mitigate restraining ones, thereby clarifying the initiative's overall value proposition.

A. PEST analysis is used for external environmental scanning (Political, Economic, Social, Technological), not for resolving internal stakeholder disagreements on value.
C. Feasibility analysis determines if an initiative is viable (e.g., technically, financially). It answers "can we do it?" not "what is its value?"
D. Gap analysis identifies the difference between the current and future states. It defines the scope of work, but does not resolve disputes over an initiative's value.

Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 5.5.2.3, p. 178. "Force field analysis is a technique used to analyze the forces for and against a proposed change... It is useful for facilitating a decision on whether to move forward with a proposed change."

Agile methodologies are founded on principles of close, daily collaboration between business stakeholders (like product owners) and the development team. This approach is specifically designed to facilitate constant communication, enabling rapid feedback loops and the ability to address changes or issues as they arise during development. The Agile Manifesto explicitly values "customer collaboration over contract negotiation" and states, "Business people and developers must work together daily throughout the project," which directly supports the scenario described.

A. Iterative is a component of many Agile approaches, but Agile as a whole better encapsulates the required collaborative and communication principles.
B. Waterfall is a sequential model where communication is formalized at phase gates, preventing the constant interaction needed to address issues as they develop.
C. Linear is another term for a sequential, Waterfall-like approach and is unsuitable for fostering constant communication and adapting to emergent changes.

- Project Management Institute. (2017). Agile Practice Guide. Section 2.2, Principles of the Manifesto for Agile Software Development, p. 9. The guide highlights the principle: "Business people and developers must work together daily throughout the project."

- Project Management Institute. (2017). Business Analysis for Practitioners: A Practice Guide. Section 2.3.3, Adaptive Approaches, p. 18. This section describes how adaptive (Agile) approaches "rely on short iterations... and a high degree of stakeholder engagement."

The project life cycle is a fundamental factor that dictates the approach to business analysis. Whether the project follows a predictive (waterfall), adaptive (agile), or hybrid model determines the timing, formality, and nature of business analysis activities. For instance, a predictive life cycle requires extensive upfront requirements definition and formal documentation, while an adaptive life cycle involves iterative elicitation and refinement of requirements in short cycles. The business analyst must tailor the plan for BA activities to align with the chosen project life cycle to ensure integration and success.

A. Communication plan: This is an output of the planning process that describes how information will be shared, not a primary driver for selecting which BA activities to perform.
C. Return on investment (ROI): This is a financial metric used to justify the project's initiation and measure its value, but it does not dictate the specific BA tasks to be performed.
D. Payback period: This is another financial metric for project justification. It determines how long it takes to recoup the investment, not how business analysis activities are planned.

1. Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 3.1.4.2, Project Life Cycle, p. 48. "The project life cycle influences which business analysis activities will be performed, when they will be performed, and how they will be performed."

2. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 3.2, Determine the Business Analysis Approach, p. 25. "The business analysis approach is also influenced by the project life cycle."

The business analyst's primary role when a requirements conflict is discovered is that of a facilitator and communicator. The first and most critical step is to inform the relevant stakeholders about the conflict. By bringing the right people together, the business analyst can facilitate a discussion, ensure all viewpoints are heard, and guide the stakeholders toward a mutually acceptable resolution. This approach ensures that the decision is made by those with the proper authority and ownership of the requirements.

A. Consulting only the sponsor may bypass other key stakeholders. Logging it as a constraint is premature as the conflict may be resolvable.
B. Performing an impact analysis is a valuable part of the resolution process, but the initial action must be to communicate the conflict to stakeholders.
C. The requirements baseline cannot be updated until the conflict is resolved and a decision has been formally approved by the stakeholders.

1. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 4.6, p. 89. ("The business analyst is responsible for ensuring that conflicts are resolved... The business analyst facilitates communication between the stakeholders who are in conflict to help them resolve the issue.").

2. Pohl, K. (2010). Requirements Engineering: Fundamentals, Principles, and Techniques. Springer. Section 7.3.2, p. 188. (Discusses conflict resolution, emphasizing that the first step is detection and communication, followed by negotiation among stakeholders).

A team peer review is a formal or informal review of a work product by colleagues of the producer. It is a direct and highly effective technique for quality assurance. During a peer review of requirements, the team specifically checks for characteristics such as clarity, conciseness, completeness, and verifiability. This process is designed to identify and correct issues like ambiguity or requirements that cannot be tested, ensuring they are of high quality before being baselined.

A. Fishbone analysis is a root-cause analysis technique used to identify the potential causes of a problem, not to evaluate the quality of requirement statements.
B. A resource checklist is a project management tool used to ensure that all necessary resources (e.g., people, equipment) are available for the project.
C. A traceability matrix links requirements to other artifacts to ensure coverage but does not directly identify ambiguity within the text of a requirement itself.

Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 4.4.1, Verify Requirements, p. 61.

Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 5.4.3.1, Verify Requirements, p. 138.

The process for obtaining formal signoff should be defined in the project's planning documents. A RACI (Responsible, Accountable, Consulted, Informed) matrix is a standard tool used to clarify stakeholder roles and responsibilities. By referring to the RACI matrix, the business analyst can identify the individual(s) designated as 'Accountable' for accepting the solution, ensuring the correct person provides the official signoff.

A. The sponsor may be the accountable party, but this is not guaranteed. The RACI matrix provides the definitive answer without making assumptions.
B. The stakeholder who provided the most requirements is not necessarily the one with the authority to approve the final solution.
C. Formal signoff is a critical step in solution evaluation and project closure to confirm that the deliverables meet the agreed-upon criteria.

1. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 3.2.2, Identify Stakeholders, p. 35. This section describes the use of a RACI chart to "identify the roles and responsibilities of the stakeholders in relation to the business analysis activities." The 'Accountable' role is typically the approver.

2. Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 5.3.2.2, Stakeholder Engagement and Communication Approach, pp. 111-112. This section discusses using tools like a RACI matrix to define stakeholder roles, including who has approval authority.

The requirements baseline is the formally approved set of requirements that the project team has committed to delivering. It serves as the definitive source for what is in scope for a particular release or for the project as a whole. Providing this document to the project sponsor directly and authoritatively answers the question of which requirements will be implemented. Any changes to this baseline must go through a formal change control process.

A. A requirements traceability matrix shows relationships between requirements and other artifacts but does not, by itself, represent the final, approved scope.
C. The requirements management plan describes the process for managing requirements; it does not list the actual requirements to be implemented.
D. A requirements impact analysis is a study conducted to evaluate the effects of a proposed change, not a document listing the full scope.

1. Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 4.4.2.1, "Requirements Baseline," p. 122. Defines the baseline as the approved requirements that form the basis for project work.

2. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 5.6, "Establish the Requirements Baseline," p. 80. States that the baseline is the agreed-upon requirements that will be used to manage the project execution.

In a RACI (Responsible, Accountable, Consulted, Informed) matrix, the 'Responsible' role is assigned to the individuals or groups who perform the work and execute the tasks. The scenario states that the technical staff will "write and code the requirements" and the testing team will "test the new functionality." These are the hands-on activities required to complete the project deliverables. Therefore, the technical and testing teams are responsible for these tasks.

A. Accountable refers to the single individual with ultimate ownership for the task's completion, often a manager or project lead, not the team doing the work.
B. Consult refers to stakeholders who provide input or expertise; the teams here are executing the work, not just providing advice.
D. Inform refers to stakeholders who are kept up-to-date on progress; these teams are active participants, not passive recipients of information.

1. Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 3.2, Identify Stakeholders. Project Management Institute. "Responsible. The person or people who will perform the work." (p. 58).

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 9.1, Plan Resource Management. Project Management Institute. "Responsible. Those who do the work to achieve the task." (p. 317).

When a new requirement is added, its relationships with existing requirements, business objectives, and solution components must be understood to assess the full impact. Managing requirements traceability involves creating and using a requirements traceability matrix. This matrix is the primary tool for identifying these relationships, allowing the business analyst to effectively trace the dependencies and potential impacts of the change across the project, thereby uncovering associated risks.

A. Manage solution scope: This is a broader process; traceability is a specific task within it used to perform the impact analysis.
C. Manage requirements prioritization: Prioritization occurs after the impact of the new requirement is understood, not as a means to identify it.
D. Manage assumptions and constraints: While the new requirement might affect assumptions, traceability is the direct task used to identify impacts and dependencies.

- Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 5.1, Trace Requirements, p. 148. "The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to manage the effects of change to one level on related levels."

- Project Management Institute. (2017). Business Analysis for Practitioners: A Practice Guide. Section 5.4, Traceability and Monitoring, p. 87. "Traceability helps in performing an impact analysis by providing a view of all the requirements that will be impacted by a proposed change."