WHO WE ARE
Our team & vision
We are a remote team of software engineers and project managers with over 10 years of experience developing custom software solutions and digitizing businesses. In addition to a wide range of IT services, we offer consulting for enterprises and organizations that need to optimize their own software maintenance and development processes while implementing Agile methodology.
OUR METHODS
Processes & solutions
Agile Methodology
Our team encourages partnerships based on Agile Sprint Process.
It is a method of collaboration that makes the best accountability and flexibility possible by dividing a development process into periodic iterations called sprints. With constant client collaboration and feedback loops on every development sprint, we have a workflow that is far more efficient than any other.
A sprint is the most basic unit of a release, where we specify tasks: estimate, implement, test, deploy, and review them. During a sprint, ideally, no changes to the tasks or their ordering are allowed. Therefore, the shorter the sprint, the more agile we can be: ie we can make quicker decisions to do something different in light of knowledge we’ve acquired along the way.
Accountability
Machine Learning
Complex problems often require complex solutions – such as Artificial Neural Networks and other Machine Learning algorithms. We have a plethora of experience in this area that ranges from fitting a tiny neural network on a smartwatch app, to building a core Machine Learning system for a 1M+ worth Artificial Intelligence startup.
In the Cloud
Our team encourages partnerships based on Agile Sprint Process.
It is a method of collaboration that makes the best accountability and flexibility possible by dividing a development process into periodic iterations called sprints. With constant client collaboration and feedback loops on every development sprint, we have a workflow that is far more efficient than any other.
A sprint is the most basic unit of a release, where we specify tasks: estimate, implement, test, deploy, and review them. During a sprint, ideally, no changes to the tasks or their ordering are allowed. Therefore, the shorter the sprint, the more agile we can be: ie we can make quicker decisions to do something different in light of knowledge we’ve acquired along the way.
As we break down the project into smaller iterations – sprints, we can have more precise point estimates and can also implement and execute the project in a way that the client team can be more involved. Both sides are always aware of the project status and deliverables. As a result we have a working prototype for you to use and interact with at the end of each sprint.
Complex problems often require complex solutions – such as Artificial Neural Networks and other Machine Learning algorithms. We have a plethora of experience in this area that ranges from fitting a tiny neural network on a smartwatch app, to building a core Machine Learning system for an Artificial Intelligence startup with more than 1 million users.
We are keen on setting up project infrastructure in the cloud even when the project needs to run on clients’ hardware. If applicable, we happily set up containerized services to be hardware agnostic and easily scalable.
HOW WE WORK
Workflow solutions
01 | For the start, we will go through all the vision of the project, provide overall estimation for the client and discuss main parts and tasks. We will also provide insights and comments on what could be improved to achieve the best result. | |
02 | We prepare and spec out separate tasks and details for the first sprint. | |
03 | Developers start to do their magic. | |
04 | While our developers are hard at work, we are preparing and planning the next sprint. | |
05 | When developers are finished with the tasks of the previous sprint – it is deployed and you can test it. | |
06 | Developers start working with the next sprint, while we talk about what you liked, collect all your comments and feedback, and prepare for the upcoming sprint. | |
01 | Before we begin work, it will take several days or a week to get to know the team, projects and all the background. | |
02 | As we get introduced to the current project, we will provide overall point estimation and discuss main parts of the project. | |
03 | We prepare and spec out separate tasks and details for our first sprint. | |
04 | Developers start to do their magic. | |
05 | While our developers are hard at work, we are preparing and planning the next sprint. | |
06 | When developers are finished with the tasks of the previous sprint – it is deployed and you can test it. | |
07 | Developers start working with the next sprint, while we talk about what you liked, collect all your comments and feedback, and prepare for the upcoming sprint. | |
* | As we integrate our team into the ongoing projects, the initial velocity might be a bit lower, but as soon as we merge our methods and get into the rhythm – you will be surprised. | |
01 | For the start, we will go through all the vision of the project, provide overall estimation for the client and discuss main parts and tasks. We will also provide insights and comments on what could be improved to achieve the best result. |
02 | We prepare and spec out separate tasks and details for the first sprint. |
03 | Developers start to do their magic. |
04 | While our developers are hard at work, we are preparing and planning the next sprint. |
05 | When developers are finished with the tasks of the previous sprint – it is deployed and you can test it. |
06 | Developers start working with the next sprint, while we talk about what you liked, collect all your comments and feedback, and prepare for the upcoming sprint. |
01 | Before we begin work, it will take several days or a week to get to know the team, projects and all the background. |
02 | As we get introduced to the current project, we will provide overall point estimation and discuss main parts of the project. |
03 | We prepare and spec out separate tasks and details for our first sprint. |
04 | Developers start to do their magic. |
05 | While our developers are hard at work, we are preparing and planning the next sprint. |
06 | When developers are finished with the tasks of the previous sprint – it is deployed and you can test it. |
07 | Developers start working with the next sprint, while we talk about what you liked, collect all your comments and feedback, and prepare for the upcoming sprint. |
* | As we integrate our team into the ongoing projects, the initial velocity might be a bit lower, but as soon as we merge our methods and get into the rhythm – you will be surprised. |
TECHNOLOGIES WE USE
Frameworks & tools
Mobile apps for iOS, Android
Native
Cross-platform (React Native, Flutter)
Backend development
Python: Django, Flask
Ruby: Ruby on Rails, Sinatra
Elixir: Phoenix Framework
Frontend development
Vue.js
ReactJS
Machine learning
Torch, Pytorch
Tensorflow
UX / UI design
Sketch
Figma
InVision App
Axure RP
More tools
AWS
Docker
Dataswift
Firebase