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 1
Requirement GatheringStage 2
Analysis and questionsStage 3
Feasibility StudyStage 4
Our Understanding of the project (U.O.P)Stage 5
Final Project scope from the client with the list of all the featuresStage 6
S.R.S document 1st DraftStage 7
Client iterations related to the features, functionalities and modulesStage 8
S.R.S document 2nd DraftStage 9
Client iterations if anyStage 10
Final 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 11
Wireframe of the product/software/systemStage 12
Client iterations regarding the flow of the system, navigation and data fieldsStage 13
Client iterations regarding the flow of the system, navigation and data fieldsStage 14
Client approval of the WireframeStage 15
U.I design 1st VersionStage 16
Client iterations related to the look and feel of the U.I and positions of various elements on the screenStage 17
U.I design final versionStage 18
Client approval of the U.I designStage 19
Screen integration of U.I design with the approved flow (shown in the wireframe)Stage 20
Client Iteration related to the flow and data elementsStage 21
Final versions of the screen integrationStage 22
Database designStage 23
Database design approval and backStage 24
Back end admin codingStage 25
Web service development and testingStage 26
Web service integration (Module wise)Stage 27
Client testing (Module wise)Stage 28
Implementation of the “Change document”Stage 29
Bug fixing if anyStage 30
Third party integration if anyStage 31
Final testing and DemoStage 32
Deployment online, or on play store, itune storeStage 33
Apps live on play store, and itune storeStage 34
Final testing of the system using live appsStage 35
Official Closure of the project