Free CCBA Exam Braindumps
Certification of Competency in Business Analysis Questions 271–275 (page: 56)

Updated On: 9-Feb-2026

Which of the following documents graphically depicts the project team members and displays their interrelationship for a specific project?

  1. Project team directory
  2. Project organization chart
  3. Project scope statement
  4. Project charter

Answer(s): B

Explanation:

Project organization chart is a document that graphically portrays the team members of the project and their interrelationships for a specific project. An organization chart is a diagram that shows the hierarchical structure of an organization. Usually a chart starts with a higher or superior level and branches downward to subordinate levels.
Answer D is incorrect. The project charter is the document that formally authorizes a project. The project charter provides the project manager with the authority to apply organizational resources to project activities. Answer A is incorrect. It is a documented list of project team members, their project roles, and communication information.

Answer C is incorrect. Project scope statement is the narrative description of the project scope. It includes major deliverables, project assumptions, project constraints, and a description of work. It helps developing a common understanding of project scope among the stakeholders. It is a documented description of the project to answer Questions such as What is being produced? How is it being produced? What is included? etc.



What does MoSCoW mean when it comes to requirements prioritization?

  1. Must, Should, Could, Would
  2. Money, Schedule, Control, Waiting
  3. Must, Should, Could, Won't
  4. Mustn't, Shouldn't, Couldn't, Won't

Answer(s): C

Explanation:

The MoSCoW Analysis approach allows requirements to filter into the four categories of must, should, could, won't.
Answer A is incorrect. This isn't the correct definition of MoSCow; the correct definition is must, should, could, won't.
Answer D is incorrect. This isn't the correct definition of MoSCow; the correct definition is must, should, could, won't.
Answer B is incorrect. This isn't the correct definition of MoSCow; the correct definition is must, should, could, won't.



A business analyst is meeting with the customer of the project. The customer tells the business analyst that she can only allow the budget of $575,000 for the project. This budget is best described as what type of constraint?

  1. Technical constraint
  2. Verified constraint
  3. Financial constraint
  4. Business constraint

Answer(s): D

Explanation:

A business constraint describes the limitations on the available solution - including financial, schedule, and resource limitations.
Answer C is incorrect. Financial constraint is not a category of business analysis constraints and assumptions. Answer A is incorrect. A technical constraint describes an architectural decision that may affect the allowed solution, such as development language, hardware, or software.

Answer B is incorrect. There's not a category of constraints called a verified constraint.



You are the business analyst for your organization and you're working with Adam on business analysis processes. Adam allows the business analysis activities and resources to exist in support of the organization. Of the following, what type of business analysis stakeholder is Adam?

  1. Project manager
  2. Domain subject matter expert
  3. Sponsor
  4. Regulator

Answer(s): C

Explanation:

Adam is the sponsor. The sponsor allows the business analysis activities and resources to exist in support of the organization.
Answer B is incorrect. The domain subject matter expert is a person who is steeped in knowledge regarding the project's purpose.
Answer A is incorrect. The project manager must ensure that the business analysis approach is compatible with other project activities.
Answer D is incorrect. The regulator approves any tailoring to the business analysis processes or activities.



According to the book 'A Guide to the Business Analysis Body of Knowledge', effective business analysis practices can do what to the amount of change to requirements in a stable business environment?

  1. Reduce the amount of change, but not eliminate entirely.
  2. Document the changes to requirements.
  3. Control the frequency of the change.
  4. Eliminate the change entirely.

Answer(s): A

Explanation:

Effective business analysis practices can reduce the amount of change in a project, but it cannot eliminate the amount of changes entirely.
Answer D is incorrect. This isn't a valid statement as business analysis practices cannot eliminate the need for change in requirements.
Answer C is incorrect.
While this may be true in some instances, it's not true for all areas of requirements change.

Answer B is incorrect. This isn't a valid statement to the Question. All changes and requirements must be documented.



Viewing page 56 of 104
Viewing questions 276 - 280 out of 638 questions


Post your Comments and Discuss IIBA CCBA exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!