RECOGNITION

All projects begin acknowledging customers exactly. While clients may sometimes be an institution, firm or corporation, may also be a person or just one section belonging to a legal entity. In this process business infrastructure is taken out by defining all the tasks and processes related to the customer. This step is the most time consuming and most important step for projects. Thus, the needs of customers are strictly determined.

IDENTIFICATION

After the determination of long term needs of customers, the long, medium and short-term goals are defined by considering all the system. All targets are divided into stages and the general plan is prepared.

ANALYSIS

Project analysis is done in accordance with the determined general plan. All transactions related to the project are examined in detail and documented. Project starts by submitting all analysis documents for the customer’s approval. Analysis process consists of the following steps:

• Defining the Project

• Configuration of the Project

• Presentation of the Project and Approval

• Initiation of the Project

PLANNING

Resources, budget and time schedule reports are prepared and submitted for approval. Planning process consists of the following steps:

• Scope Definition

• Event Identification

• Resource Planning

• Process Duration Estimates

• Cost Estimate

• Cost Budgeting

• Project Logic Diagram

• Quality Planning

• Risk Identification

• Risk Quantization

• Risk Response Development

• Organizational Planning

• Personnel Procurement

• Supply Planning

• Communications Planning

DESIGN

Complexity of the application is determined in terms of integration, security, performance, databases, platforms, specifications, scalability, modularity and maintenance. Project is designed in terms of these guidelines and project design document is prepared. After everything clarified for the project, expert team is selected according to the project’s needs. Even this team can include insource or outsource members; it also can include freelance members. The only criteria while creating the team is the project basis expertise. At the end of the design process it is established that all the team adapts the design including the customer and alignment in the team is ensured during the project.

DEVELOPMENT

All processes before the development stage ensures this stage to be more clear, constant, consistent and easier to be completed. Considerations during the development stage:

• Being sure that detailed designs are compatible with high-level design. By organizing the system logically, distribution of the resources and reusable areas is simplified.

• Good coding practices and guideline applications is used. Too complicated areas for the coordinated detailed design are determined. Design and code reviews are performed in appropriate times to determine these areas.

• Development of good communication within a team structure issues is created. Project communication plan is put into practice.

• Early responsibility distribution such as database installation and conversion and the areas that requires responsibility is determined.

• Promotion points and guidance team is created. Control points for new team members are created and evaluations are made.

• Design objectives relating to security, performance, portability, scalability, modularity, maintenance and reuse issues are put forward and apply.

IMPLEMENTATION

Test is the most important issue in the implementation phase. Test is the most recent control to ensure the quality of the system to be delivered. Test scenarios should test not only expected functionality of the site but also all possible functionality and behavior. It is determined that the system is ready for the production by making application steps and application tests for the application phase.

OPERATION

After the implementation phase, the system needs operation at regular intervals and new need analysis documents should be prepared as an input to the renewal and improvement phase.

RENEWAL AND IMPROVEMENT

Within the project life cycle, making improvements in the system becomes mandatory for some reasons such as expansion of the customer's needs and advancing technology. In this case, the documentation of the steps recognition and identification must be updated and targets should be re-formed. Thus, each project in the system should be renewed and improved in parallel to the renewal and improvement.

All projects begin acknowledging customers exactly. While clients may sometimes be an institution, firm or corporation, may also be a person or just one section belonging to a legal entity. In this process business infrastructure is taken out by defining all the tasks and processes related to the customer. This step is the most time consuming and most important step for projects. Thus, the needs of customers are strictly determined.

After the determination of long term needs of customers, the long, medium and short-term goals are defined by considering all the system. All targets are divided into stages and the general plan is prepared.

Project analysis is done in accordance with the determined general plan. All transactions related to the project are examined in detail and documented. Project starts by submitting all analysis documents for the customer’s approval. Analysis process consists of the following steps:

• Defining the Project

• Configuration of the Project

• Presentation of the Project and Approval

• Initiation of the Project

Resources, budget and time schedule reports are prepared and submitted for approval. Planning process consists of the following steps:

• Scope Definition

• Event Identification

• Resource Planning

• Process Duration Estimates

• Cost Estimate

• Cost Budgeting

• Project Logic Diagram

• Quality Planning

• Risk Identification

• Risk Quantization

• Risk Response Development

• Organizational Planning

• Personnel Procurement

• Supply Planning

• Communications Planning

Complexity of the application is determined in terms of integration, security, performance, databases, platforms, specifications, scalability, modularity and maintenance. Project is designed in terms of these guidelines and project design document is prepared. After everything clarified for the project, expert team is selected according to the project’s needs. Even this team can include insource or outsource members; it also can include freelance members. The only criteria while creating the team is the project basis expertise. At the end of the design process it is established that all the team adapts the design including the customer and alignment in the team is ensured during the project.

All processes before the development stage ensures this stage to be more clear, constant, consistent and easier to be completed. Considerations during the development stage:

• Being sure that detailed designs are compatible with high-level design. By organizing the system logically, distribution of the resources and reusable areas is simplified.

• Good coding practices and guideline applications is used. Too complicated areas for the coordinated detailed design are determined. Design and code reviews are performed in appropriate times to determine these areas.

• Development of good communication within a team structure issues is created. Project communication plan is put into practice.

• Early responsibility distribution such as database installation and conversion and the areas that requires responsibility is determined.

• Promotion points and guidance team is created. Control points for new team members are created and evaluations are made.

• Design objectives relating to security, performance, portability, scalability, modularity, maintenance and reuse issues are put forward and apply.

Test is the most important issue in the implementation phase. Test is the most recent control to ensure the quality of the system to be delivered. Test scenarios should test not only expected functionality of the site but also all possible functionality and behavior. It is determined that the system is ready for the production by making application steps and application tests for the application phase.

After the implementation phase, the system needs operation at regular intervals and new need analysis documents should be prepared as an input to the renewal and improvement phase.

Within the project life cycle, making improvements in the system becomes mandatory for some reasons such as expansion of the customer's needs and advancing technology. In this case, the documentation of the steps recognition and identification must be updated and targets should be re-formed. Thus, each project in the system should be renewed and improved in parallel to the renewal and improvement.