I saw the thread the Good BA and thought it might be interesteting to discuss what makes a bad BA.  Here are a couple of thoughts from me and I look forwad to other people's points of view.

A bad BA...

• Is focused on communication via documents
• Assumes knowledge of the business and dictates requirements to the stakeholders
• Knows the solution before the problem is generally agreed
• Addresses the technical problem space but doesn't deal with managing people through change
• Is managing their work to the objectives of the project manager, rather than the project sponsor or client

More?

A bad Business Analyst:

• has poor communication skills,
• does not know how to listen,
• lacks analytical skills,
• is not a facilitator,
• gets lost in the details,
• does not have many "tools" in the toolbox,
• stopped learning a long time ago
• hates being a BA and is in it only for the money.

A bad BA is a very enthusiastic person, performs few sessions with the client, consumes a lot of time analyzing the requirements depending on his own logic, develops his idea based on standards and optimal work and ... forgets what the client currently really needs!

wishes