Jul 12 | 05 min read
When we talk about increasing the speed, the very first question was about where we needed to increase the speed. As the first step, the team started categorizing the bugs under various categories so that the appropriate prioritization can be done which will help in mapping the efforts that go into solving the bugs. The team also worked on priority setting internally. This helped the engineering team to channel their efforts and ultimately resulted in increase in the speed of the complete process. The team also realized that in order to focus on the high-priority new bugs, the solving of old bugs must not take a back seat. The team aligned themselves with the support team to prioritize the bugs in such a way that the team can maintain a balance between the new bugs raised and the old backlogs.
As the famous framework, OODA states: Observe, Orient, Decide and Act; the team observed the changes that needed to be done while executing the plan for achieving the target of zero bugs and they simultaneously oriented themselves on the go. This was followed by quick decision-making and action. This framework ensured that the speed of the process keeps on increasing without even compromising the quality.
The process evolved over 2-3 quarters and after multiple iterations and we were able to successfully bring down the bugs count to zero. This happened on a new year and was a perfect example of smart work, perseverance, and consistency. What seemed like just a lofty goal in the beginning, eventually ended up being an achievement for the team.