how to handle conflicting requirements

Hi BABCT,

Currently I’m running into the trouble that the customer is not available:( He is so fully occupied with the internal stuffs. And I have tons of unclear requirements waiting to be confirmed with him.

It seems there is no way to get him.

Also, the system is pretty large, so we divide into 2 groups and develop in parallel.

Hence there might be some functions that overlap each other.

Whenever the 2 parts get merged, a lot of conflicts and duplicates need to be cleared, which is really really a big headache.

Looking forward to your answers.

If You Enjoyed Reading This Post ... Subscribe To Business Analysts Boot Camp Newsletter ... It Is Free »


One Response to "how to handle conflicting requirements"

  1. Business Analysts Training   May 9, 2011 at 9:04 PM

    First, everyone on your team has to have the same understanding of what constitutes a good business requirement or what doesn’t.

    So, you have to learn: ” How To Write Good Business Requirements “! A good business requirements is:

    • A good business requirement is: Feasible

    • A good business requirement is: Verifiable

    • A good business requirement is: Traceable

    • A good business requirement is: Consistent

    • A good business requirement is: Complete

    • A good business requirement is: Unambiguous

    • A good business requirement is: Necessary

    Here is a detailed article on this titled: “How To Write Good Business Requirements”

    Reply

Leave a Reply

Your email address will not be published.