Agile methods are gaining in popularity and are steadily being adopted by more and more organisations.
However most agile methods provide very little guidance on how requirements are to be gathered and managed and who should be responsible for this activity. Many organisations struggle to define the role of the Business Analyst in agile methods and in some extreme cases the need for the Business Analyst role is challenged. The reality is that effectively including the Business Analyst role as part of an agile team greatly reduces project risk.
In this session we provide an overview of agile methods from the perspective of the Business Analyst and identify some of the challenges involved in agile. Real world issues that arise when using agile requirements techniques are identified and examined. Finally we present a number of proven methods for successfully incorporating the Business Analyst role into an agile project environment.
Learning Objectives
- Explore how Agile methods impact on the traditional role of the business analyst
- Understand some of the common requirements related issues that occur on Agile projects
- Review a number of proven techniques for successfully incorporating the Business Analyst role into agile projects
|
Mark Foley
Asia-Pacific Principal Consultant
Borland Software Corporation
Mark Foley is the Principal Consultant for Borland Asia-Pacific. Mark works with organisations across the region to help them improve the outcomes of their software delivery efforts through the application of improved processes, skills development and Borland technology. Mark's focus areas include requirements engineering and software testing.
Over the last 18 months Mark has had the oppoertunity to work with a number of organisations adopting agile methods (including Borland itself) and has observed first-hand the good, bad and ugly of such a transition.
|