Business Analysis in Action

The actual journey of business analysis begins once we have a business case. The project gets started with the requirements gathering and analysis. However, the real action begins with the process improvement, and it goes through a series of stages until we roll out the product. In this article, I am trying to explain about different stages in Business Analysis and the actions performed within each stage in order to successfully complete a project.??

Note: This article focuses on a digital transformation journey rather than the analysis of improving or adding a new feature in an existing application.?

Process Improvement

In an ideal digital transformation journey, improving the process is critical and it is the stepping-stone to success. The current processes that a company follows should be improved as most of them would be outdated as there are technological advancements almost every decade. The focus should be on those outdated processes and to improve those. The output of a digitally transformed environment is a company that is following an improved process. There are different steps in process improvement. The goal of process improvement is to get an improved process map which can then be used to map the capabilities and features to support the development.?

Process Mapping?

As-Is/Current Processes?

Document all the as-is or the existing processes. It is better to start these processes on a very high level and then focus on sub-processes to a detailed level. Use a tool like BPMN to document the processes as it is well known and easy to understand. While documenting, the analyst should also focus on key areas that have delayed the process.??

Improvements Log?

Once you find the possible improvements required in the process, the next step is to document the improvements in an improvements log. This improvement log can be in excel which will help you track the improvements at a later stage.??

To-Be/Proposed Process?

With the help of the improvements log, we can then define the to-be or the future process that we must implement. While defining the to-be process, you should be able to visualize the output?

At the end of the process stage, you will be having a document with an improved process map, which can be used in the next stages to generate the capabilities and features required for the new application.?

Capabilities and Features Mapping

The capabilities and features mapping can be used for “reference” purposes. At the beginning of this stage, you would have visualized the output and be able to identify the capabilities required. Each step in the to-be processes can be analyzed and this will help you to create the capabilities required. These identified capabilities can be updated in excel along with the associated process for reference purposes. Once we list down the capabilities, we need to identify the features required against each identified capability. The feature should also be mapped with the process, and it is important to have an order based on the process flow. The benefit of identifying the capabilities and features allows you to take this into the solution design stage and makes it simple to design a solution as we already know what is required.?

Data Modeling

Once we have the features ready, it is time to evaluate and analyze each feature and see the fields that are required whilst identifying the required master and reference datasets. A good data model always brings a better user experience (minimal input), less complexity, better value, better analytics, thus providing better insights for the business. The key point that must be looked at is that while building the data model you should focus on data analytics. This will bring a much better value to the product, and you will be able to provide quality reports in the future. You could consider key dimensions and measures during this stage.?

Prototyping/Wireframing

I personally consider this as a key stage as this is a stage wherein you get a buy-in from the users even before you deliver a product/feature. Create a mockup or a wireframe based on the processes that you have identified. This does not necessarily give the look and feel of the final product, but it will give the user a view where they will be able to see whether we have captured the right requirements and the fields required are in place. This will also give a chance to improve the product behavior at a very early stage. There might be several iterations required to finalize the wireframes and this stage might take some time to get finalized. However, it will simplify the complexity in the next stages.?

Solution Design

The performance and quality of software or applications are directly impacted by its Architecture. So, the better you design, the better it will perform, and the maintainability (BAU) will be much easier. The core objective here in the solution design is to see what technology to be used, what needs to be modularized and how do we do the integration so that the modules can communicate with each other.?

Define Epics and User Stories

The complexity of the stage is comparatively easier as we have the required processes, the capabilities, features, the agreed wireframes, and a high-level solution design. During this stage, we should be comfortable in defining the epics (which can be tied into the capabilities) and user stories (which can be tied into the features), and these wireframes or mockups can be used within the user stories so that the designer/developer will get a visual view of the screen.?

Again, this doesn’t mean that the product can be further improved. This is the beauty of scrum. We are able to see a completed feature and there is always room for improvement if it is within the scope, the feature can be added to the subsequent sprints or in a backlog.?

Next Steps?

The development phase begins with this and an important task here is to review the application at different sprint cycles and make sure that the developed application is meeting the customer requirements. This is important from the beginning stage, as a rollback can be difficult at a later stage.?

Conclusion?

To successfully complete a project, a lot of effort is required while it goes through different stages and steps within each stage should be completed in a comprehensive manner so that the outcome is a quality product that brings value to the business.?