I find myself running into a lot of business analysis professionals who say, “I don’t do data analysis. That is the data architect’s job.” My response: “…What?!?!”
In a nutshell, a good business analysis professional knows that part of their role is to understand the business and help the business solve its problems by making sure their business processes and rules are correctly implemented in a solution.
Let’s Decompose
Ensure your business processes and rules are correctly implemented in a solution.
What is a business process?
A process takes inputs (also known as data!) and adds value to them via some identified activities to generate outputs (also known as data!). A business process is an activity or set of steps that the business needs to perform in order to be successful. Let’s consider a project to provide a solution for a grocery store business.
A business process for the grocery stores, for example, might be “Capture Customer Payment,” which would occur when the customer checks-out at the register or online. To understand what the business should accomplish in this process we would need to understand what data is used to complete it. Total of products purchased, taxes charged or coupons to apply might be examples of some of that data. If we do not understand these data items and ensure they are delivered in the solution developed, we probably will have gaps and errors. And the customer would not be too happy if we calculated their total, taxes, or coupons incorrectly. I probably would not continue to shop in a store if I knew their calculations of what I am paying for is incorrect.
What are business rules?
They are the constraints a business implements in order to be successful. They tell us how, logically, to manipulate the data so that the business process is completed correctly. Continuing with the grocery store project, a business rule might be, “If the store is in any US state except Alabama, Mississippi, or South Dakota and the product is a food product, then no sales tax is applied.” In order to implement this business rule correctly, we need to understand what is considered a “food product” and what the term “sales tax” means. Also, is the coupon within date and item being purchased applicable? These are data items. If we misunderstand these data items, we will have errors and or gaps in the solution we are delivering.
What is a solution?
In an IT environment, solutions usually involve an information system and the users and workflows involved in using the system. Typically, an IT solution combines automated and manual components to deliver a complete solution to the problem. For grocery stories, this might be the point-of-sale system that combines the manual and automated processes needed for the customer to check-out. A solution can also be purely manual and not have to involve IT at all. For example, the process of selecting grocery items from a brick-and-mortar store and placing them in a physical shopping cart.
No matter what the solution includes, whether manual, automated, or a combination, it will still involve business processes and therefore involve business rules and business data. To leave out a third of that (the data), we risk delivering a solution that does not solve the problem. That is a big risk!
What is an information system?
It pulls and pushes data (the term “information system” contains the word information, and information is data). A good information system provides timely, correct data about the business so that the business can make decisions that will drive its success. Once again, if we as business analysts do not understand the data contained in the system, how do we know that the system fulfills the business need?
What is at the core of all of this?
Data.
Without correct, timely data, a business will not have the ability to make good business decisions. Period…end of story. It may not be the whole story, but I think it is the punch line, so missing that would be missing the target.
In my experience, a deep, clear understanding of the information that a business uses and the relationships between that information is the best way to really understand the business. Processes can and do change, but data is relatively stable. If you understand the data a business uses to run itself, you can really get a good understanding of that business and enable the business to better understand itself and what it does.
What can you do as a business analysis professional to get a good understanding of the data a business uses?
4 Step Process to Performing Data Analysis
1
In project scoping, I make sure I understand all of the project’s interactions with the ‘outside world’.
This means identifying all interfaces we think are going to be necessary for the solution to work. To help me and the project executives understand these interactions, I typically build a context (dataflow) diagram. This diagram is a great high-level picture of the complexity of the data interactions on a project. It gives me the original sources of the information that the solution will need to run effectively, as well as the final destination of the data that the solution will produce. These sources and destinations will have stakeholders from whom I will need to elicit more details.
Learn how to build a Context Diagram in our Essential Skills for Business Analysis class.
2
Also in project scoping, I identify the high-level business capabilities that the project will be affecting or creating.
This gives me a good idea of how many lower-level processes will be affected and how complicated they appear to be. For those processes that seem complex, I break them down into the activities or tasks that make them up so that I have a better idea of how to estimate effort.
3
Having analyzed the processes and context diagram from steps 1 and 2, I now have a great picture of the processes and data I’ll need to get more detail on and the stakeholders from whom I need to elicit the details.
4
As I begin analyzing the processes and data flows from steps 1 and 2, I also start to build my data model.
I use the time-honored technique of using an Entity Relationship Diagram (ERD) to see the data entities with their detailed data and relationships. The data relationships are hugely important as they are the data business rules that drive your business. Asking good questions about the data will bring out business rules that might be missed if you just concentrate on the process workflow. As more questions are raised and answered, the data model becomes robust and complete. It also gets us thinking about that “Big Data”. What ELSE do I need to know about my business to help it market, sell, and produce the products that will make it more successful? How do I relate all that ‘stuff’ together so that we can diagnose problems and predict demand? A deep understanding of that data helps with those important questions.
Our Entity and Attribute Metadata templates are a good way to capture and share this information.
In my projects, I always ensure that we have a good understanding of the system interfaces that will be involved in the solution. Those interfaces contain business data, so we need to validate that the data passing through system interfaces is complete and correct.
What is the result?
You end up with a full, deep, clear understanding of the data on which the business runs. You ensure that the data architect now has the information needed to build an efficient, effective database that contains the data and relationships to match the business needs. The business areas in which you are working end up with a better understanding of what they do. Additionally, you move beyond the BA that is just an order-taker and become a valuable, crucial part of the project and the organization as a whole.
I challenge and encourage you to become a business analyst that DOES do data!
To the data,
– Ali
Editor’s Note: This blog post was previously published by B2T on our previous website. Due to its popularity, Ali has updated its content to be more comprehensive and accurate for the state of today’s environment.
Ali Cox
LEAD EXPERT
Alison (Ali) Cox has experience since the mid-1980s in various areas, including business agility, business analysis, project methodology development and training, systems development (mainframe, client-server, and web), and telecommunication expense management. She began her career in the financial services area, and then moved into systems development for accounting systems.
Ali has lived through IT and operational initiatives from waterfall to implementing agile in her own small business, then helping other companies do the same through training and mentoring. She believes that having the small business mentality (everyone has to pitch in on everything) is the right kind of mindset for all organizations, no matter the size or industry.
Ali is the author of Business Analysis for Dummies, 2nd Edition.
