In the arguments over agile versus traditional approaches to software development, Business Analysis (BA) has sometimes been ignored - as the elimination of a formal BA position is sometimes confused with elimination of the practice of business analysis and a reduced emphasis on formal documentation is confused with the remaining need to perform the analysis behind it. As a result, the product backlog is loaded with items that are noted inconsistently, are difficult to reconcile with over-arching business goals and difficult to estimate and prioritize. The truth is - agile projects, with their increased emphasis on communication between developers and the business side, depend more heavily than ever on individuals (whatever their job title) who know how to structure their conversations with stakeholders for maximum benefit, individuals who are able to pull the right analysis techniques out of their ‘back pockets’ when they need them. In this Track, Howard Podeswa, author of 2 leading works on Business Analysis The Business Analyst’s Handbook and UML for the IT Business Analyst makes the case for reintroducing Business Analysis into the agile stream by providing a detailed, nuts and bolts discussion of best techniques for conducting conversations with users to elicit an appropriately comprehensive understanding of business goals and requirements.