Request value of requirements/features, aides prioritization and identifying alternatives Discuss and document customer's why Document gestures per task and max time per task: user productivity Avoid discussing solution/how as it moves conversation from customer's domain to developer's Fast, responsive, and extensible are not requirements because they aren't quantifiable Criteria are objective with thresholds Non-functional requirements like performance should be specified early and tested and tracked early (baselined) and throughout the project Clarify and Document Constraints Clarify, Document, Reduce and Manage Scope Prioritize and build most important features first Divide and conquer - breakup, parallelize, and design/implement smaller features whenever possible Document and track risks, i.e., the same as bugs update the status as risks are mitigated