Our cooperation with you starts with the first message you send us. From there:
We have an intro call, where we agree on all initial details and sign an NDA;
We have the Q&A session with the client and our BA to get all needed details
about the project in order to complete a quotation;
After the proposal is accepted, we mutually commit to the original
development agreement and start the cooperation when the contract is signed.
However, some steps may be skipped or merged.
What are the pre-development stages?
What are the pre-development stages?
A project kickoff with the client;
Available initial requirements analysis;
Form a backlog for the 1st development iteration;
Agree on details of the approach that will be comfortable for both parties.
How will you ensure that you understand my project’s requirements?
We give a high-level overview of the project as part of our estimation process, along with some mind maps (the simpler, the better). Then we have a meeting to review the requirements and talk through the business problem and proposed solution.
How does your process reduce my risk and increase my chances of success?
We provide very precise analysis, research, and an overview before starting the project. Also, we set up teams such that the developers have a relevant experience in the required domain, know what the weak spots are and which solutions are better, and always put quality over quantity. Thanks to our Agile methodology, you ll get fully transparent progress overviews. These allow us to track success and decrease risk.
How do you integrate existing brand guidelines?
We measure our clients satisfaction by requesting feedback constantly. We send out simple questionnaires every 2-4 weeks to ask about:
Our team’s performance;
What was good or bad during the iteration, and where the areas for
improvement are;
Your overall satisfaction level.
What s the best way to share project requirements with your team?
The best way is to send an email to our Business Analyst with all existing documentation related to the project.
How much lead time/preparation time do you need before starting a project?
Basically, we need about 5-10 working days to set up a team up for a project, depending on the project domain and team size.
How does a typical project unfold, especially with regards to agile project development?
We use classic SCRUM methodology with 2-week sprints. We constantly review our progress and
provide demos to the client, starting from project initiation right through to the MVP release, further
project growth, or maintenance.
How do you ensure that all the necessary requirements within the project are met?
We store all project documentation in a task management tool called Confluence. For each
requested feature we create reasonable tasks, which are implemented by the development
team step by step.
How do you realize the final hand-over of a project?
We do final testing and:
A development environment for the development team;
A demo environment for clients;
A production environment.
The client has access to all 3 environments. The demo environment is used by the client to check project progress.
How do you measure the performance of staff on a client project and ensure non-performers are removed from the project?
We ve defined an approach for performance measurement:
Planning
Performance review
- he PDPs of each employee are based on the company s strategic goals (MBO approach);
- team Leaders provide intermediate reviews.
We provide 360-degree feedback once every 6 months and track factors such as initiative, motivation, teamwork, results orientation, time management and self- sufficiency.
- a results checkup after each sprint;
- an independent code review by a Tech Leader from other projects;
- strict task-management and reporting procedures are covered by Project Manager.
We have monthly one-on-one meetings to make sure each specialist is involved in the development process, highly motivated to work, and ready to handle possible challenges.
The client has access to all 3 environments. The demo environment is used by the client to check project progress.
Which are the different roles within your team?
We offer turnkey solutions. That’s why we have specialists including:
Agile Project Managers;
Business Analysts;
Solution Architects;
UI/UX Designers;
Software (Backend, Frontend) Engineers;
QA Engineers;
DevOps Engineers.
Can someone on the project team, or a developer, work temporarily on-site at our office (assuming we cover their travel expenses)?
Sure.
Do you provide a single point of contact who is responsible for us, beyond project-related questions?
Yes. This person will be the Sales Representative before the contract is signed, and the Project Manager after the project has started. You are welcome to communicate with the dev team throughout the process.
Are you able to provide additional resources, in case they’re needed?
Yes, we can provide additional resources if we need to increase a team’s capacity.
How quickly can you ramp up additional resources?
Usually it takes us 5-10 working days to allocate the necessary specialists to a team. The overall duration depends on the requirements.
Communicate
& Cooperation
In general, what documentation do we get once the product is delivered?
The client gets all the business documentation written during project development, as well as technical documentation.
Do you provide user manuals for the end-user?
Yes.
Are your employees bound by contract to confidentiality?
Yes. Each new employee signs an NDA.
Do you conduct code reviews internally or externally?
We do it both ways.
Which tools do you use for remote cooperation/ communication?
For a remote cooperation/communication, we use the following tools:
Jira for issue-tracking and filling the gaps between project managers and
developers;
Slack for internal messaging and notifications about progress, code
updates, deployments, system alerts, etc.
Github for code management, using branches, code review, PEP8, and
internal code conventions
Sketch/Figmafordesignprototyping.
How often should we communicate with you during the development process?
Based on our experience, around 2–4 hours per day in the first two weeks. After that, the client is welcome to attend daily meetings, but doesn’t have to. The results-review meetings take place every two weeks. You can expect us to be available to answer your questions on a daily basis (it will take usno longer than 24 hrs to reply).
How do you estimate time and cost?
After a deep analysis of your initial requirements, we’ll provide you with an estimate for features implementation based on the following parameters:
The experience we’ve gained by building similar projects;
Project domain knowledge;
Risks;
Teamsize;
Integrations with 3rd-party services;
Uniqueneeds.
What will my estimate include?
Your project estimate will include a list of initial features, the team required and their rates, the expected project duration, and the project’s initial cost.
What happens after my product has been delivered?
We hand over all project documentation to the business, terminate supplier contracts, release the project resources, and communicate the closure of the project to all stakeholders.
If required, we can sign a separate agreement for maintenance and support.
What happens after my product has been delivered?
Yes.
Do you offer DevOps services for the target environment?
Yes. We offer the following DevOps services:
CI/CD;
Scaling;
Data migration;
Service health monitoring;
Do you work with Docker?
Yes, we work with Docker/Ansible/Fabric for creating, deploying, and running applications.
What does your typical deployment process look like?
For the deployment process, we use CircleCI as a continuous integration and delivery platform. All code repositories are linked with CircleCI. Code is checked after every new update to make sure it passes all the predefined tests. After the Pull Request passes checks and all Tests are "green", CircleCI automatically deploys on the server (dev, stage, production).
Do you use a monitoring tool to control performance and follow up on debugs?
Yes. We use the following tools:
Newrelic for performance monitoring. It shows the state of all servers and ensures
all of them are responding in time. When things go wrong, it sends reports to our Slack channel, which notifies our admins. This all happens within seconds of any failure;
Sentry for real time error tracking. It gives insight into production deployments and information to reproduce and fix crashes.
