As Adrian mentioned, some BAs are focused solely on documenting and improving the manual business processes and operations while others are more focused on implementing IT solutions that make these processes more efficient. And then there are those that fall in between and do a bit of both. You will have to decide where you fit best. This is a big topic, so I will first comment on the non-IT related aspect. Then in a follow-up post I can take you into the systems side of things.
We should approach your question in three parts. First, I will list some of the high level tasks a BA may perform. You should take the time to understand and contemplate these. Then, we have to identify and relate your work experience to those types of tasks. You will have to assist with this since I don’t have any knowledge of your work experience. Finally, I will list a few skills/techniques that you should probably acquire. This will give you the tools required to perform in the role of a BA.
Tasks a BA may perform (not comprehensive)
Document the business workflows/processes as they exist today: Understand the processes the business uses to bring value to there customer, the things of the business that are needed or used in these processes, and the data or information that flows between processes. The processes are documented using a process flow diagram. The things of the business can be a simple business glossary of terms with their definitions or it can be a more complicated but richer business entity model. The goal here is to create a commonly understood vocabulary among all involved. You would be surprised how often people think they are speaking the same language only to find out far too late that they are not. The data and information can be modeled using a data flow diagram and also by adding attributes to a business entity model. Don’t get too worried about these terms if they seem foreign. The Modern Analyst community is here to help and mentor!
You may have heard of the term use cases. I have not mentioned them only because they convey the same information as a process flow diagram, but in a narrative format like telling a story. They are typically used later when a systems solution is involved. I’m trying to prioritize and focus you attention on the most basic items at the moment.
Analyze the business workflows/processes and identify possible improvements: Now that you understand the details of the business workflows and processes (the operations of the business), try to identify process complexity that can be simplified. Complexity costs money and creates errors, defects, or general problems within the organization. Begin to visualize and document how these areas that you have identified can be improved. Document the improved process using the same tools/diagrams you used to document the current state of the business, i.e., process flows, data flow diagrams, edits to business glossary or business entity model. Often you may document more that one possible improvement to the same area of the process which is great.
Compare options and weigh cost of each versus benefits of each: Now that you have several options for improving the process, address the feasibility of each. Are they all realistic? May be some are not. Try to estimate the monetary benefits of the improvement. How many defects will you eliminate per week, or how much rework/redundant work will be eliminated? Can positions be eliminated? What is the dollar savings of this? Then identify the costs. How much will it cost to make these changes and improvements? What is the risk involved? Every risk has an associated cost if it develops into a real issue. So what is the cost and what is the probability that it can occur? Use all of this information to create a nicely organized Cost Benefit Analysis report.
One you have completed this work the decision makers can choose a direction.
While this is very high level and not at all comprehensive, it’s enough to move on and identify how much of this you may have experience with, even if informally.
Relating your work experience to those tasks
This is the part that I need you to help with. How much of the above have you done? Remember, it doesn’t have to be a formal project and you may not have created process flows and the like, but you still probably have some experience with the BA tasks in general. Also, if you’d like you can email me your resume and I will try and help identify areas where you may have “hidden” experience.
Skills to acquire (We will refine this list based on your current skills and the responses you give.)
-
Read the IIBA Business Analyst Book of Knowledge (version 1.6 is available for free download at their site www.theIIBA.org)
-
Learn to create a Process Flow Diagram (using BPMN Workflow Diagrams or UML Activity Diagrams)
-
Read up on the advantages of a Logical Data Dictionary or Business Glossary (there is an article on the Modern Analyst site on this. Also search the web)
-
Understand how to create a Cost Benefit Analysis
-
Understand how to create a Risk Assessment, taking into account both the associated cost of a risk and its probability of occurring. Decision Trees are helpful for this.
-
Learn to create a Data Flow Diagram and Context Diagram (don’t focus on this first, this is not as high of a priority)
-
Learn to create a Business Entity Model (don’t focus on this first, this is not as high of a priority)
I will list some additional skills in future posts for systems analysis; items such as requirements elicitation