Decisions
The choices that shaped how we build at Bykea — documented with the context, alternatives considered, and reasoning behind each call. Because good decisions deserve a paper trail.
4 decisions documented
Structuring Engineering Into Cross-Functional Agile Squads As Bykea scaled engineering from 10 to 25+ engineers, the traditional functional team structure (separate dev, QA, backend, mobile teams) was creating handoff problems, slow delive... Read decision Transforming QA from Gatekeeper to Quality Assistance Bykea's QA team was the last line of defense before every release. Engineers threw code over the wall, QA found bugs, devs fixed them, repeat. This model was creating slow releases... Read decision Introducing Mandatory ISTQB Certification for the QA Team Bykea's QA team had grown from 2 to 8 engineers with very different backgrounds — some from manual testing, some from development, some self-taught. Inconsistency in testing vocabu... Read decision Choosing Appium + Python for Bykea's Mobile Automation Stack Bykea had 3 mobile apps (customer Android, customer iOS, partner Android) with zero automated UI testing. Manual regression was taking 3-4 days per release cycle. We needed to pick... Read decision