"Seize the day."
Approach
Insonix team focuses on client satisfaction by rapid delivery preferably in weekly iterations, with the first three iterations focus on delivering key features the last iteration every month is meant for bug fixing and refactoring code. The team is passionate about fulfilling the vision of the client and the team is always ready to receive change requirements at all stages of the SDLC, while managing the expectation of clients and providing them with effort estimates corresponding to these changes.
Graphic designer initiates work on Adobe Photoshop and creates PSD’s of the front layer , once signed off by the client they are handed over the front end developer for cutting in CSS/HTML, simultaneously our CTO overlooks creation of the Database and the middle layer. Right from the beginning we like to host the prototype and later the working web application on our development-server that is password protected and can be accessed by clients and other key stakeholders.
To measure the performance we use our project management tool, the most preferred being Redmine and we look forward to client representative to be a part of the project on the PM tool. The definitive measure of performance is a “working feature” which is first passed by our QA and then finally closed by the client on the PM tool.
The key to success is communication with the client and the project coordinator is available on daily basis, if possible we encourage client representative to be a part of the daily stand up scrum meeting on skype. We always prefer to set up auto-deployment script for our code and developers are trained to do the following before the code is deployed on the deployment-server:
- Use frameworks for Java and Flex
- Unit testing on individual machines
- Revision Control and continuous integration on our local testing server
- Working closely with the tester and focus on correcting errors as early as possible on all browsers (some times even in IE6 if the client so demands!)
- Code Review and Code re-factoring every forth sprint
- Getting a build failure email is considered as “grave lacking” on part of the developer
Insonix uses the following tools to maintain quality objectives: Maven, Ant, Hudson, SVN, Redmine, JUnit, JMeter
