Often a Business Analyst (BA) gets branded as being a bad analyst as a result of a project effort that has gone astray. Fortunately most of the time it is not the fault of the BA, but rather the project to which they have been assigned. This could be the result of any or all of the following situations.
Project Objectives
Problem: One of the first problems encountered is being assigned to a project which has unclear objectives or simply an idea or concept in the head of management (not to mention "objectives/management by airplane magazine articles"). In trying to determine the scope, objectives or real reason for initiating the project, the BA may appear to be struggling or confused, when in fact the confusion originated at the top. Often these projects are unofficially entitled "Top Management's Pet Project(s)."
One of the more controversial techniques fostered by some in the agile community is 'Pair Programming'. It is a practice that originates from 
Lately I've been getting questions from Agile seminar participants about how to apply Scrum to "real life," as though these methods are "good in theory, but not at my company!" Some organizations may not be ready to adopt agile methods completely, so I encourage students to take an organizational readiness self-assessment to see if Agile in general and Scrum in particular is right for them. The questions on the self-assessment can be used to begin conversations as a way to raise issues that need to be resolved in organizations thinking about adopting Scrum.