Codest Playbook

Looking for a set of rules and our approach to software development projects?
Find out how we code and build products for our clients. Discover more!

See more

This is our Playbook

We have prepared this document based on our experience in cooperation with clients from different parts of the world. We have gathered good practices related to software and product development as well as project management methods.

In our Playbook, you will also find a step by step guide on how to establish cooperation with Codest as a software development company. We show in detail how our daily cooperation looks like from our and client’s perspective.

Learn more about our company and approach to software development by discovering articles of your interest.

How do we implement the requirement analysis?

The purpose of the requirement analysis is to create a general outline of the project's operation, establish an action plan through which the project will be implemented, and, if possible, identify the tools to be used. There is no simple recipe for requirement analysis.

Our approach to customer journey

Every successful business cooperation needs to start somewhere and somehow by one of the partners initiating the first interaction. In our software house setup, the new business team plays the leading role in assisting the customers on their journey with their inquiries.

Code review best practices

Code review is another topic in the series about best practices for building software. At Codest, it is an organization-wide belief that great code reviews benefit everyone involved. Why is this important, and what is our approach to code review? Discover it!

How do we do estimation?

One of the most difficult elements of an IT project is the right estimation. In our organization, we pay special attention to it because of our many years of experience. A conscious customer is also very important for the efficient implementation of the valuation.

Product from scratch – UX design

Creating products from scratch is a challenging process. First, we must think about the appropriate UX Design. Why UX not UI? Well … a beautiful but unintuitive product is useless, so we should focus on user-centered design, always and forever. 

Customer Success Management

It is all about making the client happy with our services. Once the deal is closed by the new biz team, the customer success manager is added to the conversation between the new client and the team, so he can drive the consumption of our services and bring them value.

Project management in SCRUM

SCRUM is a project management methodology based on empirical process control theory, which is consistent with the values of the Agile manifesto (2001). This is not a restrictive work methodology but rather a framework that allows you to provide software without having a vision of final shape straight away.


This document was written in order to unify the internal company Git Flow rules. This method is not introducing pure Git Flow, as it is a mix of both Git Flow and GitLab Flow, with best company practices worked over many years. It helps keep a clean and readable history of the repository and better control over changes and project lifecycles. 


CircleCI is a very simple tool that is well-configured as a supervisor of our projects. But is the configuration itself simple? This, of course, depends on the complexity of the project. In our case (mono repo) it turned out to be more difficult than expected.

Project documentation

They say that when we meet someone for the first time, that initial impression is the most important one. The same applies to a project code repository. A well-written README is crucial not only for current developers but also for future ones. It introduces the project and provides step-by-step instructions that allow quick setup and contribution.