ERP for Plastic Woven Sack Industry, Ecommerce Web Site Developer

The methodology listed below is the broad guideline that we follow ensure timely and systematic offshore software development. We adapt the methods to suit the project complexity and client requirements.


	Define Project Objectives
	Business Purpose statement from client: This will tell us the purpose / objective to be achieved
	Project Dictionary:- We request the client for a glossary of words and phrases unique to the project that we need to understand. This will help in communication and understanding of requirements
	Detailed Project specifications (Scoping document) (information should be sufficient to enable us provide an estimate)
	Decision on OS, backend, development technologies, browser and screen resolution
	Agree on required documentation


	Commercial Approval
	Provide time and cost estimates
	Determine the number of resources required
	Await commercial approval from client


	Documentation & Planning
	Receive detailed User Requirement Document from the client
	Functionality statement. This translates the user requirements and defines the specific functionalities to be covered in the application / website. This will form the base for detailed system design and development as listed below.
	LFP, Low Fidelity Prototyping:- This is literally a paper and pencil representation of the user interfaces of the application. Each Paper represents a screen along with comments. There maybe multiple papers corresponding to a screen to depict the changed appearance on click of a tab. Comments on the page will highlight salient features and the list the name of the next screen
	Data Model:- We prepare a database model with field names, size, relationship diagram
	Essential Use Case:- (If required) This will define how the user interacts with the system and how the computer responds. We list the validation of each data input. The essential use case supplements the LFP and Data Model and is prepared if required
	Process flow diagram for back end processes is prepared for complex processes. This will depict the transformation of data as it logistically traverses the users and the applications
	Template for approval of look and feel and formatting. In case of websites we offer our client a few design options and based on feedback prepare the final template. In case of client server applications a detailed layout specification is sent for approval
	Submission of Milestone Document
	Finalize hardware & network configuration and flow of data

	Coding
	Start development
	Submit weekly progress vs. Milestone Document
	In case of web projects we will update a test site on completion of each module (deliverable). In case of client server projects SQL scripts, exe and installation instructions will be sent as per schedule
	Instead of email we will prefer a project communication tool like Groove or others (http://www.groove.net/home/index.cfm) for exchange of information, feedback and deliverables
	Hold prescheduled weekly chats on IM to review the project
	Submit required documentation at predetermined intervals
	Submit QA reports at regular intervals