 |
Quality |
|
Tekfi ensures high service quality through its standardized process and clear communication. We employ dual-management approach to ensure the delivery quality and communication quality at the same time.
Tekfi assigns two leaders to each project:
| Project manager |
| Project manager, the technical leader for the project, is responsible for the technical success of the project and make sure everything gets delivered on time and with high quality. |
| Client manager |
| Client manager is responsible for all communication and documentation of the project. He/She is a single point of contact for all client communications – reporting, updates to requirements, status tracking and so on. All project coordinators speaks clients’ language and understand their culture. |
|
|
Process |
|
Tekfi’s standard project development process has been mostly influenced by RUP and MSF. Projects are executed iteratively; with most iterations consisting of the following phases (MSF):
| Envisioning |
| During the envisioning phase, the team and the customer define or refine the business requirements and the overall goals of the project. Alignment of business and IT priorities in this phase is crucial, and the team will spend time understanding how the architecture will be used. During this phase, the team also begins identifying and mitigating risks. The envisioning phase culminates in the vision-approved milestone, which indicates that the team and customer agree on the project direction. |
| Planning & Designing |
| During the planning phase, the team plans the development and makes requirements more specific. The end of the phase is marked by the approval of the project plan by the customer. |
| Developing |
| During the developing phase, the team moves from project planning into the projects themselves. |
| Stabilizing |
| During the stabilizing phase, the team collects and integrates feedback on the released version, resolves project-related issues, enhances the architecture, and prepares for the next version. |
We implements unified standards in place for Configuration Management, Code Styles and Project Documentation. |
|
Requirements management |
|
| For remotely implemented projects, it is essential that requirements are assessed, analyzed, and updated accurately and effectively. Tekfi has an established requirements-assessment procedure in place. As part of the standard process, the Project Coordinator and Project Manager go from top to bottom, from understanding the client's business processes to creating workflow models of the software to be built and down to creating technical requirements for software. Every step is documented and approved by client along the way. |
|
Requirements Change management |
|
| Tekfi recognizes the need to accommodate requests to make functional or operational changes to the system. All requests for changes will be submitted through the project supervisor on the client side. Tekfi will estimate the cost of the change, schedule and system impact of the change. This analysis is delivered to the Supervisor. |
|
Change procedure standards |
|
Tekfi follows certain fundamental principles when making any change:
| Making any change must not affect the integrity of the system |
| The system must be consistent, both in the working procedures (i.e. data entry, reporting, etc.) and user interface. Therefore, all changes must be done in alignment with existing system style |
| A change must be properly documented and change development must be planned and executed |
| A list of changes must be traceable |
| Software code repository must permit rolling back to any previous system version |
| Deploying an updated system should have minimal or no affect on the normal work cycle |
|
|
Document sharing and management |
|
| Typically, project documentations are maintained in a centralized repository accessible to a client over the web. |
|
