PMI-PBA Certification Analysis Flashcards

A business analyst has been requested to look at an issue. The results of this inquiry will help create a business case. The business analyst first seeks to comprehend the current business procedures of the company. Which approach ought the business analyst to take?

Answer: Observation

To comprehend the current business procedures before creating a business case, observation is a highly effective approach. By directly watching employees perform their tasks in their natural work environment, the business analyst can gain firsthand, unbiased insight into how processes actually work, identify pain points, and understand the context of the problem. This provides a realistic foundation for defining the business need and potential solutions.

The creation of a solution scope is a joint effort between the client and the business analyst. It is crucial that the client:

Answer: spend the time required to provide, clarify, and elaborate requirements.

The client is the primary source of business needs and requirements for any project. For a successful solution scope, it is crucial that the client actively participates by dedicating the necessary time to clearly articulate their needs, provide detailed information, and clarify any ambiguities. This active engagement ensures the business analyst accurately captures the true requirements, leading to a solution that genuinely meets client expectations.

At a nearby pizza joint, automated order entry software is being implemented under the direction of a business analyst. The ordering process takes too long and frequently results in inaccurate orders, thus the business analyst has very little knowledge about the project. What action needs to be taken by the business analyst next?

Answer: Schedule a requirements gathering sessions with the manager of the ordering department.

Given the business analyst has very little knowledge about the project and needs to address issues like long ordering processes and inaccurate orders, the immediate next step is to gather information from key stakeholders. Scheduling requirements gathering sessions with the manager of the ordering department is crucial, as this individual can provide detailed insights into the existing problems, the current process, and the specific requirements for the new automated system.

The business analyst discovers a project objective with no corresponding requirement after the project has been completed. What could have been done to identify this problem prior to delivery?

Answer: Tracing requirements

The problem describes discovering a project objective without a corresponding requirement *after* the project is completed. Requirements traceability is the process of linking requirements to other project artifacts, including business objectives, design components, and test cases. If requirements had been properly traced to objectives throughout the project lifecycle, this gap would have been identified much earlier, ensuring all objectives were addressed by specific requirements before delivery.

A cost-benefit analysis of alternative solution options is being done by a business analyst. The predicted growth rate is clearly highly relevant to the stakeholders. Which method will make it possible for the business analyst to find this information?

Answer: Net present value (NPV)

Net Present Value (NPV) is a financial metric used in cost-benefit analysis that calculates the present value of all future cash flows (inflows and outflows) over the life of an investment, discounted by a specific rate. It explicitly accounts for the time value of money and the predicted growth rate by incorporating discounting. This makes NPV highly relevant when future value and growth are key concerns for stakeholders, as it provides a comprehensive financial assessment.

A user from a department that wasn't involved in the requirements analysis logs a defect during user acceptability testing. The user need to have been: in order to prevent this predicament and lessen its effects on the project.

Answer: identified as a stakeholder as part of the stakeholder analysis.

A user from a department not involved in requirements analysis logging a defect during UAT indicates a critical oversight in stakeholder identification. To prevent such predicaments, the business analyst should have conducted a thorough stakeholder analysis early in the project. Identifying all relevant stakeholders ensures their needs are considered, they are involved in appropriate stages (like requirements gathering or UAT), and their input is incorporated, significantly reducing late-stage defects.

After a test session, a business analyst is looking over a discrepancy report. A flaw has been discovered by the discrepancy report, which the business analyst now needs to fix. Which of the following factors should the business analyst apply in order to determine the best course of action in light of the subpar test result?

Answer: Determine if the defect is in the solution developed, in the original requirement or in the test case.

