IIBA Updated CBAP Exam Questions and Answers by irha

 MoSCoW is an acronym for Must-have, Should-have, Could-have, and Won’t-have this time. It is a prioritization technique that many organizations use in project management, software development, business analysis, etc., to categorize and prioritize requirements or tasks based on their importance and urgency. The method provides a simple and effective way to prioritize work items by assigning them to one of the four categories12:

Must-have: These are the critical and non-negotiable requirements or tasks that must be completed for the project or product to be successful. Without them, the project or product will fail or become useless. For example, compliance with legal or security standards, or core functionality of the product.

Should-have: These are the important but not essential requirements or tasks that should be completed for the project or product to be satisfactory. They add significant value or benefit, but they are not as time-sensitive or critical as the must-haves. They can be postponed or omitted without compromising the project or product. For example, performance improvements, minor bug fixes, or nice-to-have features.

Could-have: These are the desirable but not necessary requirements or tasks that could be completed for the project or product to be enhanced. They improve the user experience or customer satisfaction, but they have a low impact or benefit. They can be included if time and resources permit, or they can be left out without affecting the project or product. For example, aesthetic changes, extra functionality, or user feedback.

Won’t-have: These are the least important or relevant requirements or tasks that won’t be completed for the project or product at the current time. They have a low or negative impact or benefit, or they are not appropriate or feasible at the moment. They can be excluded, deferred, or reconsidered for future projects or products. For example, out-of-scope requests, low-priority issues, or unrealistic expectations.

MoSCoW prioritization helps to manage the expectations and needs of the stakeholders, and to focus on the most valuable and urgent work items. It also helps to deal with changing requirements, scope creep, and resource constraints. MoSCoW prioritization is often used with timeboxing, which is a technique that sets a fixed deadline for the completion of a project or product34. References:

What is MoSCoW Prioritization? | Overview of the MoSCoW Method

MoSCoW method - Wikipedia

Simplify Requirement Prioritization With the MoSCoW Method - Geekflare

MoSCoW: Framework for Effective Prioritization | craft.io

The project manager is the stakeholder who must approve the business analysis approach to ensure that it is compatible with the other project activities. The project manager is responsible for overseeing the project execution, managing the project resources, and ensuring that the project meets its objectives, scope, schedule, and budget. The project manager also coordinates the work of the project team, including the business analyst, and ensures alignment between the project management approach and the business analysis approach. The project manager needs to approve the business analysis approach to ensure that it supports the project goals, fits the project constraints, and does not conflict with the project plan. The project manager also needs to monitor and control the business analysis activities and deliverables throughout the project lifecycle. The project manager and the business analyst should collaborate closely to define and document the business analysis approach, as well as to communicate and manage changes to the approach as needed1234. References: 1: How to Choose the Right Business Analysis Approach1 2: Business analysis approach planning2 3: Approve Requirements3 4: Defining the Business Analysis Approach in 20235

According to the Wikipedia article on requirements traceability1, tracing a requirement means to follow the life of a requirement in both a forwards and backwards direction, from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration. Tracing a requirement helps to ensure that the requirement is linked to a business objective, that it is consistent and aligned with other requirements and deliverables, and that it is verified and validated by the stakeholders. Tracing a requirement can also help to identify the impact of changes, the source of defects, and the gaps in the requirements.

Option A is incorrect because it does not mention the business requirements, which are the high-level needs and objectives of the organization or the customer. Option C is incorrect because it does not mention the stakeholder and solution requirements, which are the detailed and specific requirements that define the scope and functionality of the solution. Option D is incorrect because it describes tracking a requirement, not tracing a requirement. Tracking a requirement means to monitor the progress and status of a requirement throughout the project lifecycle, not to link it to other related artifacts.

 Focus groups are a type of requirements elicitation activity that involve gathering a group of stakeholders from different perspectives and backgrounds to discuss a specific topic or issue. Focus groups can help to identify the ideas and attitudes of the stakeholders about the current situation, the desired outcomes, the problems, the solutions, and the actions needed to improve the service. Focus groups can also help to generate new ideas, uncover hidden needs, and reveal conflicting opinions. Focus groups are facilitated by a moderator who guides the discussion, asks open-ended questions, and encourages participation from all members. Focus groups are usually recorded and analyzed to extract the key findings and requirements1234. References: 1: Software Engineering | Requirements Elicitation - GeeksforGeeks 2: A Review of Fundamental Tasks in Requirements Elicitation 3: Top 10 Most Common Requirements Elicitation Techniques 4: 20 Tips for Effective Requirements Elicitation | Inflectra