To learn best-practice lean and agile business analysis techniques, check out our new Udemy course, "Agile Business Analysis: Getting / Writing Lean Requirements" https://goo.gl/CZ5hMF. #BusinessAnalysis #UserStories #RequirementsDiscovery

Career prospects for Business Analysts (BA's) have been growing by leaps and bounds for many years. However, a new challenge has arisen. With the widespread adoption of Agile software development, the process of defining IT requirements is evolving rapidly. This video offers a brief overview of how you can adapt your Business Analysis practices to optimally support the new lean and agile software development world.

Agile teams now build robust products incrementally and iteratively, requiring fast feedback from the business community to define ongoing work. In Agile, Product Backlogs replace Requirements Definition Documents. User Stories, Epics and Features replace requirement statements. Scenarios and Examples replace test cases. The timing of Business Analysis activities is shifting like sand. Defining all requirements upfront, working in silos, and checking quality at the end no longer works. The bureaucracy that went with traditional Business Analysis is a death trap for any Agile initiative.