The document outlines strategies for building an effective development team, emphasizing collective responsibility and collaboration. Key advice includes promoting open communication, leveraging individual skills, and setting shared goals to enhance productivity and reduce technical debt. It also highlights the importance of meetings for aligning on vision and decisions, alongside encouragement for team engagement through activities like hackathons.

1. Every time we create
something new we go
from zero to one
Peter Thiel

2. 2
How to build
an effective
dev team
and help business

3. 3
Mykola
Savenko
@biosis21

4. 4
Kantar
Consulting
Virtual
Reality
Front End

5. 5
Inertness
To be, or not to be

6. 6
Achievements

7. unit tests coverage
7
0 86%
9
55%
5.x
6
technical debt story points
Velocity Factor
version of Angular
Proof of Concepts
168
21%
1.x
0

8. Strategist
Listener
Goals
creator
Driver
Who you are?
8

9. 9
Advices

10. 10
Visible
process
Basic level
of team
agreement
Reduce
routine
Time Innovation

11. 1
2
3
4
3
11
4
2 Do not try to solve the problem alone. You are the team. Solve it together.
Praise team members. It gives people the drive and motivation to continue doing a work.
Advices 1-4
1
Collectiveness responsibility - when other team member asks you
something, ask all team members about it, if you already know the
truth.
Use People Partners’ skills.

12. 7
8
6
5
7
12
8
6
Advices 5-8
5
1-to-1 is a key to success.
If you want to talk about something important, setup a meeting.
Pair programming - give opportunities for other members to discuss.
Delegate your work - do not show the useless of this work, describe a goal.
Analyze business strategy and combine with DIP goals.
Every member will see the power of something big.
Create shared goal when one member depends on other.

13. 11
12
10
9
11
13
12
10
Create a meeting where you can share business vision or technical decision.
Visible sprint process. Each team member knows when and where.
Create your own technic how to eliminate huge amount of bugs and reduce technical debt.
Advices 9-12
9
Find hackathons and try to work together.

14. 14
Technical
Debt

15. 15
Team
Improvements

16. 16
Gantt
chart

17. 17
Let your boss know you wanted one
Demonstrate leadership skills
Look for ways to step outside of your comfort zone

18. T
Thank you
Thank you