CCBA Exam Dumps - Certification of Capability in Business Analysis (CCBA)

Dependencies are the relationships between requirements that indicate that one requirement is contingent on another requirement. Dependencies can affect the feasibility, value, and risk of the requirements, and therefore, they should be taken into account when prioritizing the requirements. The business analyst should identify and document the dependencies between the requirements, and analyze how they impact the project scope, schedule, and budget. The business analyst should also communicate the dependencies to the business owner and other stakeholders, and help them to prioritize the requirements based on the dependencies and the business objectives. References: BABOK Guide v3, page 156; CCBA Mock Test, question 7

The user story “As a customer service representative, I need to enter my time on the mobile application so that I can leave work to pick up my sick daughter from school” is not aligned with the existing scope of the project, which is to support external customers and broaden the organization’s brand and increase customer engagement. This user story is focused on the internal staff and their convenience, rather than the external customers and their needs. Therefore, the BA must suggest that the story be included with a change to solution scope or be removed, as it may not add value to the project or the stakeholders. The BA should evaluate the alignment of the user stories with the existing scope by using the scope statement, the business case, and the business objectives as the reference points1. The other options are not the best techniques that the BA should use to evaluate the alignment of the user stories with the existing scope, as they may not address the issue of scope creep or misalignment. Adding the functionality to the list of requirements may increase the complexity, cost, and risk of the project, without delivering the expected benefits. Asking the product owner to rank the user story against the existing product backlog may not resolve the conflict or inconsistency between the user story and the scope statement. Reviewing the business objectives and determining the potential value may not be sufficient to justify the inclusion of the user story, as it may still contradict the scope statement or the business case. References:

• 1: Scope Statement: Definition, Benefits and Examples
• : Business Case: Definition, Benefits and Examples
• : Business Objectives: Definition, Benefits and Examples

The business analyst should consider the business relevance of the requirements while tracing them to the business needs, goals, and objectives. This will help the BA to ensure that the requirements are aligned with the business value and provide a clear rationale for their inclusion in the solution scope. By tracing the requirements, the BA can also identify and eliminate any unnecessary or redundant features that do not contribute to the business value.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Life Cycle Management knowledge area, where tracing requirements is a key task for the BA12. It also relates to the Business Analysis Planning and Monitoring knowledge area, where the BA should define the business analysis approach and the requirements prioritization process

The BA should store the requirements package on a secure shared drive that has access control and encryption to protect the sensitive information from unauthorized access or modification. This will ensure that the requirements are available for future reference and can be traced to the solution. Printing the requirements package and distributing it to stakeholders in person may compromise the confidentiality and integrity of the information. Archiving the requirements package in the business analysis portal may not provide adequate security measures for sensitive information. Sending the requirements package to stakeholder in a password protected email may expose the information to interception or hacking. References: [A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)], Chapter 3: Business Analysis Planning and Monitoring, Section 3.6: Plan Requirements Management Process, Task 3.6.2: Define Requirements Change Process, Page 58. [Business Analysis for Practitioners: A Practice Guide], Chapter 3: Requirements Elicitation and Analysis, Section 3.7: Requirements Traceability, Page 66.

Creating an agenda is a useful activity to ensure a productive and focused workshop, as it helps to define the purpose, scope, objectives, participants, roles, and expected outcomes of the workshop. It also helps to manage time and expectations, and to avoid distractions and conflicts. Documenting feedback, facilitating the workshop, and reserving a location are also important activities, but they are not done in advance of the workshop. References: BABOK Guide v3, page 54; CCBA Mock Test, question 18

 According to the BABOK® Guide, risk attitude is the degree to which an organization or stakeholder is willing to accept or avoid risk. There are four types of risk attitudes: risk neutral, risk averse, risk tolerant, and risk seeking. A risk neutral attitude means that the organization or stakeholder is indifferent to risk and makes decisions based on the expected value of the outcomes. A risk averse attitude means that the organization or stakeholder prefers to avoid risk and is willing to accept a lower return or pay a premium to reduce the uncertainty. A risk tolerant attitude means that the organization or stakeholder is willing to accept risk and is not concerned about the variability of the outcomes. A risk seeking attitude means that the organization or stakeholder prefers to take risk and is attracted by the possibility of higher returns or rewards. In this scenario, the corporation’s attitude towards risk is risk averse, as it decided to cancel the initiatives that were driven by the government regulations based on the prediction of an industry thought leader. This shows that the corporation prefers to avoid the risk of investing in projects that may become obsolete or non-compliant due to the regulatory changes, and is willing to forego the potential benefits of those projects. References:

• [BABOK® Guide], section 10.1: Risk Analysis and Management
• CCBA Exam Questions & Answers with Explanations, question 130

According to the BABOK® Guide, a waterfall approach is a sequential project life cycle that consists of distinct phases, such as initiation, planning, analysis, design, construction, testing, implementation, and maintenance. Each phase has a defined set of activities, deliverables, and exit criteria that must be completed before moving to the next phase. A waterfall approach is suitable for projects that have a clear and stable scope, well-defined requirements, and minimal changes or uncertainty. In this scenario, a new contract requires a thorough level of documentation to be developed and maintained with planned phases of reviews and authorized sign offs. This implies that the project has a high degree of formality, control, and documentation, which fits the characteristics of a waterfall approach. References:

• [BABOK® Guide], section 2.5: Plan Business Analysis Approach
• CCBA Exam Questions & Answers with Explanations, question 418

 Choosing appropriate format to communicate requirements is a technique that helps to ensure business analysis information is clear and understandable. It involves selecting the most suitable way to present the information based on the audience, purpose, context, and complexity of the information. Aligning test scenarios with business needs, ensuring all requirements are testable, and using checklists for quality control are also good practices, but they are not techniques for communicating requirements. References: BABOK Guide v3, page 50; CCBA Mock Test, question 19