Talks

In mature companies, the effects of scale and time become apparent. It is not enough to just think about the implementation of a task; a vision of system development on the horizon of 10+ years is required. Unmanaged growth of complexity is one of the main risks of new development projects. Let's look at the enterprise architecture decomposition methodology for defining system boundaries, and building an architecture repository based on the Docs as Code approach.

Most of the developers make modifications to the microservices, which do not affect other parts of the platform. Still, sometimes those changes will involve one or more microservices. To reduce this type of problem, most teams use different tools to maintain communication like Slack, Teams, or other means, but this solution does not work in all cases. Some strategies to reduce the possible problems include using a feature flag, versioning the endpoints, or indicating the deprecation of some endpoints using the headers.  During this talk, you will learn how to implement some of these solutions depending on the situation.

Dashboard design is a discipline at the intersection of analytics and design. The speaker states that he does not believe in a process where the customer of the dashboard himself draws up the TOR for the developer, because in the end the developer becomes just "hands on". The person responsible for preparing the ToR and understanding the task is the specialist himself.

The speaker developed Dashboard Canvas, a requirements gathering framework, for convenient requirements gathering process for dashboard. This talk about its new version, there will be examples of its use. 

A session for systems analysts with experience in integrating IT systems and a basic understanding of brokerage principles and use cases. At the workshop in teams we'll break down some cases of using brokers: transactional and business processes, data collection and synchronization, event architecture.

How to define non-functional requirements? How should they be documented? Who should define them? How to do it properly? Why should this be done?

All this will be discussed in the talk.

Modern business is critically tied to IT. If yesterday software was used as a tool to cheapen and speed up part of business processes in a company, today it is an integral, and often a key part of business. In particular, this means that business development requires a clear alignment between the company's business goals and its IT capabilities. That is the general strategy of business development and the strategy of IT subsystems development must not only be coordinated, but also be parts of the whole. As a rule, contractors involved in custom software development rarely touch the subject of the customer's business strategy.

The speaker will tell about the consulting services formed by DZ and E-Legion, which help synchronize roadmaps for company development and the development of its information systems.

Interview with Alexander Belin in the main studio of Flow 2022.

We take stock, remember the bright moments and talk about our plans. Join the broadcast, so you don't miss anything!

At last week's meeting, the speakers did a good job of going over why analysts should participate in professional communities and what goals to set before launching an internal community. They also talked about how to communicate and defend the idea of an internal community, and formed expectations about what to endure while moving that community forward. We ended up with an organizer's checklist of sorts. We strongly recommend reviewing the last entry.

