Dedicated Development Teams
We believe in team work. Great achievements are only possible by cooperation with peers and helping each other. This is why we offer teams which can work exclusively on your project. It is the most effective and efficient way to organise work both in terms of costs and time. Our teams consist of people who are the best fit and have all the necessary skillset to achieve your project's goals.
Web Development Team
- Python (Django/Flask) developer with database skills
- Frontend (React/Angular) developer with Python & Django skills
- QA engineer
- Scrum master
This kind of a team could achieve a lot within short amount of time. It is small enough to quickly turnaround and big enough to perform significant amount of work.
Mobile App Development Team
There is a bigger variety of skills require to created a successful mobile application then web one. Often, there are three components of mobile app considered: Android app, iOS app and backend which typically has admin panel as well. Thus, the team should have relevant skills to be able to produce these components.
An example of mobile team could look like follows:
- iOS developer
- Android developer
- Python & Django backend developer
- QA engineer
- Scrum master
In case you need a bigger team, the following price table applies for additional engineers:
|Type||Hours per Week||Weekly Rate||Description|
|Basic Web Team||40||$2,800/Week||Basic team of two developers, one QA engineer and a scrum master to manage the project.|
|Basic Mobile Team||40||$3,900/Week||A team of three developers, QA and scrum master.|
|2nd, 3rd, etc additional developer||40||$1,100/Week||Either web or mobile developer. For example, this would be the rate we will charge if you'd like to build website along with your mobile application.|
|Additional Quality Assurance engineer||40||$500/Week||QA/QC engineer|
We use scrum framework when approaching web and mobile applications. The approach to development can be described as follows:
- Create a backlog. Outlining all the features that may be developed
- Plan a sprint. Define what exactly will be done within the next iteration (typically 2 weeks long)
- Start a sprint. Kick-off meeting to get development started
- Daily meetings. Stand-up 15 minutes long meetings occurs on a daily basis to keep track of the progress
- Demo. Once sprint is done, we show what was done to each other and product owner
- Retrospective meeting. This is where we discuss what was good, bad and what we can potentially improve
- Start over again with new sprint
Once product owner is happy with the product, we release it to production. New sprint could be started upon release or the project can enter support & maintenance phase.