Client’s team shares the detailed requirement (BRD document).

TechBulls TL will define the sprint of two weeks based on the estimates by TB and priorities of the features defined by Client.

A Technical Design Document is created by TB and Client which is based on BRD Document that includes user size, server infrastructures, database, scalability parameter, security type and performance to design system.

In This document TB define Domain objects, User stories, identify core components & frameworks, tool & technologies to use, code scope considering all aspects of High availability, Disaster recovery, Audit, Securiy, Monitoring, Traceability etc.

In this stage UI Prototypes give glipms of final project.

SPR (Software Product Revision) document is prepared, which includes User stories (covers test case coverage), and code scope (request/response structure, API behavior, DB interaction, etc). Any impact on the existing functionalities if applicable.

On reviewing the SPR document jointly, and making all the necessary amendments a development will kick-off.

Build an initial version of the core framework which solves patterns of common problems. Create interfaces to which other developers can code. Architects and Sr. Engineers are involved during this activity and closely govern development of critical parts of the system.

Team works on developing the actual business logic with the help of components and libraries that are built. Architect ensures the implementation as per expectation (component integration wise not necessarily business problem wise)

After committing the code to the repository automated code checks analyzer (which is pre-defined by the team leader with all the standards to be followed) will be executed and if the code fails to match it will reject the check-in.

Manual / Automated QA is performed on the deployed build by the QA team. If there are certain performance loads to be tested a Performance Testing will be performed. If any issues are found all of them are reported in an issue tracking system. Once a QA is completed, the team lead will incorporate the issues in the next sprint or current sprint based on the criticality and Development -> QA cycle is followed. QA sign off is given after everything is working as expected.

User acceptance testing is done as per the define & design document & sign off is given if everything is working as expected.

Once a UAT is successfully completed a build is promoted to a Pre-Prod environment to check the sanity of the application with the infrastructure.

A final Deployment is done to production after verifying everything on Pre-Prod environment.