Complete CBAP IIBA Materials

A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It is written to justify the resources required for the project (money or effort) and align the project objectives to the business needs. It also includes the costs, benefits, and risks of the proposed solution, and compares it with alternative options1. A business case is an important input for the project initiation and approval process, as it helps the decision makers to assess the value and feasibility of the project2.

To write a business case, you need four main inputs: feasibility study, assumptions and constraints, business need, and solution options3. A feasibility study is an analysis that evaluates the technical, economic, social, and environmental aspects of the project, and determines whether it is viable and worth pursuing4. Assumptions and constraints are factors that affect the project scope, cost, schedule, and quality, and that need to be identified and documented in the business case. Assumptions are things that are believed to be true or certain, while constraints are things that limit or restrict the project5. Business need is the problem or opportunity that the project aims to address, and that aligns withthe strategic goals and vision of the organization. Solution options are the different ways of solving the business need, and their respective costs, benefits, and risks.

Stakeholder concerns are not an input for writing a business case, but rather an output of stakeholder analysis. Stakeholder analysis is a process of identifying and prioritizing the people or groups who have an interest or influence in the project, and understanding their needs, expectations, and perspectives. Stakeholder concerns are the issues or challenges that the stakeholders face or anticipate in relation to the project, and that need to be addressed or resolved. Stakeholder concerns are important for defining the requirements, managing the communication, and ensuring the stakeholder satisfaction, but they are not directly used for writing the business case. References:

• How to Write a Business Case (Template Included) - ProjectManager
• How to Write a Business Case | Smartsheet
• Business Case Examples, explained in simple language - Chase Consulting
• Feasibility Study: Definition, Methods, and Examples
• Project Assumptions and Constraints: Examples and Differences
• [Business Need - IIBA®]
• [Solution Options - IIBA®]
• [Stakeholder Analysis: Overview, Tools and Techniques - KnowledgeHut]
• [Stakeholder Concerns - IIBA®]

 The management horizon is the time period over which the costs and benefits of a proposed solution are evaluated. It is also the point in time when the net present value of the solution becomes positive, meaning that the solution has recovered its initial investment and started to generate a profit. The management horizon helps to determine the feasibility and viability of a solution, as well as its alignment with the strategic goals of the organization. References:

• CBAP® Handbook, page 15, section 4.1.2.3
• BABOK® Guide, page 32, section 3.2.3
• How to Write a Business Case (Template Included), under Step 3: Calculate the Financials

 Regulatory ranking is a type of requirements prioritization that involves ranking the requirements based on the compliance with laws and regulations in the industry. Regulatory ranking can help to ensure that the solution meets the legal and ethical standards and avoids penalties or lawsuits. Regulatory ranking can also help to align the solution with the organizational policies and objectives. Regulatory ranking is one of the factors that influence the requirement prioritization, as it reflects the penalty of not implementing a requirement. Regulatory ranking can be done by identifying the relevant laws and regulations for the solution, assessing the impact and likelihood of non-compliance, and assigning a priority level to each requirement123. References: 1: What AreRequirement Prioritization Techniques?1 2: Prioritizing Legal Requirements2 3: What Is Requirements Prioritization?3

The one interrogative that requirements should answer is what. What defines the characteristics, attributes, and features of the requirement. What describes the desired outcome or result of the requirement. What specifies the functional or non-functional aspects ofthe requirement. What helps to identify and differentiate the requirement from other requirements. What also helps to verify and validate the requirement by testing whether it meets the acceptance criteria.

The other interrogatives, when, why, and how, are not essential for identifying the requirement, but they may provide additional information or context for the requirement. When defines the timing, frequency, or sequence of the requirement. Why defines the rationale, purpose, or benefit of the requirement. How defines the method, process, or technique of implementing the requirement. References:

• BABOK® Guide, p. 36, 38, 40
• CBAP / CCBA Certified Business Analysis Study Guide, p. 154, 156
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 1, Video: “Specify and Model Requirements”