Voice Interface for Warehouse

Retail

Development

Team

Project manager, Solution architect, Analyst, 2 Backend developers, and 2 QA Engineers

Technologies

Java 11, Spring Boot, PostgreSQL, JSAPI

Duration

6 months

Problem

This project involved developing a voice interface for data collection terminals used by a warehouse with a significant number of foreign workers. The aim was to address errors caused by language barriers and difficulty reading small screens.

Solution

Introduction of the voice interface led to an average 7% increase in worker efficiency.

Error rates dropped by 10%.

Other Case Studies

With the Right Software, Great Things Can Happen

Finance

QA Audit for EMEA bank

4 months

Problem

A rapidly growing EMEA bank encountered a problem when it decided to expand its digital product portfolio. The addition of new products and integration with partner solutions began to cause increased downtime of certain elements of the bank's digital ecosystem.

System downtimes are critical for the banking sector from the perspective of business operations, profitability, and security. So, The Director of Development turned to the inbybob_ team for help.

Solution

Our team conducted a QA audit to streamline quality control processes. The methodology included a Preliminary Assessment, Analysis of the Testing Strategy and Coverage, Evaluation of Test Automation, Analysis of Integrations and Microservice Interactions, Defect Management Process Analysis, and Performance and Security Testing Assessments. Based on the results, we provided recommendations for improving QA processes, increasing automation, enhancing microservice interactions, and optimizing test coverage.

As a result, following these recommendations, key metrics were improved:

COBIT/ITIL/RUP/ISO/CMMI/PMBOK maturity level parameters and points to improve to reach 3/4/5 level
Measurement of development team performance as a current state with points to improve:
- Code quality control
- ROI for Autotests - time for development autotest / time for manual testing
- Time to fix defects
- Time to market (feature to production)
- Average time for regression testing

Team

Head of QA, QA Automation, QA Analyst

Technologies

.Net, Oracle, REST API

E-commerce

Facet Search

12 months

Problem

The search is carried out by the partner’s SaaS solution, in which the availability of all sales channels directly depends on the search.

The frequency of updating the search index is once a day, which significantly increases the time for new products to appear on the site and in other channels.

Boxed solutions lead to the Vendor Lock-In problem, unlike solutions built on open-source technologies.

Solution

Improved analysis of the search query for the presence of phrases typed with an incorrect layout. Extracting product attributes from a search query (conceptual search). Improved indexer based on In-Memory solution with support for partial indexing. Collection of statistics on search results based on ELK.

The team achieved an increase in the average check for sessions from a search by 1.5%, the share of sessions using the search by 7 percentage points.

Team

Product/Project Manager, Business Analyst, 4 Backend developers, 3 QA Engineers, DevOps Engineer

Technologies

ELK, Java 11, Kotlin

Finance

Quality Assurance

QA Audit for EMEA bank

4 months

E-commerce

Development

Quality Assurance

Facet Search

12 months

Retail

Development

Quality Assurance

Warehouse Management APP

12 months

Retail

Development

Quality Assurance

POS Check Constructor

3 months

Retail

Development

Quality Assurance

Temperature Monitoring System

3 months

Retail

Quality Assurance

HR Helper Bot

12 months

Flexible work formats

For convenience we offer several standard models of work with our clients.

Time and material

Model works best when you don’t have a clear scope and want to be deeply involved in the development process.

Choose it if:

you want to follow agile methodologies
you need to be flexible due to quickly changing requirements and taste hypothesis time to time.
you don’t have strict deadlines

All of that doesn’t mean you go in blind. Just like in the fixed-price model, you start your cooperation with planning, but only for the upcoming week or two. So instead of determining and fixing requirements for the whole project, you start fast and can further adjust the scope and priorities.

Fixed-capacity

This model focuses on ensuring the efficiency and velocity of the team. To achieve this, the supplier must ensure that different skill sets of members are assigned to a development squad to effectively deliver the project.

Choose it if:

you want to follow agile methodologies
you would like to have a fixed budget for a certain period, but don't have a clear idea on the defined scope of work or specifications
you understand further support steps and define continued predictable costs

We need to work with the client to clarify the scope of work and prioritize the backlogs before the next iteration starts. As the project progresses, it allows the client to mold the project along the way to take advantage of newly released features.

‍

Fixed-price

Model works best when you don’t have a clear scope and want to be deeply involved in the development process.

Choose it if:

you want to follow agile methodologies
you need to be flexible due to quickly changing requirements and taste hypothesis time to time.
you don’t have strict deadlines

Discount system

The discount is applied annually for a period of 6 months.

We provide discount system for long-term cooperation customers. If the threshold is reached for the sum of all orders from one customer, a discount applies to all new subsequent projects.