We develop correctly.
We develop alienably

We build development processes based on best practices and fundamental IT knowledge. To do this, we read fundamental works on development and management theory, specialized research, test practices on our projects and select the best ones. Therefore, customers eventually trust KT.team with 5—8 implementation and development projects.

Process approach

We work on IT consulting, outsourcing, and outstaff models. But in any format we rely on 4 values

Honesty

If we make a mistake, we honestly admit the mistake. We don't hide the facts, we tell the team and the client “as it is”

We expect honesty from the team. Thus, falsifying worklogs is punishable by immediate dismissal.

Customer = partner

If a client wants to cancel payment for any type of work, we certainly allow them to do so without complicated explanations. This is feedback for the quality of our work and customer satisfaction.

The client may ask for a refund even for work under already signed acts within 50 calendar days. We understand that some persons sign acts and others accept works. Moreover, even serious problems can be identified after the signed acts.

We keep the client's secrets and don`t hunt his employees. That's why we regularly sign NDAs with all our employees.

We require our clients not to hunt down our employees under any explanations, because this creates a bad precedent and forces us not to put the best people on the project.

We are trying to understand the client's true request and are not afraid to ask “5 why” questions, we do not accept answers for the sake of answers, and we do not encourage the “do as asked” strategy — we know that in custom development this leads to architectural problems that are difficult to fix.

Schemes should not contain terms that are unclear to business. To understand each other, you need to speak the same language.

Quality

First we design, then we do it.

We design software in a language that businesses understand to make the perfect naming.

The designed value is explained to at least one more experienced person before implementation (by standards — to a technical lead or an architect).

If we did a bad thing, we'll redo it for free, even if it works as intended.

We are committed to the KISS (Keep it Short and Simple) principle. The solutions must be elegant and beautiful. The criteria for ugly things are complex, unclear, and nonlinearly.

Simple is not easy. So if we see an ugly solution, we think about it until we find an elegant way to solve the problem.

Reproducibility

We make software in business processes that ensure the simplicity of services and the ease of explaining their essence.

Creativity where there is no solution template, discipline in execution where there is one.

Focus on increasing the number of standard and already designed solutions, rather than on exclusive solutions.

If you don't agree with the standard, suggest changes. The changes should apply to the entire company.

As long as the standard is not changed, it is relevant. None of the typical patterns (standards) can be ignored.

Process approach

Our approach is the business-oriented approach

The continuous development and training of the team is embedded in our processes. The qualification department, leading developers and managers are constantly updating and improving training practices. We do not allow employees who have not been successfully trained in key practices to participate in projects.

Ongoing training for managers

A rating system to ensure the required level of project management

The audit conducted by the CEO is carried out on a monthly basis

We collected best practices in the IT Manager Workbook

The site provides a constantly updated electronic version of materials on managing development, measuring results and developing teams. Each section of the notebook is a short version of our own certification course, which all our project managers and developers take. The paper version of the notebook can be purchased at OZON and Wildberries.

Learn more