2 offline days

Talking about schedules, sessions and sharing information. Come to the gym or connect online to find out what's coming up for you!

20 years ago the Agile manifesto announced a new era in development. Many practices from the waterfall process, including system-engineering requirements management, were thrown out of projects. For the next 20 years, we watched as the void was filled. Today it's time to talk about requirements again: whether they are needed and, if so, in what role and quality.

In what cases a log of architectural decisions can replace a detailed design and detailed documentation, how to develop it, what are the formats for describing architectural decisions and the practice of their preparation.

According to statistics, 80% of ERP implementation projects are unsuccessful. The speaker will talk about 10 classic mistakes that happen when implementing IT systems and share his experience on how to avoid them.

Sometimes to create something new, you have to understand how the old works.

We'll look into the UX research approach and analysts' actions, as well as learn how to apply it and discuss possible errors on the way. 

The speaker will share his experience and tactics used on a new project with a new team. He will also talk about opportunities for rapid growth in the current circumstances. 

The speaker will talk about how they combined separate products into one, then came eventually to a platform and multiple products. There were many changes in the processes built in Jira and in the services themselves: improving microservices, adding micro-fronts, abandoning the monolith. The talk will be of interest to analysts and developers as well as executives.

We'll learn about the most common obstacles you may encounter when writing security requirements. We will be discussed: laws and standards, the threat model, plugging holes. We will also learn how security requirements are related to other types of non-functional requirements.

Olga will tell on practical cases how analysts can apply Miro and what its pros and cons are.  

Alexander will tell how his team developed their own Java plugin for Trino and uses it in combination with Apache Superset for efficient data analytics through BI connector to Bitrix24.

In practice, analysts are not so much concerned with analysis as with system design. This work is often not highlighted or even realized by the analyst, which means it is not always checked and done well. The speaker will give analysts tools and a set of practices that will allow a more conscious approach to the system design process.

One of the current problems is training ML/DL systems on real data. The speaker will talk about the peculiarities of working with physical documents from the point of view of ML/DL systems, why you need DWH and ETL, and why it makes sense to read books about projects from the USSR of the 60s.

Artyom will tell how his team built the architecture of a mobile application that allows new features to be delivered to Alfa-Bank employees without updates in the stores. The peculiarity was that it was necessary to unite dozens of legacy corporate systems under the hood in a short period of time.

Process Mining, a modern technology for analyzing processes based on digital traces in information systems, is now actively gaining popularity among business analysts, process management specialists, operations managers and internal auditors. The technology is applicable for analyzing processes from different areas - sales, procurement, logistics, back office. Application of the technology allows to reduce the cost of the process by more than 10% on average.

A perfunctory examination of Enterprise Architecture materials gives the impression that it is something out of the realm of TOGAF, Zachman, and ArchiMate. But successful architectural practices have nothing to do with them. The speaker will analyze the most popular misconceptions about enterprise architecture and explain how things really are.

As we know, there are no roles of system and business analysts in the GameDev-team. But does this mean that analysis is absent in game development altogether? And if it does exist, at what stage and how much analysis is involved?

Sergey will talk about chopping a large monolith of the "Transportation Management System" at Magnit. This system manages the planning and control of the movement of more than 10,000 vehicles in online mode. 

Ksenia will tell us about the challenges faced by analysts and vendors when developing internal services used in multiple corporate products of one company, using VK as an example.Ksenia will tell us about the challenges faced by analysts and vendors when developing internal services used in multiple corporate products of one company, using VK as an example.

We will analyze the concept of data governance and answer the question: how can companies move towards data-driven, if it is impossible to implement everything at once? We will understand the goals of data management tools, prioritize their implementation according to the stage of business development, and talk about the global trend towards storage hybridization.

Tired of thinking during the talks? Then we invite you to think at a creative quiz!

Together with Liga Indigo, we are organising an intellectual quiz, where you can test your intelligence and erudition, as well as have a great time together with other conference participants.

Lightning talks are a great format to have a dynamic discussion and find like-minded people. Ten-minute talks on near-professional topics and vibrant discussions are waiting for you. You have seen Flow's talks and feel you can add something of your own to the them? Apply for a Lightning talk at the venue and expand the list of conference topics!

An analyst has a lot of knowledge, but often does not use it. The speaker will explain how, armed with the right communication skills, you can properly influence your team and stakeholders to achieve a common goal.

Anastasia will talk about the pros and cons of the low-code platform, prerequisites for moving the system to a new stack, and share the experience of import substitution. The report will be useful for system analysts, who take part in choosing the architecture for new projects, as well as those involved in the development of a low-code platform.

A workshop for analysts who have read 100500 times about Kafka and tops, but still haven't figured out why they are organized the way they are. We will use practical examples to understand the key Kafka concepts: topics, partitions, consumer groups, and replication. 

Daria will talk about what notations for describing processes exist in general, what are their fundamental differences and how to apply them in different contexts: business process automation, simulation modeling and functional-cost analysis, creation of software robots.

C4 model is a popular approach to architecture description. The speaker will tell about his experience of using C4 model: how to develop at each level and what tool is convenient to use for architecture description.

Event Storming methodology allows you to significantly reduce the time and labor intensity of analytical work by replacing individual work sessions and agonizing offline approvals for contact work in the format of specialized face-to-face or online seminars. Denis will introduce this technique and show the specifics of its application in work to improve the efficiency of teams.

Nowadays design systems are an integral part of any application. But few people think about how they are created, much less how to write requirements for UI components that are understandable to developers, analysts, and designers.

The report will consider the possibility of using regular expressions in the work of a system analyst and analyze real cases of solving problems using regular expressions.

Evaluation is an important part of the team's work. A competent evaluation requires a high level of expertise, responsibility and objectivity from the analyst to make the project profitable for the company.

The speaker will talk about how to create an environment and interaction in teams that help analysts grow and solve more and more complex problems. How to gradually work your way up from a novice to a solution architect, and most importantly, how to create an environment in which this path would be comfortable.

The report is devoted to the practice of using Customer Journey Map (CJM) as a communication language in a product team. We will also talk about using this tool for personal purposes.

The "Architecture as Code" approach allows you to integrate all participants in the production process into a single, continuous pipeline. It is able to cover production from strategic business objectives, to deployment in production. Ideally, it is the digital twin of production.

The speaker will talk about the approach they have formed at AlfaStrakhovanie to transfer requirements. Why and how it helps minimize the risk of coming back to redo or finalize design layouts.

A talk on mobile application development with a focus on the role of the systems analyst. Consider the competencies of an analyst to work effectively in a team.

The speaker will talk about his methodology of user research: how to understand what they do, what tasks make up their working day, and what difficulties they face in the face of tight time constraints.

We summarize the results of the conference, recall the highlights and talk about future plans. Come to the hall or join the broadcast so you don't miss a thing!