PMI Professional in Business Analysis Free Sample Questions

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.

MoSCoW (Must have, Should have, Could have, Won't have) is a collaborative technique used to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.

Buy a Feature is a collaborative game where stakeholders are given a limited budget of play money to 'buy' the features they want most. This forces them to prioritize and discuss trade-offs, making it highly suitable for agile environments.

A workshop agenda is the key planning document for a facilitated session. It communicates the purpose, inputs, participants, time-boxed activities, and desired outputs to all attendees, setting clear expectations and ensuring the meeting stays focused and productive.

Root cause analysis (RCA) is a systematic problem-solving method used to identify the underlying causes of a problem. Techniques like the Fishbone (Ishikawa) diagram or the 5 Whys are used to look beyond the immediate symptoms and find the fundamental issue, which is exactly what is needed in this scenario to address the product defects effectively.

The primary purpose of a business case is to provide justification for undertaking a project or initiative. It focuses on the business need, benefits, costs, risks, and alignment with organizational goals. While it may reference high-level requirements, a detailed list is developed later in the project lifecycle.

These are business objectives. They are specific, measurable, achievable, relevant, and time-bound (SMART) goals that define the success criteria for the future state. They quantify the expected business value and provide a benchmark against which the solution's performance will be measured.

Observation (or job shadowing) is the most effective technique in this scenario. It allows the business analyst to see the process in action, understand the context, identify workarounds and pain points that users might not articulate in interviews, and gather rich, tacit knowledge. This provides a much deeper understanding than surveys, high-level focus groups, or potentially outdated documentation.

The BA is beginning the process of requirements analysis and modeling. This involves taking the unstructured information gathered during elicitation and organizing, structuring, and specifying it. Modeling techniques (like process models, data models, and use cases) are used to clarify requirements, identify gaps, and present the information in a clear, unambiguous way.