PDF CBAP Study Guide

 A RACI chart is a matrix that defines the roles and responsibilities of the stakeholders involved in a task or a process. RACI stands for Responsible, Accountable, Consulted, and Informed. A RACI chart helps to clarify who is responsible for performing the work, who is accountable for the outcome, who needs to be consulted for input or feedback, and who needs to be informed of the progress or results. A RACI chart is important to ensure that the roles and responsibilities of the stakeholders are tracked and communicated, and that there is no confusion, duplication, or omission of tasks. References: [IIBA BABOK Guide v3], section 2.2.2.4, page 25; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 237; CBAP Sample Questions, question 235.

The planning stage of a project defines the number of risks and opportunities, including intense planning and anticipation of risk events. The planning stage is the process of establishing the scope, objectives, approach, and deliverables of the project. It involves defining the project requirements, assumptions, constraints, and dependencies. It also involves developing the project management plan, which includes the subsidiary plans for scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management. The planning stage helps to identify and analyze the risks and opportunities that may affect the project, and to plan the appropriate responses and strategies to address them. The planning stage also helps to align the expectations and involvement of the project stakeholders, and to obtain their approval and commitmentfor the project12. The executing stage of a project is the process of performing the work and producing the deliverables of the project. It involves implementing the project management plan, managing the project resources, executing the project activities and tasks, and creating the project outputs and outcomes. The executing stage helps to monitor and control the risks and opportunities that occur during the project, and to implement the planned responses and strategies to deal with them. The executing stage also helps to communicate and collaborate with the project stakeholders, and to manage their expectations and satisfaction12. The initiation stage of a project is the process of authorizing and launching the project. It involves identifying the problem or opportunity that the project intends to address, and defining the purpose, objectives, scope, and justification of the project. It also involves developing the project charter, which is a document that formally approves and initiates the project. The initiation stage helps to identify and assess the high-level risks and opportunities that are associated with the project, and to determine the feasibility and viability of the project. The initiation stage also helps to identify and engage the key project stakeholders, and to obtain their support and endorsement for the project12. The closing stage of a project is the process of finalizing and terminating the project. It involves verifying and validating the project deliverables, evaluating and documenting the project performance, and closing the project contracts and accounts. It also involves developing the project closure report, which is a document that summarizes and communicates the project results and lessons learned. The closing stage helps to identify and resolve the remaining risks and opportunities that are related to the project, and to ensure the project objectives and benefits are achieved. The closing stage also helps to acknowledge and appreciate the project stakeholders, and to transfer the project ownership and responsibility to the customer or sponsor12. References: CBAP® Handbook, Project Management Body of Knowledge (PMBOK® Guide) - Sixth Edition

A Pareto chart is a quality control tool that displays the frequency of defects or problems in descending order of importance. It helps to identify the most significant causes of poor quality and prioritize improvement actions. A Pareto chart is based on the Pareto principle, also known as the 80-20 rule, which states that 80% of the effects come from 20% of the causes. By using a Pareto chart, a business analyst can focus on the vital few causes that account for most of the defects or problems, rather than the trivial many that have little impact. References:

• BABOK Guide v3, section 10.36 Pareto Chart
• IIBA Business Analysis Competency Model, version 4.0, section 5.2.3.1.2 Pareto Chart

The BA should recommend to gather more information from the individuals who had errors when they attempted to sign on, as this would help to identify and resolve the root cause of the problem. The BA could use techniques such as interviews, surveys, or observation to collect feedback from the affected users, and to understand their needs, expectations, and challenges. The BA could also analyze the system event log to find out the details and frequency of the errors, and to determine if they are related to the user’s behavior, the system’s design, or the environment’s conditions. By gathering more information, the BA could propose and implement appropriate solutions to improve the overall performance of the pilot application. The other options are not the best recommendations for improving the performance, as they may not address the underlying problem, or may introduce new risks or issues. For example, sending a reminder of the user ID and password may not help if the users already know them, or may compromise the security of the system. Automating the login process may not be feasible or desirable, as it may require significant changes to the system or the user’s preferences. Extending the pilot to more people may not improve the performance, but may worsen it, as more users may encounter the same errors or create more workload for the system. References: CBAP Handbook, CBAP Study Guide, BABOK Guide