cbybe

Respond ….100 min…..

In order to determine what action should be taken to resolve conflicting requirements, the analyst must first determine the root cause of the conflict. The causes of conflicting requirements are typically the same, time and time again. Here are a couple of the more typical causes and how you might deal with them. One or more of the stakeholders/groups misunderstand the higher level divisional or company goals which are driving their specific requirement. This leads them to push for a process or system requirement that is not in line with the true needs of the business.

Take some time to step back and level set everyone on the overall business case for the project. Set up a meeting to discuss the project/business goals. Avoid taking an approach of telling them in the meeting what the goals are, but instead ask the conflicting stakeholders/groups to reiterate the higher-level goals themselves. It will quickly become apparent that not everyone is on the same page. Open conversation can then take place to gain consensus around the actual project goals. If necessary, the group can go back to a project executive or sponsor for clarification.

 

Reference:

Semeniuk, M. (2010). Techniques for managing conflicting expectations.