Company - How we Work

IntelliGrape follows Agile methodologies for software development. Scrum and XP Practices form an integral part of our development processes.

We broadly follow the following steps for application development.

• Comprehensive and detailed analysis of the business needs.
• Segregation of requirements into small modules/iterations as per priority.
• Initiate design concept & programming on iterations.
• Client feedback on completion of each iteration.
• Block wise testing of application to get the real time feedback.
• Practicing Scrum and XP principals such as re-factoring, pair programming to eliminate redundancies and optimize efficiency.

Our core philosophy for web application development

Two-Way Communication

Though sounding rude, but we DO NOT want to work with a client who does not feel the need of clear communication. We believe in having a clear and two-way communication. We do not believe in having a guarded communication with our clients. We do not hesitate in sharing our problems/roadblocks with the client and prefer to give an honest and clear picture to the client. On the other hand, we also expect our client to elucidate the requirements as clearly as possible and provide us the feedback almost instantly.

Flexible Approach and Mind-Set

Though we expect the client to lay down the requirements clearly, but also know the fact that it is practically impossible to not to digress from the original requirement. By virtue of Agile delivery model, we are able to respond to business change quickly. Agile processes give us an edge, particularly for new application development where the detailed requirements are unclear or likely to change with time.

Small Iterations of 1-6 weeks

We apply time bound iterative and evolutionary development. Small iterations from 1-6 weeks, depending on the kind of application to be developed, are delivered to the client.

Track of Project Status

Our team conducts daily stand up meetings to provide the updates on the completed tasks and activities on daily basis. We track the status of project almost on hourly basis. An effective burn-down chart tracks both the amount of work required to implement a particular iteration and the work needed to complete the entire project.

Automated Functional Testing

We are quite religious about automated unit/integration/functional testing.