CBAP Questions Bank

A change log is a tool that helps to manage and monitor the changes that affect the requirements, the solution, or the project. A change log tracks all characteristics and status of changes that have been received, such as the source, description, priority, impact, approval, and resolution of the changes. A change log can help to ensure that the changes are properly documented, communicated, and controlled, and that they are aligned with the stakeholder needs and expectations. References: BABOK Guide v3, page 54; CBAP / CCBA Certified Business Analysis Study Guide, page 161.

 A business case is a document that provides justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. The purpose of the business case is to communicate the value of the solution to the organization and help the decision-makers decide whether to approve the project or not. The business case should include the following elements:

• Executive summary: A brief overview of the problem, opportunity, solution, benefits, costs, risks and recommendations.
• Introduction: A description of the background, context, scope and objectives of the project.
• Analysis: A detailed analysis of the current state, future state, gap, options, criteria, assumptions and constraints.
• Evaluation: A comparison of the options based on the criteria, such as financial, strategic, operational, technical, social and environmental factors.
• Recommendation: A clear statement of the preferred option and the reasons for choosing it over the others.
• Implementation: A description of the implementation plan, including the schedule, resources, roles, responsibilities, governance, change management and risk management.
• Appendices: Any supporting information, such as data, calculations, charts, diagrams, references, etc.

References:

• Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Approach, Task 3.4.3: Define Business Analysis Process, Technique 3.4.3.1: Decision Analysis, p. 66-67.
• What is business case? | APM
• How to Write a Business Case: Template & Examples | Adobe Workfront

 A test plan is a document that describes the scope, objectives, strategy, and activities of testing a software product or system. A test plan is mandatory in most software development projects because it ensures that the software meets the quality standards and requirements of the stakeholders. A test plan also helps to identify and mitigate the risks, defects, and issues that may affect the software functionality, performance, usability, and security. A test plan is different from a communication management plan, which is a document that describes how the project information will be communicated to the stakeholders. A test plan is also different from a disaster recovery plan, which is a document that describes how the project will resume its operations in the event of a disaster or emergency. A test plan is not a procurement plan, which is a document that describes how the project will acquire the goods and services needed from external sources. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 9: Solution Assessment and Validation, page 329-330.
• How to write a software requirement document (with template), paragraph 6
• These testing methods should be mandatory for any software, paragraph 1
• Software Testing Plan - Tutorialspoint, paragraph 1

Problem tracking is not a technique for conducting elicitation, but rather a technique for managing requirements. Problem tracking is used to identify, document, and resolve issues that arise during the business analysis process. Problem tracking helps to ensure the quality and validity of the requirements and the solutions. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, p. 177
• BABOK® Guide, Section 4.2: Conduct Elicitation, p. 106-107
• BABOK® Guide, Section 4.6: Manage Requirements, p. 121-122