Following the lead of another forum, where the question was asked about the use of UML by Business Analysts, I would like to ask the same question when we come to Agile Analysis.

The answer is NOT simple and like all professional questions needs analysis. This means, I shall post a series of these blog pages, expanding one point at a time. I will NOT rush in and give you the answer now.

• Business Analysis is a coat of many colours:
  
  • It starts with the real business professional or consultant. They are masters of politics, hand waving and general waffle. Above all they speak 'Management speak' and that certainly does NOT include a solid diagramatic approach. They know that 'If a person has time to read a document, they are NOT a manager.' It is the members of this group who very often help make the decision to start a program of work on computer systems to meet some business. requirements. These are the people who read the documents aimed at managers. They are really Business Consultants.
  • Then there are Real Business Analysts. These guys map out how the business works and how to change it. BPR is a term I most often associate with them. Producing a spec for a software system is something they can do if the need arises. BPMN is probably central to the diagramatic aspects of their work. Costing floor space, business growth etc is as important They do NOT need two products doing the same job, so UML is one of the many methods they need to know about without needing to be able to use it.
  • Next comes the Computing Business Analyst. They analyse the business, including mapping Business Processes and identifying Business Requirements. They may also produce Business Requirements Documents, or respond to them with System Specifications, responses to tender. They work on the basis that if there is a relevant Business Process, it MUST be documented. This documentation is often very helpful to a person doing a full analysis of a Business requirement. They differ largely from the 'Real Business Analyst' in that they are brought onto a project in order to help create a new computer product; Real Business Analysts, are interested in how the business will respond to such a computer system, and the computing side is just a small part of their job.
  • Finally, there is the Business Systems Analyst, for whom the Business Process Diagram is a necessary evel that they may sometimes have to resort to. These are the guys who really should be using UML. They should define the requirements for the computer system and ensure that someone designs and builds them. This is also the group that will have the greatest trouble talking to the potential end users, the project sponsors and the senior management. 

These categories have been mapped out, just to show that the question is NOT a simple as it seems. You need to start with the definition of what or who a Business Analyst is. NO two BAs are ever the same. NO one BA ever does the same job twice. There are many shades of grey.

This changes the question from 'Should BAs use UML? into 'When should BAs use UML, if at all?

Finally, I will leave you with a thought for the next  page. 'Do Business Analysts ever Analyse?'

Gil