At the new meeting, we'll focus on what happens when the community is somehow up and running and hasn't dried up after three activist meetings (that's how many meetings it takes for a community to fall apart). We'll discuss how to keep the community viable, what actions you need to take to keep it growing and thriving, more activists, and management celebrating your efforts. 

The workshop proposes the use of Notion as the main project tool for creating and maintaining documentation, as well as for project management. In addition, Miro is considered as a visualization tool.

We think that banking software should run like clockwork - reliably and securely, because users trust the bank with money, and the reputational risks associated with money are very high. Using the example of a banking integration project, the speaker will tell you how things went wrong when the project was transferred from one team to another, and what role analytics played in it. You will learn what to do to identify gaps in the analytics and protect against such failures.

It is thought that sawing a monolith into microservices is a good thing. However, this has a downside. Operation, deployment, data synchronization. The praised CD actually turns out not to be so Continous, because everyone is waiting for the last command to be integrated. Let's talk about when it's worth taking a monolith apart, and what to keep in mind when designing such a change.

We will talk about the schedule, sessions, and share the information. Join the broadcast to find out what's on the air soon!

The speaker will talk about the interaction of services in the contract language, contract validation between services, autogeneration of code by contract.

In this workshop, you will learn how to build a project information management system based on Confluence and Jira so that it is easy to maintain.

We'll discuss how to formulate general requirements for documentation in a project and choose an appropriate documentation pattern. How to determine how to communicate in the project, make a communication matrix, what technology stack to use. How to define a requirements management plan. How to easily organize all this in Jira and Confluence.

Denis Bogdanov will act as a presenter, who is not immersed in corporate architecture, and will ask questions about it. Mikhail Maksimov will be in the role of an expert and will answer all questions. Viewers will also be able to give their comments in the process.

In her talk Natalya will tell: Who is a technical writer-analyst and how his work is organized. Why the approach "I will give an ordinary analyst the task to write documentation" does not work. What the processes in her team looked like and how it went from "we have a technical writer and he writes documentation" to "the development team itself writes documentation on services

Have you ever encountered PlantUML? Surely you've never used embedded procedures and have just learned about it.

Nikita invites you to master this tool together. At the workshop, you'll learn the full range of PlantUML features, see ways to automate documentation gathering, and practice approaches not described in the guide. You'll create a diagram to realize the power of the tool.

Stakeholder analysis is one of the most important areas of work for business analysts. Without a clear understanding of who we are doing everything for, what they expect to receive and how they will use it, it is pointless to continue the project.

We have already learned how to find stakeholders, describe them, classify and even work with their resistances. But a new concept of “Person” has appeared, which again confuses everyone: who are persons, why were they needed, and how do they differ from stakeholders?

When we start writing requirements for a solution, another new entity appears - “End Users”. And again, many questions arise: who are they, how are they related to each other, and what benefit do they bring in the process of developing a solution?

The speaker will share the results of many years of research in this area. He will talk about his own framework, which clearly describes the structure of the complex relationships of these three key concepts. Shows how to apply this framework in projects conducted for global global companies.

Let's talk about the new edition of the System Analyst standard, its key features, and what this standard gives to the community: analysts, employers, and educational organizations.

The workshop proposes the use of Notion as the main project tool for creating and maintaining documentation, as well as for project management. In addition, Miro is considered as a visualization tool.

The speaker will talk about how his team designed, developed and launched cloud BI analytics for hundreds of thousands of companies for Google Data Studio, Microsoft Power BI and Yandex DataLens tools. We'll talk about mistakes, pitfalls, and the choice of column-oriented repositories from Druid and Pinot to ClickHouse and Amazon RedShift. We'll touch on BI visualization tools from Apache Superset to Amazon QuickSight and Yandex DataLens. We will not ignore the issue of heterogeneous data replication. It will be interesting and informative.

In the Scrum process (as well as in other Agile methodologies) there is an inconspicuous ritual - sprint planning meeting. It is usually described as a simple prioritization of stories from the product backlog and selection of those that the team takes to work on this sprint. In fact, this is where the magic happens: user stories from the product backlog turn into sprint tasks. It's not often you hear exactly how they turn, with not every story fitting into the sprint without losing value.

The speaker wants to close this default. He'll break down more than ten techniques for breaking down stories into more detail, so that they fit into the sprint framework while still being meaningful and bringing value to users. And at the end, you'll get to practice breaking them down yourself. The session is aimed at analysts, product organizers, and the teams themselves - in general, anyone who works in short iterations and strives to deliver comprehensible value in each of them.

We will talk about the schedule, sessions, and share the information. Join the broadcast to find out what's on the air soon!

Dmitry and Mihail will share their experience of designing microservice architecture for a system of digital banking services on Digital2Go by BSS.

Using their system as the example, with data-driven approaches, the speakers will show the method of economically effective division of monolith. They analyzed the structure of the modules, frequency and collectiveness of amending the source code, technology of delivery to clients and dependency of income from Time2Market and came to unexpected conclusions which they will share with you.

On the last day of summer, we held a podcast called Docs as code, which aroused lively interest. The practices that were discussed are developing and spreading very quickly, as they give a concrete profit in a very short period of time.

The documentation roundtable on Flow 2022 is a continuation of this discussion. We will look at a typical version of the technical implementation of a documentation project (what is now increasingly called DocOps), try to assess the prospects of this practice, and discuss tools and approaches that allow the analyst to organize the process of requirements management in the context of DocOps.

BPMN often hovers around the world of Enterprise Development. Some are lucky enough to have encountered them and saved hundreds of hours of time, while others have only got pain and gigantic technical debt. The speaker will dot all the i's of using BPMN in software development projects on the example of Tinkoff, tell about the good and bad practices.

The talk is an overview of key elements of any corporate structure (business, application, technology) seen through the notation of ArchiMate.

The talk may be useful and interesting for a wide range of IT specialists (from business analytics to system and infrastructure architects) and is to help figure out different ways of modeling and describing complex processes and systems.

Maintaining documentation around the code (in the same repositories), in markup languages with support for constant relevance and versioning by the system analyst. Approach - staging = part of documentation.

Conflict in the team is an unavoidable part of our work. Conflict develops, moves us forward, and keeps us energized. Problems arise when conflict moves from a controlled to an uncontrolled state.

Together with Irina, we will explore how these conflicts between the team, unit, and employee can be mitigated, resolved, and avoided.