In HT we know that it is impossible to have a unified approach to every project. Large projects must have higher level of processes maturity and internal complexity than small ones that can have no formal processes at all and still be very successful. Large and small scale projects must controlled at each phase to avoid failures. We are using a wide set of well known software development methodologies depending on customer requirements. We believe that HT is a truly customer oriented company, so the idea is to be as much flexible and transparent for our clients as possible.

We adopt our project methodologies to the needs of our clients making our processes homogeneous with the existing ones, thus assimilating into client’s working environment. We have defined and institutionalized the minimal set of practices that are used in every project in one or another form:

Requirements Management

Clear project requirements are the key point to be successful in any software development project. Team must know exactly what client wants to have at the end of the project. In some cases it is very difficult for a client to provide team with specifications detailed enough. In HT Inc we assign local Business Analyst to convert customer needs into software development specifications. The Analyst is a gate between software development team and client.

Project Management

An ideal project is the project where requirements are stabilized before its start. But in fact we often have requirements changed during project execution that leads to additional risks, as far as new changes will affect system quality if they are not thoroughly controlled. Each new change of requirements must be deeply analyzed by the Architect/PM/Lead developer before its implementation and integration into the system.

Change Management

An ideal project is the project where requirements are stabilized before its start. But in fact we often have requirements changed during project execution that leads to additional risks, as far as new changes will affect system quality if they are not thoroughly controlled. Each new change of requirements must be deeply analyzed by the Architect/PM/Lead developer before its implementation and integration into the system.

Defects Management

New defects must be first assigned to responsible developers and then fixed. It is a good practice to use some defects tracking system for that purpose.