Thank you for a description of what a BA role is.

Personally I can see point three taken too literally:

“Proactively communicate and collaborate with external and internal customers to analyze information needs and functional requirements and deliver the following artifacts as needed: (Functional requirements (Business Requirements Document), iii. Use Cases, GUI, Screen and Interface designs)”

with BA’s thinking it is their responsibility to create the GUI and interface designs.

What I think is lacking in the definition is the distinction between finding out what is required and designing how that is implemented and which part of that is in the role/responsibilities of the BA and which is not.

Do you think the role of the BA is to design “HOW” a system will do what it does?

I find the “HOW” creeps in whenever the requirements take the form “The System shall…” rather than “It is required that …”.

What do you think ?

Rgs,James.

BTW- I posted this comment to Mike’s site too, since Im *very* interested in resposnes.

A while ago I surveyed BA job descriptions and broke down the cmpetencies they were looking for. There is a pie graph at the other end of this link.
(You’ll need to scroll down)

Oh, I’ve fixed your link, too. Sorry about that!

Thanks for the kind words. I appreciate the feedback. For me, providing this kind of service is what it will take for us to become strategic and go beyond just being order takers.

By the way, the link to the article is actually http://mikeschaffner.typepad.com/michael_schaffner/2007/02/lets_get_down_t.html#more

You inadvertently used the trackback link instead of the permalink.

Thanks,

Mike Schaffner
http://www.mwschaffner.com