- How many development resources do you usually assign to a project?
- Can you provide the summary of the experience and skills of each of your application development resources?
- Do you guarantee the security and confidentiality of our intellectual property?
- Do your development resources make use of any version control repository?
- Do you practice code reviews? If yes, how frequent is that?
- What is the standard practice you follow for code comments?
- Do you provide system documentation?
- Do you provide end-user documentation?
- How do you handle change requests from your customers?
How many development resources do you usually assign to a project?
The number of resources employed for a project depends entirely upon the scale and complexity of the project. For example – we allocate two developers, one tester and a part-time UI designer for a small project. In addition, each project will have a Technical Architect, Business Analyst and Project Manager. We can increase the number of resources depending upon the customer/project requirements.
Can you provide the summary of the experience and skills of each of your application development resources?
We are bound by the confidentiality agreement, and will be unable to share these details. A large number of full-time developers are a part of our pool, working on different in-house and client projects. At different times, the available resources are different and unique. You can be assured that only the best quality, trained and experienced resources will work on your project and meet your requirements.
Do you guarantee the security and confidentiality of our intellectual property?
This clause is covered in the IP contract, and NDA is also signed between Curl Labs and the customer specifying the same. The same clause is also covered in the contract signed between Curl Labs and its employees. In addition, we audit our processes and train employees on a regular basis. These efforts ensure that our customers’ intellectual property is always secure.
Do your development resources make use of any version control repository?
We use Git as source code and version control repository. In addition, we are experienced with Visual Source Safe, Team Foundation Server, and other popular version control systems.
Do you practice code reviews? If yes, how frequent is that?
A Peer Review practice is a part of our standard development process. Any code developed by an application resource is always verified by another application resource. Only after verification is the software released for testing. This practice is applicable only when the customer hires more than one developer.
What is the standard practice you follow for code comments?
While we feel that providing comments for all public methods is a good habit, we comment only when it is “truly required”. For instance, we avoid commenting on codes that have the correct method name. Through this practice, we avoid over-commenting and create codes that are easy on the eyes.
Do you provide system documentation?
We provide the SRS documentation to the client. The code will have comments to facilitate easy comprehension. Our documentation is comprehensive and self-explanatory.
Do you provide end-user documentation?
We will provide end-user documentation if the clause is included in the work contract and quoted by Curl Labs.
How do you handle change requests from your customers?
We have a standard procedure of handling change requests from our customers. Firstly, we seek their approval for any change request. After the customer approves the request, we do an impact analysis. This allows us to deliver the timelines and cost estimates to the customer. Once the customer approves the estimates, we implement the changes.