In my report, I talk about how to organize a department from scratch. I will talk about the main points and subtleties of this process.

1. Organization of development
from scratch
Boguslavsky Maxim / Full Stack Team Lead / Gett

2. Based on the experience of companies
2

3. The report is based on years of experience
● Organization of the process:
○ Developments
○ Testing
● Organization of work with external teams:
○ Testing
○ Automation
● Organization of educational process
3

4. Define the concepts
Organization is a process, an activity to create or improve the interrelations
between parts and elements in order to bring order to processes and improve
their effectiveness.
4

5. General principles
● Regardless of the company, the principles of management and
organization are the same
● But there are important nuances
● Management dev team! = Management team of low-skilled labor
5

6. Difficult start
● An established project has developed:
○ Processes
○ Budget
○ Technology
● A new project is a large zone of uncertainty.
● To keep the process is more costly than growing.
6

7. Where do we start?
● We gather the understanding of the goal from:
○ Stakeholders
○ Colleague and subordinates
○ Validate the existing view of the manager
● The goal defines the criteria for achieving
● We fix the current point (budget, technology, personnel, timing)
7

8. Forming the Path
● Each task is a step in achieving the goal
● The achievable task is an achievable step
● Remember about SMART
8

9. Quality control
● The area (quality) of the project is determined by:
○ Budget
○ Time
○ Scope of work
● The task of the manager to identify and manage changes
● Manage the edges keeping the volume
9

10. Restrictions are great
● Limitations - an important indicator
● Borders - this is what keeps water in a glass
● Manage through the alignment of borders
● Narrow or expand the boundaries depending on the level of pressure in the
department or group
10

11. Importance of direction and support
● Choose any suitable methodology
● Each methodology gives its advantages
● Agile's values ​​in:
○ Confidence
○ Transparency
○ Feedback
● The methodology is secondary to management
● There are basic properties
11

12. Formation of organizational structures
● Formation as projects are implemented
● Balance:
○ Excessive planning drowns projects
○ The lack of planning blurs the framework and deprives the structure
● Of necessity:
○ Enforce the arrangements
○ Fix and approve plans
○ Fix job descriptions and regulations
12

13. Structure of the department
● Agile vs Matrix vs Hierarchy:
○ Three dimensions of control
○ In our company, a combination of three
● When recruiting a staff, a balance is important:
○ Lack and shortage gives flexibility and controllability
○ The excess deprives mobility, efficiency and increases the cost of communication
13

14. Stages of growth of the team: employee
● One person - minimum documentation
● Excess of tasks is better than absence.
● My recruitment recruitment:
○ If you have tasks for 1-1,5 weeks is better not to take
○ If you have 2-3 months of work in the backlog, initiate a set
● When overclocking after idle time, it is worth remembering that the team is
inert.
14

15. Stages of growth of the team: team
● The team begins to form with 2 people
● The leader is revealed
● With the growth of goals lost control
● When you are 6 people about programming you can forget
15

16. Formalization of processes in the team
● The reasons for the formalization of processes:
○ Vocal cords are poorly restored
○ Answers to the same questions
○ People on different understand oral arrangements
● Do not be afraid to make mistakes.
● If you have a trusting or conflicting relationship - feedback will be fast
16

17. ● Does not exist
● Division into teams is best done when reaching 5 - 7 people
● Specializations are needed when achieving a large number of profile tasks
● Remember about 5-7 focuses of attention
Ideal process
17

18. Organizational structure
● The department consists of 15 or more people
● It can contain 3 or more teams
18

19. Cycles of team growth
19

20. Management Position
● Remember that you are neither a friend, nor a brother, nor an enemy
● You are a person who:
○ Is higher
○ Endowed with resources, power and authority
● Goals of the management:
○ Organization of processes
○ Hiring
○ Manage your budget
20

21. Management problems: loss of control
● Loss of control is part of the process
● The task of building a self-regulating process
● Remember about 5-7 focuses of attention
● Get rid of people who eat the focus of attention
21

22. Command networking
● The informal leaders and the opposition are part of the process
● Everyone has a chat room where they wash their dice
● Repression gives strength to the opposition
● Listening and solving problems - deprives forces
22

23. Command riot
● Riots are when your activities are not satisfying
● When the team is ready to go against the leader - this is a serious oversight
in the leadership
23

24. Illusions
● Illusions are what lead to rebellion and stagnation
● Let us recall Nicholas II
● Ask yourself more often the question: Do not I do bullshit?
24

25. Assholes and psychopaths
● Asshole is a person in a bad mood who once created a conflict on the level
ground
● People with pathologies:
○ Will lie in your face, and behind you will be against you
○ Psychopaths - a physiological disorder that deprives a person of empathy
○ Sociopaths - a form of behavior when people do not consider the consequences of their
actions
○ With them you need to say goodbye at once
25

26. Confronting unscrupulous personnel
● Regularly clarify the situation:
○ Monitor layoffs and productivity losses
○ Conduct face-to-face betting
○ Fix arrangements
○ Reduce emotional communication
○ Speak your decisions
○ "Don't be asshole!"
26

27. Conclusions
● Winners are not judged.
● Work with management
● Empty power is a dangerous thing
● Trust must be based on something
● Do not hold on to the place
● Work is the fourth priority in your life
27

28. Literature
● Cognition in the wild:
○ A book on how the ship's ship is organized
● Being geek:
○ A book about how an engineer became a manager
○ Recommendations and advice
28

29. Literature
● Power, influence and management in organizations:
○ A book about politics, management and influence
● Theory of ethnogenesis:
○ A book about how large communities of people are organized
○ About people and how the idea drives communities
29

30. Literature
● Snakes in Suits:
○ A book about how harmful psychopaths are
○ How they think
○ What harm do they have and how to identify them?
● Do not work with assholes:
○ A book about how much harm the organization causes to toxic communications
○ And why is it useful to get rid of spectacular but scandalous colleagues
30

31. Contacts
Maxim Boguslavsky
Email: maxim.boguslavskiy@yandex.ru
Linkedin: https://www.linkedin.com/in/maxbogus/
31