Business analysis

How we do it

We know that each project phase is very important for successful project completion. That’s why we don’t underestimate the introductory work with the client, right before any beginning of request implementation. We can very well handle the initial project phase where we look for “burning” areas of the company we work for. After that we are able to come up with possible solution proposals.
Of course, in the analytical phase, which is absolutely crucial, we collect detailed information of the client's requirements for the new system, respectively the required modifications to the existing one, while trying to get the maximum information about the systems with which we will eventually communicate with, get data from or supply data to them.
When the project comes to its implementation phase, our analytics team focuses on consulting development teams for details and solves any changes to the assignment if it’s found that some bright spots have appeared in their analytical outputs.
The subsequent phase of testing and deployment with the client is also partly under the responsibility of the analytical team in terms of solving various queries regarding delivered and tested functionalities or outputs, which may differ with the expectations of the end client.

What tools we use

We often work with Microsoft Office packages. Process analysis cannot happen without the knowledge of BPMN / UML tools for process maps, so we work with tools like Enterprise Architect or ARIS. In addition to our clients' internal systems, we also need their data warehouses or any data storages with internal methodologies.
From time to time, we need to look at the deeper details of logs, errors or systems communication passages. Hence tools like Kibana and Grafana help us do that.
Of course, we like to support agile development, so we use Atlassian software like JIRA - for project planning, task and bug logging, and Confluence - to document everything from meeting logs to detailed business / IT analysis.
During brainstorming we need well-known diagrams like Ishikawa, fish bone or SCRUM tools.
And it might be a surprise, but even today, paper and pencil are still needed.


The main benefit is the visualization of areas that are being solved for the client himself. Then it is an understanding of the issues that business analysis takes care of, as well as uncovering some of the ills of the past, which sometimes burn the company itself the most.

Who we work for

Our teams have experience in the areas of telecommunications, banking, insurance, and also in areas with significant automation.



Project: GLOBPAS

Project description:

The aim of this project was to provide a comprehensive overview of the motivation, costs and benefits, implementation timetable and technical implementation of the TOPAS project, which in the future will enable more efficient, safer and more powerful solutions for a completely new digital distribution channel.


Thanks to a proactive approach and years of experience of our supplier, we have successfully implemented activities within the analytical phase of the project.

Gleb Nagin
Program manager,
Československá obchodní banka, a.s.

Project: PAD

Project description:

Implementation of EU Directive 2014/92 / EU for payment accounts and other areas of the PAD project.


We especially appreciated the many years of experience of specialists from Denevy, thanks to which we received a quality job. At the same time, we are grateful for flexible and helpful communication.

Petr Kejř
Business analyst, KB