It is sad but true that most Business Analysts justify their existance on a project by generating lots of documentation. And the more the better.
When someone asks what a business analyst does. Normally the answer is "Writes the functional Spec." Even though this revered document is normally never read by anyone apart from the "Project Analyst" working for the business who demands several rewrites to justify their own existence. Check out NerdHerding for a fairly accurate description of what happens on an IT project.
The business coach focuses on developing the domain knowledge of the project team. When someone asks what a Business Coach does, the answer should be "I don't know but they did something pretty cool because the developers can understand what the business are talking about."
Do not justify your existence by writing pointless documents. Do something worthwhile and develop the team instead.
Posted by chrismatts at June 5, 2004 3:33 PMHi Chris,
Another way of looking at this is that
(a) many business or systems analysts think lots of documentation is good.
(b) even if they don't they get beaten around the head with a methodology manual (which isn't light) if they don't produce lots.
(c) they have no idea what the alternatives are.
Sometimes it's justification, but many times it's just that they feel they have no other choice.
You've been busy today. Keep it up. You make me think.
Clarke
Posted by: Clarke Ching at June 5, 2004 5:23 PM