A business analyst has identified four different solutions for a business need. In the light of solution assessment, how many solution assessment iterations should he do?
The business analyst can do multiple assessments, one for each solution or to compare multiple solutions.
There is no limit, but the business analyst should perform the same type of assessments for each solution to be balanced.
The business analyst can do one assessment per solution.
There should only be one solution assessment - four is too many. Some of the solutions are better than others.
Solution assessment is the process of evaluating the proposed or implemented solutions, assessing their value and performance, and recommending improvements or changes. Solution assessment can be done in multiple iterations, depending on the number and nature of the solutions, the complexity and uncertainty of the problem, and the stakeholder preferences and expectations. The business analyst can do multiple assessments, one for each solution or to compare multiple solutions, to determine the best solution that meets the business need and objectives, and delivers the expected benefits and outcomes12
Option B is incorrect because there is no rule that the business analyst should perform the same type of assessments for each solution to be balanced. The type of assessments that the business analyst performs depends on the criteria and metrics that are relevant and appropriate for each solution, as well as the availability and reliability of the data and information. The business analyst should use the most suitable and effective assessment methods for each solution, which may vary depending on the solution characteristics and context34
Option C is incorrect because the business analyst can do more than one assessment per solution. The business analyst may need to repeat or refine the assessment for a solution, based on the feedback, validation, and verification of the results, or the changes in the requirements, assumptions, or constraints. The business analyst may also need to perform different types of assessments for a solution, such as feasibility, cost-benefit, risk, impact, gap, or performance assessments, to evaluate the solution from different perspectives and dimensions12
Option D is incorrect because there is no limit to the number of solution assessments that the business analyst can do. The business analyst should not assume that some of the solutions are better than others, without conducting a proper and rigorous assessment. The business analyst should consider all the possible solutions that are within the solution scope, and evaluate them based on the agreed criteria and metrics, to ensure that the optimal solution is selected and implemented5
References:
As a candidate for CCBA, you should be able to recognize the activities associated with each knowledge area. Which of the following is an elicitation process that is a part of job observation?
Identifying stakeholders
Job shadowing
Defining and determining business analysis processes
Planning how requirements will be approached, traced, and prioritized
Job observation is a technique that involves observing and documenting the tasks, activities, and behaviors of a stakeholder or a group of stakeholders in their work environment. It helps to elicit information about the current state of the business processes, the roles and responsibilities of the stakeholders, the problems and issues they face, and the opportunities for improvement. Job observation can be done in different ways, such as:
The other options are not elicitation processes that are part of job observation, but they are related to other business analysis knowledge areas or techniques:
References:
If an organization wants to re-use requirements, where should the defined requirements be kept?
Requirements management plan
Requirements repository
Solution scope
Project management plan
According to the BABOK® Guide, a requirements repository is a tool that stores and manages the requirements and designs of a project or an organization. A requirements repository can facilitate the re-use of requirements by providing a centralized and accessible location for storing, retrieving, and updating the requirements. A requirements repository can also help to maintain the traceability, quality, and consistency of the requirements. Therefore, option B is the correct answer. The other options are not suitable places for keeping the defined requirements for re-use, as they are either documents or scopes that may not be easily accessible, searchable, or modifiable. References: BABOK® Guide, page 40; Business Analysis Expert Certification, CCBA® | IIBA®, section “What Should I know to be CCBA Certified?”
Ralph is a business analyst for his organization and he's using the plan-driven approach for business analysis. Ralph has captured the requirements of the project, but what must happen before he can begin capturing and defining the requirements at a deeper level of detail?
The initial requirements must be tested for time, cost, quality, and risk.
The initial requirements must undergo a feasibility study.
The initial requirements must be formally approved by the stakeholders.
The initial requirements must pass through the Delphi Technique.
According to the BABOK Guide, a plan-driven approach is an approach that plans upfront with maximum control of what the expected implementation would be. The waterfall project methodology supports a predictive approach in planning. In this approach, the business analyst defines the requirements at a high level and then seeks formal approval from the stakeholders before proceeding to the next phase of the project. This ensures that the scope and objectives of the project are clear and agreed upon by all parties involved. The initial requirements are also known as the business requirements or the scope statement. They provide a broad overview of the problem or opportunity, the desired outcomes, the assumptions, constraints, and risks. The initial requirements are usually documented in a business case, a project charter, or a statement of work. The initial requirements must be formally approved by the stakeholders before the business analyst can begin capturing and defining the requirements at a deeper level of detail, such as the stakeholder, functional, non-functional, transition, and quality requirements. These detailed requirements are usually documented in a requirements specification, a use case model, a data model, a process model, or other artifacts. The detailed requirements must also be validated and verified by the stakeholders before they can be implemented by the solution team. References:
Copyright © 2021-2024 CertsTopics. All Rights Reserved
