Conflicting requirements

[ramram130od659]

Because requirements are often collected through meetings with separate groups of users, it isn't uncommon for them to give conflicting requirements. These conflicts must be resolved prior to implementation. For example, a salesperson says that they need to be able to offer a discount when they send a proposal. However, the sales managers said that they must approve all deals. In this example, the two requirements could be compatible, but without getting clarification, you would need to make some assumptions about it being acceptable to defer sending until it's approved. Typically, the more clarity that you have, the fewer assumptions will lead to a more successful implementation and less rework.

jboss training courses malaysia

[vapofi1331c9cd]

Conflicting requirements often arise when different user groups provide their input, as seen in the example with the salesperson and sales manager. To avoid issues during implementation, it’s essential to clarify such conflicts upfront. Explore here how the salesperson’s need for offering a discount and the sales manager’s requirement for approval could be aligned—perhaps by allowing the salesperson to propose a discount but deferring the actual sending until it’s approved. By resolving conflicts and ensuring clarity from the start, you reduce assumptions, which leads to a more successful implementation and minimizes the risk of rework later on.