Conference of Architects. How it was

    The LANIT architects team is actively hosting thematic meetings so that employees can pump expertise and share experience with colleagues from other companies.

    This time we swung even cooler and under one roof decided to bring together more than 300 specialists and experts in IT architecture at the four-day conference "(IT) architect in IT projects and organizations."

    Read how this was and what was discussed in this article.

    4 days - 10 speakers - 10 interesting presentations

    Day 1

    • Architect in the project. Key Use Cases

    Speaker: Evgeny Aslamov, Head of the Architecture Sector, Corporate Systems Department, LANIT.

    What is the report

    about : Not a single system can be said to have no architecture. But it often happens that the architect (whatever that means) as a distinguished role in creating the system was not. Is an architect needed at all?

    Eugene shares his experience, which can lead to the allocation of such a role and how to look for a specific person under it when creating an information system.


    • Do I need an architect at Agile?

    Speaker: Sergey Baranov, Managing Partner, ex-solution architect, ScrumTrek

    About the report:

    Do I need an architect at Agile? Someone will say: “No,” the second will pick up: “There is no architecture in Agile.” But there will be those who object: "Without architecture, the architect is important and necessary." The reason is that the question itself is incorrect. The presence or absence of an architect does not depend on the methodology or method of work. It entirely depends on the needs of the product, and in particular on technological complexity, the complexity of the subject area, the level of uncertainty, and other factors. The expert tried to determine what the role of the architect is and what value he can offer the product. Then the speaker formulated the needs of the teams and the product itself, identified the relationship between needs and value, then wrapped it in a single model and finally answered the question: “Do I need an architect in Agile?”


    • Solution Architect in an Organization: Organizational and Technical Aspects of Creating and Using an Architecture Description

    Speaker: Ivan Lukyanov, Head of the Department of Architecture Development, Moscow Institute of Literature

    About the report:
    Each IT organization, to some degree of detail, is engaged in a description of the architecture of the solutions created in it. The possibility of using architecture descriptions is influenced by both the characteristics of the organization’s internal culture and the level of its technical maturity. That is why a solution architect for successful work needs to understand the basic organizational and technical aspects of architectural activity and the ability to take them into account in practice. In the proposed report, an attempt was made to point out some of these aspects using the example of creating architectural solutions in the Department of Public Services of the Moscow City Institute of Information Technologies.


    Day 2

    • Practice Enterprise Architecture

    Speaker: Yuri Karabutov, Head of Solution Architecture, Raffeisenbank Presentation


    Presentation is dedicated to Enterprise Architecture Management in Raiffeisenbank Russia. How strategic architecture comes to life through projects. About architectural supervision and the role of architectural standards in the Agile world. And also about other architectural practices used and developing in the organization.

    • Architect in state projects

    Speaker: Alexander Luchkov, systems architect, “Airborne Navigation Systems”

    About what the report:

    The report discusses some of the working moments and typical tasks that arise in the work of a system architect, and the value of architectural practice in fulfilling government contracts.


    • How to save money on automation or why you need an architect

    Speaker: Vladimir Panchuk, Solutions Architect, Alfa-Bank JSC

    What the report is about:

    Over time, the organization has more systems, the relationship with systems is greatly complicated. In turn, business processes are becoming more complex. All this leads to an increase in the staff of developers who do not know what this or that system is for, what other business processes in other teams are. If you leave the development process without proper control, then there is a duplication of functions and / or the creation of rather strange processes. In this situation, a properly built process with the participation of an architect helps. And there is also the wrong process. Control points should appear here. The speaker tried to tell how Alfa-Bank builds the right processes and how the team copes with deviations from the process.


    Day 3

    • A fascinating elevator ride through the eyes of a decision architect

    Speaker: Gennady Kruglov, Solutions Architect, National Settlement Depository

    About which the report:

    Practice of interaction with different groups of stakeholders in building large-scale solutions architecture from scratch in a "mature" company.

    The report is based on the cases of introducing new technologies and building project teams in developing solutions in new subject areas for companies.


    • Types of architects and their skills

    Speaker: Dmitry Romanov, Chief IT Architect, Uralvagonzavod

    About which the report:

    • What kind of architect do you want to become and what you need to be prepared for when choosing a profession or role as an IT architect
    • What competencies do different architects need, what difficulties do people face when moving from developers to architects, and other issues related to the work of an IT architect.


    • The discipline "Architecture of information systems" as the basic part of the training of specialists in the direction of "Information systems and technologies." The shock and awe of personal experience

    Speaker: Eduard Galiaskarov, Associate Professor, Department of Information Technology and Digital Economics, Ivanovo State University of Chemical Technology

    About which the report:

    Should architects be trained at universities? At the moment, this is not the question. The modern educational standard includes a discipline on the architecture of information systems as mandatory.

    Can a university prepare an architect? The question is not simple and debatable. It is clear that an architect is a synergy of knowledge, personal qualities and experience. A young man comes to a university with already formed personal qualities, it is unlikely that anything can be changed here. Experience is the son of difficult mistakes; it requires practical work in serious real projects, which is almost impossible to achieve at a university. Thus, the university should lay the foundation, form the foundation on which the future specialist will be able to grow.

    In his report, the speaker shared his experience in teaching IP architecture at Ivanovo State University of Chemical Technology, the conference participants discussed the pressing issues of teaching and exchanged ideas on how to achieve compromises between needs and opportunities.


    Day 4

    • When does a solution architecture begin and how does it end

    Speaker: Maxim Smirnov, IT architect, independent expert.


    The number of ideas for optimizing processes, creating new products or changing existing ones far exceeds the ability of organizations to implement them. Companies are experiencing a shortage of funds, people, and competencies, which do not allow them to realize a small part of their plans. This state of affairs leads to the emergence of a new type of task for IT architects: a quick assessment of the potential feasibility of a particular solution and the selection of one of the possible implementation options. This has to be done at a time when the requirements have not yet been formulated, the boundaries of the project are blurred, and stakeholders are very dimly aware of what is at stake. What architectural techniques may be useful in this situation is the topic of the report before you.

    And we also held a Round Table and exchanged views on how the tasks of the architect have changed over the past few years and how they may have to change.

    We are waiting for your comments on topics and reports.

    We are always happy to communicate and exchange experiences, so if you want to make a presentation at our meetings in Moscow, please fill out the form .

    Also popular now: