A combination of Agile and Waterfall methodology.
RAPID-M an exclusive framework developed and used by N-Tech is an efficient combination of Agile and Waterfall methodology.
We have embedded responsive agile processes into our development framework by varying our documentation and “Behavior Mockups”.
We give our clients a complete flexibility to make as many iterations they want, in the documentation stage and then in the Mockup stage.
Our “Behavior Mockups” are well furnished and provide a crisp clear idea of how final product/software/system is going to perform and look like. Just like Agile development, we provide a working model at a very initial stage, which can give a better idea and required tangibility to the client.
We take full ownership of the project
We take full ownership of the project and provide an effective consulting to our clients, suggesting extra features, flow, additional modules, design and functionality based on our competitor research model, and customer centric model. As per the new iterations and varying project scope, we create a “Change Document” instead of making changes to the original S.R.S document.
Thus we incorporate most of the Agile development components in the Documentation and “Behavior Mockup” model stage itself. This helps us to limit the iterations at the coding stage, and allows us to develop and deploy a full featured product/software/system which was conceived by our clients. This also helps us to reduce the time to market, as the time taken to implement the iterations at the mockup stage is less.
Stages of RAPID-M framework
Stage 1Requirement Gathering
Stage 2Analysis and questions
Stage 3Feasibility Study
Stage 4Our Understanding of the project (U.O.P)
Stage 5Final Project scope from the client with the list of all the features
Stage 6S.R.S document 1st Draft
Stage 7Client iterations related to the features, functionalities and modules
Stage 8S.R.S document 2nd Draft
Stage 9Client iterations if any
Stage 10Final S.R.S document with the cost (This document also contains assumptions and cost related to the some of the features which the client may add during the course of development)
Stage 11Wireframe of the product/software/system
Stage 12Client iterations regarding the flow of the system, navigation and data fields
Stage 13Client iterations regarding the flow of the system, navigation and data fields
Stage 14Client approval of the Wireframe
Stage 15U.I design 1st Version
Stage 16Client iterations related to the look and feel of the U.I and positions of various elements on the screen
Stage 17U.I design final version
Stage 18Client approval of the U.I design
Stage 19Screen integration of U.I design with the approved flow (shown in the wireframe)
Stage 20Client Iteration related to the flow and data elements
Stage 21Final versions of the screen integration
Stage 22Database design
Stage 23Database design approval and back
Stage 24Back end admin coding
Stage 25Web service development and testing
Stage 26Web service integration (Module wise)
Stage 27Client testing (Module wise)
Stage 28Implementation of the “Change document”
Stage 29Bug fixing if any
Stage 30Third party integration if any
Stage 31Final testing and Demo
Stage 32Deployment online, or on play store, itune store
Stage 33Apps live on play store, and itune store
Stage 34Final testing of the system using live apps
Stage 35Official Closure of the project