When a defect is discovered, the business analyst's first and most critical step is to accurately diagnose its root cause. It's essential to determine if the problem lies in the implemented solution (a coding error), the original requirement (it was flawed, ambiguous, or incomplete), or the test case itself (it's testing the wrong thing or is incorrectly written). This diagnostic step is fundamental before deciding on any corrective action, ensuring the right problem is addressed.

A requirement has changed, the business analyst learns while validating a project solution. The company logo is displayed in the upper-right corner of the window rather than the upper-left. The developer responds that one of the stakeholders explicitly requested the change when the business analyst inquires about the change. What is the right course of action for the business analyst?

Answer: Discuss the change in the next stakeholder meeting.

A developer implementing a change based on an explicit request from a stakeholder, without following formal procedures, is a deviation from the baselined requirements. The business analyst's correct course of action is to adhere to the established change control process as defined in the business analysis plan. This ensures that all changes are properly documented, evaluated for impact, approved by the appropriate authority (e.g., CCB), and communicated to all affected parties, maintaining project integrity.

In order to join a new market niche, a corporation is creating a new e-commerce platform. When the government introduces a new set of rules, development is already well under way. What action ought the business analyst to take?

Answer: Evaluate the impact of the change on the project schedule.

When new government regulations are introduced during an ongoing project, they represent a significant external change that can impact the project's scope, requirements, and timeline. The business analyst's immediate action should be to evaluate the *impact* of these new regulations, particularly on the project schedule, as well as cost, scope, and quality. This assessment is critical for determining necessary adjustments and communicating potential delays or resource needs to stakeholders.

Requirements Project elicitation is currently taking place. The production, acquisition, and marketing divisions seek to include particular specifications. In three months, the CEO must be deployed. Which of the following steps is more likely to contribute to the project's success?

Answer: Conduct a stakeholder analysis and balance requirements by understanding the relative power associated with each stakeholder group.

With competing requirements from different departments and a tight deadline, effective prioritization is crucial for project success. Conducting a stakeholder analysis helps identify all relevant stakeholders, their interests, influence, and power. By understanding these dynamics, the business analyst can effectively balance conflicting requirements, negotiate priorities, and ensure that the most critical needs (often those aligned with high-power stakeholders or strategic objectives) are addressed within the given timeline, contributing to project success.

An interested party wants to change a current functionality. Which of the following criteria would be considered to assess how much the product would change?

Answer: Requirements traceability matrix

A Requirements Traceability Matrix (RTM) links requirements to other project artifacts like design components, test cases, and business objectives. When a change to a functionality is proposed, the RTM allows the business analyst to quickly identify all dependent requirements and impacted components. This enables a comprehensive assessment of the scope and extent of the product change, helping to understand the ripple effect of the modification.

The management of a corporation has chosen to introduce a new product. Users may not embrace a new product that requires them to alter their current behaviors, nevertheless, is a concern. Business analysts ought to:

Answer: clearly communicate project objectives and attempt to defuse tensions.

When users are resistant to adopting a new product due to required behavioral changes, the business analyst's role is to facilitate understanding and acceptance. By clearly communicating the project objectives, the benefits of the new product, and how it addresses user needs, the BA can help alleviate concerns. This proactive communication and effort to defuse tensions are crucial for gaining user buy-in and ensuring successful product adoption.

To decide whether formal signoff for the project should be necessary, a business analyst is collaborating with the project manager, business auditors, and project stakeholders. What justification would the business analyst give the group for formal signoff?

Answer: The organization follows an iterative project life cycle.

In an iterative project life cycle, formal signoff can be crucial at the end of each iteration or phase to confirm that the delivered increment meets the agreed-upon requirements. This ensures stakeholder alignment and acceptance of the evolving solution before proceeding to the next iteration. Formal acceptance helps manage expectations, provides a clear baseline for subsequent development, and reduces the risk of rework in later stages of a dynamic project.

A software problem was discovered during user acceptability testing. What action should the business analyst take next to investigate and address the disparity as part of the root cause analysis?

Answer: Create a fishbone diagram.

A fishbone diagram, also known as an Ishikawa diagram, is a powerful tool for root cause analysis. When a software problem is discovered during User Acceptance Testing (UAT), creating this diagram helps the business analyst systematically categorize and explore potential causes across various dimensions (e.g., people, process, tools, environment). This structured approach facilitates a comprehensive investigation to identify the underlying issues rather than just addressing surface-level symptoms.

A nationwide corporation with locations across the nation has implemented a technology that enables employees to view their health benefits online. The project team's business analyst validates solution results to see whether the solution has produced the expected business outcome. What is the most effective way to learn how satisfied the staff members are with the solution?

Answer: Survey

For a nationwide corporation with a large, geographically dispersed employee base, a survey is the most effective and scalable method to gather feedback on satisfaction. Surveys allow for standardized data collection, anonymity, and quantitative analysis, making it feasible to reach a broad audience efficiently. This approach enables the business analyst to assess overall employee satisfaction with the new online health benefits solution comprehensively.

A sponsor asks for a new specification. The majority of the information required for this demand doesn't exist, the business analyst argues, thus it can't be implemented. The demand should be postponed until the required data is available, then added to a subsequent project, suggests the business analyst. The supporter concurs. What action is next for the business analyst?

Answer: Communicate that the status of this requirement has changed.

Once a decision has been made regarding a requirement, especially one involving postponement to a subsequent project, it is critical for the business analyst to communicate this change in status. This ensures all relevant stakeholders are aware of the updated plan and the requirement's current state. Transparent communication prevents misunderstandings and maintains alignment across the project team and with the sponsor.