Project Team

1. Account Manager/ Project Manager 
The project manager has full control of the strategic client account and client’s all projects. Its success or failure rides with the account manager or project manager. e-Zest follows the accepted norms of software industry that the account manager/ project manager is responsible for keeping the project on schedule. The roles above the AM/PM can, of course, influence these decisions, however, final decisions on behalf of e-Zest are left up to that AM/PM.

2. Project Coordinator/ Project Leader
The project coordinator is the person responsible for all the communication and project specific issue handling. Project coordinator/ leader is generally involved with the project specific issues. He further is responsible for the team-members coordination and also in preparing , tracking and reporting the project schedule.

3. Solution Architect/ System Architect/ System Analyst
The solution architect is generally a person who has worked with the client for coming up with the business solution for the client and might have come-up with the technical solution as well. The SA can work either for the user community or development team. This is the person that coordinates, gathers, refines, defines, and prioritizes the various user requirements. The SA takes the business requirements and the database specification and develops the software specification at the highest level. The SA is also responsible for selecting tools used for development/ deployment.

4. Team Leaders/ Tech Leads
The tech lead is the technical expert involvement into all the technical aspects of the project. He is the secondary point of contact on the project specific technical issues in absence of the Project coordinator project leader.

The TL works with the system architect to flush out the details of the software specification. The TL understands the big picture, the goals and high level architecture of the application and charts out a plan for its accomplishment.

5. Software Engineers/ Programmer
A regular programmer works with the TL to code specific tasks. The software engineer at this level may not have the understanding of the whole picture. In fact, this position is usually told very specifically what and how to code. On most projects, there are no programmers (just lead programmers). The exception is large and very large projects.

6. Test Leaders
Test leader’s primary responsibility is to organize, supervise and direct the testing efforts.

7. Test Engineers
The person or persons that test the software prior to deployment responsible for complete functioning of the software without any error/defects.

8. Database Administrator
The Database Administrator (DBA) takes the business requirements, and develops the database specification. The database specification contains all the table names, field definitions, data restrictions, trigger definitions, and stored procedure definitions. The DBA is also responsible for creating and modifying the database. Optionally, the DBA can give permission to the programmers to alter the database directly.

9. Software Quality Assurance Executive/ Process Tester
The process tester, also known as process quality assurance, is the person or persons that double checks the requirements, design specification, and facilitates code reviews. The project manager, system architect, or a senior quality analyst often fills this role.

The SQA executive reviews (and often creates) all test plans. He is one of the members of the e-Zest’s Software Engineering Process Group (SEPG). SQA executive initiates and control all the quality related activities in the project as well as company.

10. System Administrator
System administrator is a person responsible for well functioning of the e-Zest’s networks, systems, development and testing environment.

11. Japanese Management Experts
e-Zest’s has implemented ‘Gemba Kaizen’ and ’5-S’ (Japanese Management Productivity improvement Techniques) with the help of these experts. They help to improve continuously different process in the company.