Hi Michael

The company I work for is looking into using Scrum for some project work so the role of the BSA in this agile approach is something i'm keen to learn also.  Agile (or scrum) tries to generalize roles rather than a specific one. 

I've yet to come across any books which detail the role of the BSA in this approach but have found the following site to be a bit of an eye opener: http://www.agilemodeling.com/essays/businessAnalysts.htm#OneRoom.  It also has one which relates to documentation (part of my BSA role): http://www.agilemodeling.com/essays/agileDocumentationBestPractices.htm.

I think my work wish the BSA ro produce (or assist in producing) User Stories and Use Cases.

Are you part of a project/company which is using agile?  I'd be interested to know your thoughts...

Thanks :o)

Hi All,

I would like to recommend "Agile Software Development: The Cooperative Game (2nd Edition)" by Alistair Cockburn.

It's good start because of 2 reasons:
    * It's small book
    * Great author who know what to write

His great words are "Each project should have its own methodology" can be replaced by "Each project and team should have its own methodology"

Any time you should balance among knowledge keeping (requirements and architecture) and agility (code as fast as possible). Alistair says he saw heavy weight and too agile projects which were failed. And only you as the professional can choose right one.

Actually Agile methodology is a set of practice that you can apply with almost any heavy weight methodology. You can google by Agile RUP and find many interesting articles.  Any more you can have a look at AUP.

In conclusion you even can google by Agile CMMI :)