22 September 2010 The development team should ask WHY a lot in order to: Discover business rules that might not have been discussed previously Surface assumptions held by the stakeholder or identify conflicting assumptions held by different stakeholders Reveal implicate requirements not yet discussed Identify the needs behind the requirements Uncover priority in the requirements that can be overlooked by the design team Distinguish between essential knowledge vs.
{}