Software Development
Pod Configuration
Teams are grouped into sizeable chunks of 6-7 resources who are handpicked for the specific project and problem domain. This allows the group to work at a pace that's manageable and repeatable. Conversations dont go on and on... consensus is reached easily, and collaboration can happen without too many handshakes.
Code Quality
We ensure that the code we write at any point in time, could be released to production and so should be good enough to go. This means we are able to do a lot more, and move quickly than other traditional software houses. Time to market simply becomes a decision of enabling/disabling features in Prod, targeted releases for BETA users, build rollbacks, etc.
Automated Tests
The Pods will always endeavor to make sure that manual tests are only done when absolutely necessary. We invest heavily in writing automated tests at the same time as the code is written. Automated tests cover functional, regression, security and performance tests done throughout the product cycle.
Feedback Loops
The Pod is trained on working with multiple feedback loops within the product cycle. We have practices that are designed to provide immediate, daily, weekly and adhoc feedback from their peers and Product Owners. We make sure that no one is working as an island, and that the daily work output gets validated as early and quickly as can be.
Performance / Optimization
Part of what makes a successful app is its resilience to volume and tons of usage. We dont only make sure it works, we make sure it will continue to work even under the immense pressure of heavy loads and peek periods depending on the demands of our client's market. It's easy to write code to compute a value, but can the app do it while taking on 14 million other requests per hour?