Tankfish,

You might want to have a look at the Fundamentals of Business Analysis for a short article on the subject or the IIBA BABOK and framework for a more wide ranging view.

There's also this picture I drew that tries to sum up the scope and tasks of the Business Analyst role which is colour coded (blue = non-BA role the BA works with, black = what needs to be done and red= what the BA should be doing)...:bear in mind that this covers the information you need and that it is an ideal statement. So (for example) a BA needs the measures of success defined by the owners (people who can sanction or stop the project) and ideally should do the work with the owners. In reality this often doesn't happen and the Programme/Project Manager does that work. It doesn't matter who actually does it so long as it is done to a sufficient standard that allows the BA to analyse requirements to deliver the measures of success.

Guy

Tank,

This depends very much on the task (project) at hand. You could be very unfortunate and find yourself working on an existing legacy system with the occassional change request (CR). Or you could be very fortunate and work on a greenfields project, where everything is new and the whole project is kicked-off with a proper "project brief".

The BABok is a good start.

A good business analyst should be across the following steps: Project initiation, Analysis and Design, Build, Test and Implementation. Depending on the methodology (Waterfall, iterative, agile etc.) used you'll be doing some of these steps. eg. Testing may involve user acceptance testing because if you can write requirements you or someone else should be able to test them.  Also, your impact analysis should higlight the implementation and training issues early in the piece.

Anyway, there is a good black and white movie out there called "The Dam Busters" (circa 1954) with Sir Michael Redgrave and Richard Todd. Your local video store might have a copy. Their "project brief" was to blow up the dams that supported some of the German Industry during WWII and thus shorten the war. Not a bad strategy.

Watch it and you'll see each of the above steps, especially keep an eye on the project initiation and analysis&design steps(keep an eye on the dog as well).

Enjoy! This may not be what you expected, but at least you get to watch a movie.

warm regards,

K