Skip to content

DEV Community

How to design a team that would produce software of good quality? Series' Articles

Back to Vitaly Sharovatov's Series

Vitaly Sharovatov

Aug 25 '22

Designing a team that would produce software of good quality: information loss problem

5 min read

Vitaly Sharovatov

Sep 1 '22

Designing a team that would produce software of good quality: team processess issues

7 min read

Vitaly Sharovatov

Sep 8 '22

Designing a team that would produce software of good quality: no time pressure

6 min read

Vitaly Sharovatov

Sep 19 '22

Designing a team that would produce software of good quality: knowledge overlap

4 min read

Vitaly Sharovatov

Sep 26 '22

Designing a team that would produce software of good quality: team size

3 min read

Vitaly Sharovatov

Oct 3 '22

Designing a team that would produce software of good quality: management complexity

6 min read

Vitaly Sharovatov

Oct 11 '22

Designing a team that would produce software of good quality: emotions and interest

6 min read

Vitaly Sharovatov

Oct 18 '22

Designing a team that would produce software of good quality: turnover effect

5 min read

Vitaly Sharovatov

Nov 2 '22

Designing a team that would produce software of good quality: get rid of individual performance reviews

8 min read

Vitaly Sharovatov

Dec 7 '22

Designing a team that would produce software of good quality: set up dogfooding

10 min read

Vitaly Sharovatov

Dec 22 '22

Designing a team that would produce software of good quality: overcome mental sets

9 min read