Product Engineering

In open-ended/vague / no documented requirement scenarios, we propose a pre-engagement discovery session where our SMEs work with you to translate the requirement. Describing your vision, business model, solution idea, timelines, budget, and reference product over a quick call, scribe notes, or video recording can be a good starting point. Afterward, we apply the divergent & convergent thinking principles to define the in-scope, out-of-scope, boundary conditions, assumption, risk factors, solution architecture, and budgetary estimates.

We analyze your product vision, feature lineup, performance, availability, and security requirements to choose the right solution architecture that is easily maintainable, testable, and isolatable. Our Solution Architect and Functional SME will organize a whiteboarding session and recommends the best fit among the proven patterns – Layered (MVC), Client-Server, Event-Driven, Microkernel, and Microservices.

We continuously observe the market reports on top programming languages, frameworks, databases, web servers, and serverless cloud stack, evaluating them against time to design, development cost, community support, and security breach history. Then we pick the right tools & technologies based on your business case, delivery timelines, peripheral stack, system load, userbase, and skillset availability to support in the future.

We follow the 12 Factor App Methodology for building scalable, independent, and resilient enterprise products. It defines best practices for developing Software as a Service focusing on service level codebase separation, dev/test/prod environment parity, infra as a code creation, build separation, and deployment automation. We also follow the CAP theorem for creating a distributed data store system to overcome unavailability and network failure.

We collect your application’s technical, functional, process, and domain knowledge from your incumbent vendor or in-house team through our proven knowledge acquisition and validation practices. In scenarios of no documentation or limited SME support, we assign a cross-functional team to do the reverse engineering on your ecosystem and create a knowledge repository with as-is and to-be roadmap documentation.

We follow an agile project delivery model with a two-week sprint cycle to create frequent team connects, increase visibility, reduce knowledge gaps, and accommodate scope changes quickly based on user feedback. Our project delivery CoE – a team of technical and functional experts acts as a support system for audits, training, and guidance. Our Project Manager and Client Partner work as risk mitigation managers and prevent unexpected outcomes.