Too often when IT consultants receive requirements for new features they aren't requirements at all. At least, they are not defined as requirements. In most cases when identifying the problem the customer is likely to find a "solution" which is often what they presents as requirements.

In my talk I will share personal experience on projects where badly defined requirements have had a negative impact on deadlines, budgets and most importantly customer satisfaction. I will underline what to look for when investigating functional and non-functional requirements. We will glance over the attributes that completes a requirement. We will understand how to ensure a testable requirement for successful implementation.