We use SCRUM for project management –
SCRUM status lets you know the daily visibility –
and weekly update


We provide you the progress of the week and interim releases will be beneficial for early comments update – etc.

The project will initially follow the iterative waterfall model – both requirements phase and design phase. During the development and testing phases, the SCRUM methodology will be used.

Project Engineering Process

As soon as the project contract is signed,

  • The Business Analysis team will start the analysis of the requirements and come up with a Full Scope Specification document.
  • The team will do the gap analysis with the Client and update the requirements document and get it approved by the Client.
  • This will be considered as the base line requirement for the project development.
  • The whole process will be managed by the project manager from the start of the analysis phase.
  • The requirements document will be handed over to the design team by conducting a technical review of the document.
  • The design team will do the DB design as well as the class design based on the high level design done by the Technical Architect.
  • Once the DB and classes are ready, the project manager will assign the relevant tasks to the developers and will follow scrum methodology to track daily tasks.
  • The coding will be done following all the relevant coding standards like Web Standards, Cloud Standards, and Server Side Standards etc.
  • The proposed website development will be completely based on the W3C guidelines for ensuring long-term growth for the website.
  • The release will be done based on the quality assurance process and the release process as mentioned below.

UI/UX Discovery Phase

Our methodology of UI/UX design ensures the best UI and usability for the customer.

Speed of Response & Execution

  • The proposed website will be up 97% of the time (24 x 7) with high TPS (Transactions per Second). For example, the home page will be up within 5 seconds from the time of selection.
  • The system will be user friendly with tool tips wherever required, proper key board navigation and readable fonts.
  • We will ensure the first 15 keywords to be focused to bring the home page in Google ranking in the first page.
  • The look and feel and theme will be based on the inputs given by the client.
  • A sample screen of the proposed system is included in the proposal.

Quality Assurance Process

We have a very stringent Quality Assurance Process with different levels of reviews for the documents and multiple stages of testing for the code. The following types of reviews will be conducted for every document that is delivered to the client.

All methodology documented and published in the system for the access of clients and partners

  • Peer Review – Any other capable member of the team will review the document and the author will incorporate the comments.
  • Group Review/Lead Review – Either the selected members of the team will review the document or the team lead will review the document in the final stage and the author will correct the errors.
  • The design will be reviewed by a technical architect before it will be used for coding.

Each code release will go through all of the following testing stages:

  • Developer testing / Unit Testing – The developer will do the initial testing of the code and fix the errors.
  • Lead Testing / Module Testing – Either the team lead or the tester will test the module as a whole and the developer will fix the errors.
  • Integration Testing – The testing team will be testing the system after integration with the relevant modules based on the integration test cases. The developer will fix the errors.

A final integration testing will be done, when the whole system is ready and integrated with all the modules. This will be done with the whole testing team and if required, the load testing will also be done by the testing team.

A round of Beta Testing will be conducted by the team for ensuring the following:

The user acceptance testing will be carried out by the Client, but if the user acceptance test cases are made available to the team, the testing team here will also conduct their own round of testing with the above said test cases.