- What we doServicesExpertiseFintech
- Works
- Pricing
- Insights
- Company
- Contact Us
Yellow’s Delivery Quality Standards
We understand the importance of delivering a product that not only meets your specific requirements but also exceeds your expectations in terms of quality and functionality. Our team of experienced software development engineers is dedicated to ensuring that every project we undertake is completed to the highest standards. We take pride in our attention to detail and our commitment to quality, which sets us apart from our competitors.
Objectives
Trustful partnership
We aim to build long-term relationships with you as our client by consistently delivering high-quality software solutions that meet your unique requirements.
User-centric software
The end user is our top priority. The UX/UI design and code we create for your project are targeted to meet the needs of your software’s future users.
Business-first approach
We write code not just for the sake of writing code. We make sure that everything we create addresses your business goals and users’ needs.
Why can you trust us with your project?
As a responsible software development agency with 7+ years of experience, we developed a set of values and quality standards that we closely follow on every project we work with.
Documentation
Having documentation on each project saves time on employees' onboarding, knowledge transfer, and just digging through emails for the latest relevant information. Balanced documentation includes:
Defined requirements
Project specifications
Design specification
Project’s technical stack
Repositories, environment links
Workflow and process documentation
Methodologies
We mostly work on software development using Agile practices (Scrum in particular). By using Agile methodologies, we are able to develop a product:
When the product doesn't have a list of fixed and explicit requirements.
When there's uncertainty in the list of features.
When a minimum viable product (MVP) is crucial.
When there's a need to show some incremental parts of the work being done after every iteration.
Security
We understand that protecting sensitive information is crucial for all parties of the agreement. To ensure that your data is protected, we stay up-to-date with the latest security technologies and industry standards and implement strict security measures:
Source code encryption
Data encryption
Injection and input validation
Authentication, role management, and access control
HTTPS usage
Logs data access control
UI kit
UI kit includes all types of site content: buttons in different states, icons, checkboxes, menus, breadcrumbs, etc., and the way how pictures and photos will look in the final product. We create a UI kit for you to:
Free more time to focus on the most critical aspects of your designs
Decrease the necessary time for building components from scratch
Create reusable, consistent, and maintainable UI components
Continuous integration/continuous delivery(deployment)
CI/CD is a method to frequently deliver app versions by introducing automation into the app development. CI/CD is a solution to the problems that new code integration can cause for development and operations teams (aka “integration hell”). CI part:
Automated tests
Static code analysis, including linting and security checks
Review process
Building artifacts
CD part:
GitOps practice, TeamCity, GitHub Actions
Rolling Update, Recreate, Canary, Blue-Green Deployment
Version control
With version control, every change made to the code is tracked. This allows you to see the entire history of who changed what at any given time — and roll back to an earlier version if necessary. A version control system:
Creates a single source of truth.
Protects the source code from irreparable harm.
Facilitates coordination, sharing, and collaboration across the entire development team.
Enables teams to work in distributed and asynchronous environments.
Code review
Regular code review helps to maintain high standards of quality and enhances the overall performance of the code. How does code review work? When one team member has finished working on an issue, another one looks through the code and considers questions like:
Are there any obvious logic errors in the code?
Are all cases fully implemented in accordance with requirements?
Are the new unit tests sufficient for the new code?
Do existing tests need to be rewritten to account for changes in the code?
Does the new code conform to existing style guidelines?
GitFlow
At the beginning of each project in Yellow, we define a GitFlow that'll be specific to the exact project. It’s a simple and effective way to support continuous deployment and constant releases. The key benefits of GitFlow are:
Parallel development
Easy collaboration
Support for quick fixes
Quality assurance in Yellow
Quality Assurance is the process of checking the quality of the product based on a defined set of standards. These standards are established at the beginning of the development stage and are used as guidelines for testers before the product’s release.
On our projects, we use the following QA Manifesto for development:
Testing throughout the project OVER testing at the end
Preventing bugs OVER finding bugs
Understanding what to test OVER checking functionality
Building the best system OVER breaking the system
Team responsibility for product quality OVER tester responsibility
QA practices we follow:
Test Planning
Test Design
Test Execution
Completion
Unit tests
"Unit test" is a testing method by which individual units of source code are tested to determine if they are ready to use. Why do we write unit tests?
Unit tests save money and time
They help the team detect problems immediately, then fix them quickly. With fewer resources spent finding bugs, teams can move on to the next project phase.
Unit tests help with code reuse
Engineers working on your project are able to migrate not only the code but also the tests.
Unit tests are independent
Due to the modular nature of unit testing, engineers can test parts of the project without waiting for others to be completed.
Unit tests facilitate refactoring
Unit testing allows the team to refactor code at a later date and makes sure the module still works correctly (i.e. Regression testing).
Definition of done
Our approach includes a clear definition of a finished product. A project is considered completed when all the following statements are true:
Regression testing was done in the last phase of development.
The product doesn't have any critical bugs.
The product fully matches the required design unless otherwise stated/agreed with the customer.
The development process is completed, code is transferred to a client's repository.
All project closure meetings are held according to the selected methodology (Final Product Demo).
Business objectives are fulfilled, and all acceptance criteria are met and ready to be accepted by the Product Owner (you).
When these benchmarks are reached (and only when they are reached), your software is ready for release.
We create high-quality software solutions
Fill in this form orsend us an e-mail