Over the past few years, I’ve been busy building development processes in a large mobile app called Tinkoff Bank.

I talked about the evolution of approaches to its development last week in the framework of Highload++. In the same article Facebook’s whitepaper “Continuous Deployment of Mobile Software at Facebook” (Showcase)which they published at the end. 2016 years. The point is, on Facebook, 2012 During the year, there was an active transition to native development of mobile applications from just a mobile wrapper over a web application. The release cycles of Android and iOS were on 4 For weeks, the team was fine. 100 engineers. They were not happy with such release cycles and worked on their own processes. K 2016 During the year, the team grew 15 Once, and the release cycles were reduced — Android 1 once a week, and iOS 1 once 2 weeks. As the process progressed, it was important to monitor the Software quality did not deteriorate as the release cycle accelerated Productivity of developers did not decrease with the acceleration of the release cycle and increasing the team In the end, the guys wrote a document that we will consider today. This document describes how they built their processes and how they analyzed the effects of these processes. I believe that from this document you can learn a lot from experience and optimize your processes and their visibility for management.

#Processes #Management #WhitePaper #Software #ExternalReview