A large US based software developing company was willing to invest in a new business with a new software product which required much research on the actual requirement.

Though the company was confident about their investment but they didn’t have solid requirement of the product they wanted to build. Moreover, they wanted to do some study on the product to get the best out of it.

The company was planning to out source the development effort of their product but was totally unsure if any of the company will be able to handle the dynamic nature development cycle they would demand. After much study they wanted ReliSource to help to build their product.

 

 

 

 

ReliSource development team suggests a customized development process that suits best for their development need. The engineering team suggests the R-Process with extended prototype team to validate the product requirement with the client through out the development time of the product.

The development of the product started with two parallel team one targeting for rapid prototyping effort and other developing a solid framework. The prototype team started building rapid prototype and validate with the client to solidify the requirement. The team also put the finalized requirement in the SRS after the client validation. The development team after solidifying the framework started developing the product with the solid requirement from SRS.  

The development team started building the product in incremental fashion and deliver small build after every 3 weeks. The builds are tested by the SQA team for defects and performance. After several builds are done small released were introduced for client approval. 

Through the whole development cycle, client continuously provide feedback to the prototype team after validating the prototype and changes the product work flow as required. After the product workflow is solidified it was handed over to the development team for matured development. 

It is important to observe that the parallel prototyping approach deviate the norm of agile development process of using the prototype code in the real project. Where the pilot project normally get matured in time in the agile development methodology, this case the development team follow the throw-away prototype approach to get best quality code base.