Android, to parity with iOS.
The team reviewed the inherited code, spent two sprints refactoring it onto a persistent storage and sync framework, then built the features that brought Android level with iOS before the commercial launch.
Mido Lotto brought us in for three months to add five people; within two it extended the engagement to a year and handed us Android development and quality assurance outright.
Mido Lotto is a San Francisco technology company building a lottery-as-a-service platform: iOS and Android applications for players to buy tickets, check winning numbers and collect winnings, and the cloud database, API and messaging services behind them, sold both direct to consumers and to government agencies that want to digitize their lotteries. It was seed funded by SherpaVentures and other angel investors.
When we met, the product was eighteen months in and heading for its first production release. The server was 80 percent complete and the iOS application 90 percent; Android and web had only just started, with independent contractors in Eastern Europe who did not work well as a team and did not take ownership of the product, so quality suffered. The Android application had also been built without persistent storage: every launch downloaded everything again, which meant latency, data use, battery drain and nothing working offline.
Like most startups, Mido Lotto wanted to move faster at lower cost, and like most startups it found an outsourcing partner appealing financially and daunting operationally. The product owner and scrum master roles were being carried by overcommitted executives, so stories were estimated on developer tasks alone, had no definition of done, and the backlog held only the next sprint, with no view of the release burndown. Finding the right partner mattered for product-market fit, for the user base and for the Series A.
Three objectives at the start: port iOS to Android, raise product quality, and improve product planning and agile execution. Here is where each one landed.
Mido Lotto engaged us for three months to add five development and quality assurance people as an extension of its internal teams. After two months it extended the relationship to twelve, and over time handed us full responsibility for Android development and for quality assurance. In all, our people doubled the company’s size and quadrupled its product development organization, working as a seamless extension of its staff.
The team reviewed the inherited code, spent two sprints refactoring it onto a persistent storage and sync framework, then built the features that brought Android level with iOS before the commercial launch.
A surrogate quality assurance manager, one engineer each inside the iOS, Android and web Scrum teams, and one on test automation; a test case management system replaced the spreadsheets within the first three months.
Release and sprint planning, story definition and estimation with quality built in, and a new issue-tracking and agile management tool with a workflow the whole company now runs on.
Alongside the two teams we provided iOS developers, a requirements analyst for user stories and use cases, and a project manager and scrum master for Android. Technologies: Java, Swift and Amazon Web Services.
“Tangibly, CodeStringers provided Mido Lotto with a team of software development, quality assurance, requirements analysis, and project management personnel at a lower cost than internal resources. Intangibly, CodeStringers acted as a seamless extension of our company and provided deep agile development methodology expertise that improved our entire organization’s productivity and efficiency. CodeStringers raised the bar for our company holistically.”
“The CodeStringers team easily rivals the quality of any Silicon Valley software engineering organization. Working with CodeStringers, our software quality improved, our development velocity increased, and our financial runway extended.”
Within the first three months the quality assurance team had replaced the spreadsheets and expanded the test suite; the engagement grew from there.
More test cases.
The automation framework and tools expanded the list of test cases by 350 percent, each with step-by-step instructions and expected results.
Of test cases automated per sprint.
One engineer automates seven percent of the total test cases every sprint while dedicated testers cover each development project.
The product development organization.
Our people doubled the size of the company and quadrupled its product development organization; a three-month engagement became twelve.
The numbers are Mido Lotto’s, as the case study on the previous site reported them.
A seamless extension of the client’s team is still how we work; what the team builds has changed.
Business systems are moving from applications that record and route to agentic surfaces that reason and act, a paradigm shift we are driving. The quality function, the definition of done and the release plan you read about here are built into every managed solution we run: the agents do the regression, the routine checks and the reporting, and a person approves what matters.
The capability under this engagement: dedicated teams with their own product, quality and project people.
A quality function inside every development team, from test case management and manual testing to release sign-off.
Frameworks and tools that grow the suite and shrink the regression time per sprint.
Native iOS and Android applications built for performance, offline use and the features still to come.
A dedicated development team is a group of engineers, testers and, usually, a project manager or scrum master assigned to one client's product full time for an extended period. The client directs the work through its backlog; the provider supplies, manages and replaces the people. It differs from a project contract in that scope changes without a new agreement, and from staff augmentation in that the team carries responsibility for an outcome, such as an entire application or the quality function.
Staff augmentation adds individuals to a client's existing team under the client's management; each person fills a seat. A dedicated team takes ownership of a defined area, brings its own leads and process, and is accountable for the result. In this engagement both were used: individual iOS and backend developers as augmentation, and full teams for Android and quality assurance that owned those functions outright. Most engagements start as the first and earn the second.
A QA function is more than testers. It is a test case management system holding every case with steps and expected results, an automation framework that converts a share of those cases to automated runs each sprint, a QA engineer inside every development team so testing happens during the sprint rather than after, and a manager who owns the quality bar and release readiness. Spreadsheets of test cases and late defect discovery are the symptoms of not having one.
Without it, every launch downloads everything again. The user waits, the data plan and battery pay for it, and nothing works offline. A persistent storage and sync framework keeps a local copy of the data the app needs, shows it immediately and reconciles with the server in the background. Retrofitting it onto an app built as a thin client means refactoring before new features can be added, which is why it is a decision to make at the start.
A definition of done is the acceptance criteria a user story must meet before it counts as complete: the functional cases, the negative cases and the quality bar. Without one, developers estimate the coding alone, testing is left out, and stories roll over sprint after sprint. Estimating against a firm definition of done, with quality tasks included, is what makes a release plan for alpha, beta and launch something a team can keep.
Where we're not the right answer
We are not the right answer if you want seats filled and nothing more: every team on this page carried its own product, quality and project people, and the planning gates came with it. Services by the estimate are available today; the long-term focus is the managed solutions.
Every engagement on this page began with a conversation about what was slowing the business down. Tell us yours and we will say, in plain terms, whether we are the right answer, what it would take and what we would measure.