What actually happened is that we forgot about keeping the balance. After expanding the software development part of the team, we did not strengthen the testing part proportionally. So it turned out that testers work fell behind the developers, and at the end of the phase before the release, we had a written but not completely tested solution. We had to pay for this mistake with unnecessary delays and to deal with the functional testing debt that had accrued.
The lesson learned from this story – when making changes in one part of the team, think how these changes would affect the load of other team members. In addition, it is your job to explain to your client that time to market doesn’t only depend on the number of developers on the project and strengthening the team means extending all functions proportionally.
It sometimes happens that specialists on the client’s side think about software creation in terms of developers. Moreover, they base their expectations and estimations for software development costs and terms on this idea.
It is important to note that a development team also includes, for example, a test engineer, a business analyst, a project manager, a graphic and UI/UX designer, and so forth, depending on a project`s specifics. Don`t be shy to explain to your client that an efficient team does not consist of developers only.