A system owner calls the project team to inquire about a recent change in one of the requirements, and insists that the change was never requested. What should the project team do to investigate the…

The correct answer is D. Check the audit history of changes. According to the Capability in Business AnalysisTM (CCBA? guidelines, one of the tasks that business analysts perform in the requirement management and communication activity is to maintain the requirements, which includes tracking and documenting the changes and updates to the…

Requirements Life Cycle Management

Question

A system owner calls the project team to inquire about a recent change in one of the requirements, and insists that the change was never requested. What should the project team do to investigate the issue?

Options

ARecord a defect for fixing
BConsult with the project manager
CRevert back the changes
DCheck the audit history of changes

How the community answered

(33 responses)

B
6% (2)
C
3% (1)
D
91% (30)

Explanation

According to the Capability in Business AnalysisTM (CCBA? guidelines, one of the tasks that business analysts perform in the requirement management and communication activity is to maintain the requirements, which includes tracking and documenting the changes and updates to the requirements12. An audit history of changes is a tool that helps the business analysts to record and review the changes that have been made to the requirements, including the date, time, author, and reason for each change34. An audit history of changes can help the project team to investigate the issue when a system owner calls to inquire about a recent change in one of the requirements, as it can show who requested the change, when it was approved, and how it was communicated to the stakeholders.

Topics

#audit trail#requirements change management#change tracking#requirements control

Community Discussion

No community discussion yet for this question.

Full CCBA Practice