The first thing you should start with is to choose the most appropriate team size which will determine the speed with which the project will move forward
Our guys can move at speeds from 64 to 2000 hours a week. Let's further
explore how it works. The team will include the following specialists
working at a full load:
- 1 Project manager / Lead developer
- 1-4 Frontend developers
- 1-4 Backend developers
- 1-2 QA specialists
- 1-2 UX/UI designers
Now let's look at an example of a small, dedicated team that can spend
160-200 hours per week:
- 1 Project manager / Lead developer - 24‑32 hours per week
- 1 Frontend developer - 40-45 hours per week
- 1 Backend developer - 40-45 hours per week
- 1 QA specialist - 32-45 hours per week
- 1 UX/UI designer - 24-32 hours per week
The dedicated team is always made up of full-time developers who are only
dedicated to your project and cannot work less than 40 hours a week. This
condition works even if there are temporarily no tasks in the project.
Often, during such periods, the guys are engaged in code refactoring, bug
fixes with priorities 4-5, and working with the backlog.
However, a dedicated team may include part time developers, either temporarily
for a quick push or periodically as needed. For example, you do not need a
UX/UI designer all the time in a situation when all the mockups are ready and
approved, but if necessary UX/UI designers can be involved to make some adjustments.
Why do we mention 40-45 hours a week? The fact is that we work hourly and the
guys have the opportunity to work more than 8 hours a day. Each guy can work
an average of 9 hours a day at the request or request of the project manager.
This increases the total up to 45 hours per week. Therefore, when discussing
the speed of work we always stipulate a range of additional hours per week.
We also have the practice of Turbo mode in the case of ASAP or on the eve of
the deployment for production. The guys, by prior agreement, can work more
than 10 hours a day and on weekends. In this case the team logs double the
amount of hours spent into the time tracker. This practice works for a limited
time period no more than 1-2 weeks and only in agreement between the project
manager and the team.