During the testing phase, a new requirement surfaced and the stakeholder asked the developer to modify the code without informing the business analyst (BA).
The BA became aware of the new functionality after a defect was raised against another component of the design. The BA can keep this situation from occurring in the future by creating a:
To prevent unapproved changes and ensure all stakeholders, including the business analyst, are aware of modifications, it is critical to create a change control process. This process will outline how changes are proposed, reviewed, approved, or declined, and ensure that all relevant parties are informed and part of the decision-making process.
Option B- Change control process - Determine how changes will be communicated: how proposed changes, changes under review, and approved, declined, or deferred changes will be communicated to stakeholders.