At Active Development, ​We write code based on the product specification and test it.

The development phase involves writing the actual code of the system, developing and deploying the system's hardware, and preparing the primary test data. This stage includes writing polished code based on the product specification and the requirements agreed upon during the previous stages.

Here, the team meets the goals and outcomes set during the discovery stage by implementing a solution. The coding process involves multiple tasks, each of which has its own unique characteristics.Our developers in Mad Devs follow a set of coding guidelines and best practices in order to make sure that the software they build is secure, reliable, and portable.

Active Development step by step is:

Step 1. We break big tasks into
smaller chunks

At this stage, the development tasks are broken into pieces. We break down the milestones into epics, within which we create tasks, which are further broken down by developers into even smaller tasks. Going piece by piece allows for time to review and get feedback to make sure the development process is on the right track.

Step 1. We break big tasks into smaller chunks

Step 2. We arrange communication channels with you

We set up communication channels (Slack, JIRA) to enable proactive communication with a client to allow him to ensure the total transparency of all processes. In fact, Mad Devs has long adopted the principles of asynchronous communication for more collaborative and effective team.

Step 3. Continuous integration
and continuous delivery are our
standard practice

We set up CI/CD pipelines (Gitlab, Github) to freely and continuously deliver code to test/demo/staging or production instances automatically and without any need for human actions.

Step 3. Continuous integrationand continuous delivery are ourstandard practice

Step 4. We run tests

At every step, the code is systematically tested to detect and minimise bugs. We cover all code in tests to ensure the top-quality of the product we deliver.

Step 5. We build radiators to track business metrics

We build custom radiators to track business metrics and see whether a specific feature brings business value:

Step 6. We use logging and
alerting tools

Other issues to help prevent downtime. They can also be used to monitor and resolve various issues within an organization's networks. Alerting tools notify us about incidents and errors so that we can fix them without delays. We use logging tools to track the process in detail. Time logging has significant benefits for project management, team productiveness and planning:

Step 6. We use logging and alerting tools

After Development stage we can move to QA and Testing.

Case Studies

Build your solution with Mad Devs

We build products to solve complex business challenges.

Mamed Nuriev

Mamed Nuriev

Delivery Manager