To achieve our vision of becoming the leading superapp in Southeast Asia, we constantly need to balance development velocity with maintaining the high quality of the Grab app. Like most tech companies, we started out with the traditional software development lifecycle (SDLC) but as our app evolved, we soon noticed several challenges like high feature bugs and production issues.
为了实现我们成为东南亚领先的超级应用程序的愿景，我们不断需要在开发速度和保持 Grab 应用程序的高质量之间取得平衡。像大多数科技公司一样，我们一开始采用的是传统的软件开发生命周期（SDLC），但随着我们的应用程序的发展，我们很快注意到了一些挑战，如高功能错误和生产问题。
In this article, we dive deeper into our quality improvement journey that officially began in 2019, the challenges we faced along the way, and where we stand as of 2022.
Figure 1 - Software development life cycle (SDLC) sample
图1 - 软件开发生命周期（SDLC）样本
When Grab first started in 2012, we were using the Agile SDLC (Figure 1) across all teams and features. This meant that every new feature went through the entire process and was only released to app distribution platforms (PlayStore or AppStore) after the quality assurance (QA) team manually tested and signed off on it.
当 Grab 在 2012 年刚开始工作时，我们在所有团队和功能中使用敏捷 SDLC（图 1）。这意味着每个新功能都要经过整个过程，只有 在质量保证（QA）团队手动测试并签字确认后， 才会发布到应用分发平台（PlayStore 或 AppStore）。
Over time, we discovered that feature testing took longer, with more bugs being reported and impact areas that needed to be tested. This was the same for regression testing as QA engineers had to manually test each feature in the app before a release. Despite the best efforts of our QA teams, there were still many major and critical production issues reported on our app – the highest numbers were in 2019 (Figure 2).
Figure 2 - Critical open production issue (OPI) trend
图2 - 关键的开放性生产问题（OPI）趋势
This surge in production issues and feature bugs was directly impacting our users’ experience on our app. T...