IIBA CCBA Practice Test - Questions Answers, Page 10

Prioritization of requirements is used to make certain that analysis and implementation efforts focus on the most critical requirements. The requirement prioritization process ranks the requirements by importance. It is a decision process. This process is used for determining the relative importance of requirements. These priorities determine which requirements should be targets for further analysis.

Answer C is incorrect. Requirements prioritization does not rank the requirements by the stakeholders, but by the needs of the stakeholders and the requirements that are most important to satisfy those needs.

Answer A is incorrect. Requirements prioritization does not rank the requirements according to the cost and schedule, but by importance.

Answer B is incorrect. Requirements prioritization does not rank the requirements on a weighted scale; this isn't a valid statement.

In order to use the matrix documentation approach to model requirements, the identified requirements must have the uniform structure of their characteristics and identification.

Answer A is incorrect. The requirements do no need to have opposing values to use the matrix documentation approach.

Answer B is incorrect. While this choice is tempting, the best answer is the uniform structure.

Answer D is incorrect. This isn't a valid answer, as requirements don't need rated goals.

Six Sigma is a business management strategy originally developed by Motorola, USA in 1986. It is widely used in many sectors of industry, although its use is not without controversy. The Six Sigma approach seeks to improve the quality of process outputs by identifying and removing the causes of defects (errors) and minimizing variability in manufacturing and business processes. It uses a set of quality management methods, including statistical methods, and creates a special infrastructure of people within the organization who are experts in these methods. Each Six Sigma project carried out within an organization follows a defined sequence of steps and has quantified financial targets.

The Requirements Management and Communication knowledge area describes the activities and considerations to manage and express requirements to a broad and diverse audience. The execution of these tasks ensures the following facts:

The stakeholders have a shared understanding of the nature of a solution.

Those stakeholders with approval authority are in agreement as to the requirements that the solution shall meet.

Answer B, A, and C are incorrect. The Enterprise Analysis knowledge area describes the following business analysis activities:

It identifies business needs, problems, or opportunities. It defines the nature of a solution that meets that need.

It justifies the investment necessary to deliver that solution.

Assumptions and constraints are identified through elicitation from stakeholders.

Answer D is incorrect. Assumptions and constraints are not identified through document analysis.

Answer C is incorrect. Assumptions and constraints are not identified through risk identification, though false assumptions may be subject to risk analysis.

Answer A is incorrect. Assumptions and constraints are not identified through a review of project requirements.

The work breakdown structure (WBS) is a tool used to define the scope of work and to develop estimates. This tool creates a hierarchy of work by decomposing the project scope into smaller and smaller pieces. WBS can perform the following tasks:

It may break the project into iterations, releases, or phases. It can break deliverables into work packages.

It may break activities into smaller tasks.

Answer C, A, and D are incorrect. The inputs to requirements management and communication are as follows:

Business Analysis (BA) communication plan Requirement Management Plan Solution Scope Requirements Structure Organizational Process Assets Stakeholder, List, Roles, and Responsibilities Requirements

The Identify Stakeholders process identifies all people or organizations that are impacted by the project. It also documents relevant information regarding their interests, involvement, and impact on project success.

Stakeholder register and stakeholder management strategy are outputs of this process. Answer B is incorrect. Project charter is one of the inputs of the Identify Stakeholders process.

Answer A is incorrect. Scope baseline is one of the outputs of the Create Work Breakdown Structure (WBS) process.

Answer D is incorrect. Project scope statement is one of the outputs of the Define Scope process.

The author of the requirements is a good attribute to include in the requirements attribute. This allows follow- up Questions or clarifications, if necessary, for the project.

Answer A is incorrect. Absolute reference is needed to define specific requirements. A numeric coding is preferred over text and this code should not be reused.

Answer B is incorrect. The ownership attribute describes who will be the owner of the requirement or deliverable. The owner isn't necessarily the same person who created the requirement.

Answer C is incorrect. There is not an attribute called requirements sponsor, so this choice is not valid.

Only the business analyst is involved in the documentation of the elicitation results.

Answer D is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not the project manager and project sponsor.

Answer C is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not the project manager and project team.

Answer A is incorrect. Only the business analyst is involved in the documentation of the elicitation results, not key stakeholders.