I look at each day as a chance to move one notch above yesterday ... Pipedrive Supports Quality Releases while Deploying 50+ Times Per Day. -or- how we achieve a balance between speed and quality in Pipedrive
“I look at each day as a chance to move one notch above yesterday — whether it’s in service quality, delivery, speed, or any other aspect of the business.” — Daniel Snyder —
Customers are always on the lookout for solutions that are efficient enough to fulfill the need they have identified and which will also save them money. While companies work to produce something that is efficient and cost-saving, they also want their product to be considered high quality — Pipedrive is no exception. When you develop a product that not only offers top-notch features, but also stands the test of time, then you have a product customers can enjoy and you can feel proud of.
However, we shouldn’t lose sight of another indicator of value, (which can also influence quality) the speed of delivery. The focus on delivery speed comes into play to ensure a competitive advantage. On average, Pipedrive makes about 500 deployments to production per week, with more than 250 developers, and without a dedicated testing department.
The problem is that speed can come at the price of quality. Furthermore, keeping the balance also requires some effort. How do we maintain speed and quality for 10 years?Before we go into that, let’s first discuss the processes we’re following in Pipedrive.
To bridge the communication gap among the various teams working simultaneously, we follow DevOps principles in software development. This additionally helps enable faster delivery and feedback.
To adopt the DevOps process while not hindering the teams' release processes, we have nearly eliminated the need for a dedicated testing specialist. In our dev-centric environment, the developers are responsible for testing and deploying their changes. We bridge the gap by relying on _Continuous Testing _that is focused on test automation.
Instead of providing a safety net to catch failures, we are instead helping teams adapt. For this purpose, we have introduced several *specialized teams *such as DevOps, SRE, QA Analysts, Support Engineers, Infrastructure Engineers, Agile/Personal coaches, who support all the *tribes: *product development units aligned around certain product areas.
For example, the Site Reliability Engineering team is focused on collaboration with product and development teams to create scalable architecture while improving the performance, stability, and reliability of our services.
Now that you have a better understanding of what Pipedrive’s setup is like, we will move on to how we ensure fast delivery and built-in quality.
Hire our Dedicated DevOps Developers who have in-depth skills and expertise to develop an interactive and secure web application. Get custom DevOps solutions for your project.
Looking to hire top DevOps developers at affordable prices? **[Hire DevOps Developer](https://hourlydeveloper.io/hire-dedicated-devops-developer/ "Hire DevOps Developer")** from **[HourlyDeveloper.io](https://hourlydeveloper.io/...
See why mutation testing might be the answer for better quality tests and thus higher quality code.
Corona Virus Pandemic has brought the world to a standstill. Countries are on a major lockdown. Schools, colleges, theatres, gym, clubs, and all other public
This article covers A-Z about the mobile and web app development process and answers your question on how long does it take to develop/build an app.