Porting Legacy ASP Application to .NET

Quality Demand

Meeting the demand for quality was out biggest focus. We understood that these projects would be used by both government and private organisations all over America, so we challenged ourselves.

Resource Utilization

Finding and developers and other employees with the necessary talent is always a challenge, especially when very specific skill sets are required.

Software Familiarity

• The developers were not familiar with many of the tools needed for the project. This included Twilio for robo calling functionality, predesigned Crystal Reports, and reading mails from any IMAP source such as Gmail and Outlook Office 365. Efficiently learning and using the software, and getting the best outcome, was a challenge.
• We had to thoroughly understand the features of the old website by going through the old Classic ASP codes, then use that understanding to build the new website with new technology.
• The technical talent hired by the client lacked the accounting domain perspective.

Selective Hiring

We put a unique staffing solution in place with measures at every point of recruitment. We had started interviewing developers based on the skill sets we needed, and upon selection we arrange a direct interview session to help the client to understand what their developers are capable of.

Organization

After hiring suitable developers, we held client meetings to complete the requirement gathering sessions through Skype, WebEx and GoToMeeting online conference. We maintain project requirements and bug tracking through Helix ALM (formerly TestTrack) where all the tasks are maintained in monthly sprints.

Transparency

At the end of every sprint, we arrange client demos to verify and finalise the output. Usually we do the demo over GoToMeeting. Code structure and quality is maintained as per the client’s suggestion. As always, the team remains to support the software after it goes live and fix occasional bugs.