Agile Requirements at the Speed of Thought
From Word docs to wikis. Use cases to story cards. Shall statements to user stories. How do requirements change in a world of agile development methods? The real goal of project managers, business analysts, developers, and users is project success. Understanding what users need is, and always will be, crucial to any software.
How, then, can business analysts work within agile methodologies and help them succeed? What do requirements look like without all of the overhead? What is the right balance between agility and rigidity? This presentation will answer these questions and provide tips and techniques analysts can use to add value in an agile world. After the introduction, audience members will participate in a highly educational and fun activity in which they will build Lego helicopters with varying levels of detailed requirements.
Mike Alexander has been involved with requirements management for the past ten years. Mike has gathered, documented and managed requirements for a wide range of systems, including those used by researchers, consultants, teachers, students, financial analysts, physicians, and retail buyers. Additionally, he has managed teams of requirements engineers, defined and implemented requirements management practices, and been a consumer of requirements documentation as a QA Manager and DBA. Mike’s educational background combines undergraduate studies in English with graduate work in information science, usability and human-computer interaction. He is a Senior Product Manager with Seilevel in Austin, Texas.