A business analyst (BA) has completed requirements elicitation and modelling on a project to implement a new case management system. During analysis of the requirements, the BA notices that one of the requirements appears to be in conflict with the company's case management policies. What should the BA do?
When the business analyst identifies a conflict between a requirement and the company's case management policies, it is crucial to address the potential issue at a higher level rather than making unilateral changes. Identifying the policies as a potential constraint and reviewing them with management ensures that the conflict is properly evaluated and resolved. This process involves key stakeholders and ensures that any required changes maintain alignment with the company's policies and strategic objectives, fostering proper governance and decision-making.
C is correct- B is wrong because a BA cant modify the requirement of his/her own. Other options are far away
Ans C BABOK V-3 6.1.4.5 Analyze Current State: Policies -Policies define the scope of decision making at different levels of an enterprise. They generally address routine operations rather than strategic change. They ensure that decisions are made correctly, provide guidance to staff on permitted and appropriate behavior and actions, support governance, and determine when and how new resources can be acquired. Identification of relevant policies may shape the scope of the solution space and may be a constraint on the types of action that can be pursued.
Identify the policies as a potential constraint and review with management is correct. By identifying the policies as a potential constraint, the BA can raise awareness of the conflict and initiate a discussion with management to resolve it. This approach allows for a collaborative decision-making process, involving stakeholders who have the authority to address policy conflicts.
Modifying requirements to align with policies have various other negative consequences as follows: * Compromising Project Objectives: The modified requirements are not necessarily aligned with project objectives * No stakeholder's buy-in: The changes are proposed to requirements without buying-in consent from key stakeholders. This may challenge the project's acceptance.