PMI-PBA Practice Questions

For a project that is large, complex, has high regulatory oversight, and a distributed team, an informal approach with minimal documentation is the least appropriate. Such projects require robust documentation for clarity, traceability, and audit purposes. The complexity and distributed nature of the team also benefit from more formal communication and planning, which are hallmarks of predictive or hybrid approaches.

This describes the information management approach, which is a key component of the overall business analysis plan. It defines how BA information will be stored, accessed, traced, and used throughout the project. This includes selecting a repository, defining access levels, and setting standards for requirements attributes and traceability.

This is a well-formed acceptance criterion because it is specific, measurable, and testable. It follows the 'Given-When-Then' format, clearly stating the context, action, and expected outcome. The other options are subjective ('easy to use'), vague ('effectively'), or describe a general capability without a clear test case.

A formal walkthrough or review session is the most appropriate technique. This allows the business analyst to present the finalized requirements and demonstrate how they are traced to the delivered solution components, providing a structured forum for stakeholders to confirm that their needs have been met and to provide formal approval or sign-off.

The description and the diagram perfectly match a Data Flow Diagram (DFD). A DFD illustrates how data is processed by a system in terms of inputs and outputs. It shows external entities (Customer, Warehouse), processes (Validate Order, Fulfill Order), data stores (Orders), and the flow of data between them. It explicitly does not show control flow or sequence.

The problem is with business value realization. The solution was built correctly according to specifications (verification), but it is not delivering the expected business benefit (value). This is a critical part of solution evaluation, as it assesses whether the project successfully solved the underlying business problem, not just whether the software works.

The most effective first step is to bring the discussion back to an objective foundation. By referencing the project's business objectives and the pre-defined prioritization criteria (e.g., ROI, strategic alignment, risk reduction), the BA can help stakeholders evaluate the features against a common, agreed-upon framework. This depersonalizes the conflict and facilitates a data-driven decision.

While acceptance criteria, value scores, and dependencies are all important attributes, the most critical missing piece for sprint planning is the estimated effort or size (e.g., in story points). The development team needs this information to determine how many items they can realistically commit to in an iteration. Without an estimate of size or complexity, capacity planning is impossible.

Stakeholder analysis is the process of identifying project stakeholders and assessing their interests, influence, and potential impact on the project. This is a foundational activity in business analysis, performed early to ensure all relevant parties are considered throughout the project lifecycle, which helps in managing expectations and preventing scope creep.

Requirements traceability is the process of tracking requirements throughout the project lifecycle. This involves linking requirements to their origins (e.g., business objectives, stakeholders) and to other artifacts (e.g., designs, code, test cases). It is essential for impact analysis, managing change, and verifying that the solution meets the business needs.