IIBA CBAP - Certified Business Analysis Professional

A data model is a graphical or textual representation of the data and their relationships within a domain or a solution. It can help to understand the data and accurately reflect a set of requirements by showing the entities, attributes, keys, constraints, and associations that define the data structure and meaning. A data model can also help to prioritize the requirements by identifying the critical and dependent data elements and their impacts on the solution. The other options are not the best modeling formats for this purpose, as they either do not show the data relationships, or do not support prioritization. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 261-262

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 157-158

The BA should approach the solution limitation by assessing the impact on the business operations. This means that the BA should analyze how the inability to meet the SLA in one out of five scenarios would affect the business goals, objectives, performance, value, and risks. The BA should also consider the frequency, severity, and likelihood of the scenarios, and the expectations and needs of the stakeholders. Based on the impact assessment, the BA can then recommend the best course of action, such as modifying the SLA, changing the business process, increasing the scope, or deferring the requirement to a future release. The other options are not the best approaches, as they may either be unrealistic, unnecessary, or ineffective without a proper impact assessment. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 311-312

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 269-270

 The first step for the BA is to understand the current state of the service provider’s business operations and the root causes of the reduced profit margin. This will help the BA to identify the problems and opportunities for improvement, as well as to establish a baseline for measuring the effectiveness of the proposed solutions. The BA can use various techniques to conduct the current state analysis, such as document analysis, interviews, observation, surveys, and SWOT analysis. The other options are not the first step, as they are either focused on the future state or the solution, without understanding the current situation and the underlying needs. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan Business Analysis Approach, p. 93-94

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-109

A change strategy is a plan that outlines how the project team will manage the transition from the current state to the future state of the system, and how they will address the impacts and risks of the change on the organization and the stakeholders. A change strategy is needed when system A is offline for 3 months, as this will affect the claims processing operations and the user experience. A change strategy should include the following elements:

Change vision and objectives: This defines the purpose and scope of the change, and the expected outcomes and benefits of the system upgrade.

Change readiness assessment: This evaluates the current level of awareness, willingness, and ability of the organization and the stakeholders to adopt the change, and identifies any gaps or barriers that need to be addressed.

Change impact analysis: This identifies and analyzes the potential effects of the change on the business processes, roles and responsibilities, policies and procedures, systems and tools, and culture and behavior of the organization and the stakeholders.

Change communication plan: This specifies the key messages, channels, methods, and frequency of communication with the organization and the stakeholders, and how to solicit and incorporate feedback and input.

Change training plan: This defines the learning objectives, content, delivery modes, and evaluation methods of the training programs that will help the organization and the stakeholders acquire the necessary knowledge and skills to use the upgraded system.

Change management roles and responsibilities: This clarifies the roles and expectations of the project team, the sponsors, the champions, the change agents, and the end users in the change process, and how they will collaborate and coordinate with each other.

Change monitoring and evaluation plan: This establishes the metrics, indicators, and tools that will measure the progress and performance of the change process, and how to report and act on the results.

References:

IIBA BABOK Guide, Section 5.6, Define Change Strategy

Change Management Strategy: A Guide with Best Practices, Smartsheet

How to Develop a Change Management Strategy, Indeed

 In the context of risk assessment, the impact of a risk is often calculated by multiplying the Probability of Occurrence (POC) with the Cost of Impact. For each risk in this scenario:

Natural disasters: 0.2 * 15,000 = 3,000

Power surges: 0.5 * 20,000 = 10,000

Human errors: 0.9 * 3,000 = 2,700

System security: 0.4 *16,000 =6,400

Power surges have the highest negative impact to value at $10,000.

References: The calculation is based on standard risk assessment practices which involve evaluating both the probability and impact of risks to prioritize them effectively; as per Business Analysis Professional (CBAP) learning documents or resources

 A satisfy relationship is a type of traceability relationship that indicates that a model element (such as a requirement, a design element, or a test case) fulfills the intent of another model element (such as a stakeholder need, a business requirement, or a regulatory requirement). By using a satisfy relationship, the BA can link the solution components that implement the regulatory requirements and show how they meet the compliance criteria. References:

Overview of working with requirements (SysML)

SysML: Establishing Traceability using Matrix and ETL Table

IIBA BABOK Guide, Section 7.6, Traceability and Monitoring

Relaying upper management support to stakeholders is a way to reduce employee discontent and resistance to change. This can help the employees feel more confident and secure about the change initiative, as they perceive that the leaders are committed and supportive of the change. It can also help the employees understand the vision and goals of the change, and how it aligns with the organizational strategy and values. By communicating the benefits and rationale of the change, and addressing the concerns and fears of the employees, the BA can foster a positive and collaborative attitude towards the change among the stakeholders. References:

Emotional Reactions to Change in the Workplace, CMI

Reactions to Change in an Organization, Wonder

IIBA BABOK Guide, Section 5.5, Assess Organizational Readiness

Before the BA can proceed with any analysis of the features, they need to confirm that the feature requests are valid and aligned with the product vision and goals. Customer support calls may not reflect the actual needs and preferences of the target market, and may include requests that are out of scope or inconsistent with the product strategy. Therefore, the BA should first validate the feature requests with the product owner and other stakeholders, and eliminate any irrelevant or invalid ones. References:

BABOK Guide v3, section 7.2.2.1: “The business analyst validates that the requirements and designs are aligned with the business need and the solution scope.”

Guide to building a product roadmap (with template and examples), section “How to create a product roadmap”: “The first step in creating a product roadmap is to define the product vision. This is the overarching goal or purpose of the product, and it should guide all subsequent decisions and actions.”