Essentially, the process of an IT project consists of 5 phases. Phase 1 – The Preparation In the first phase, the preparation, the basics for the project are determined. It is defined what the project is about and what the goals are. At the end of phase 1, a decision is made for or against the project. This decision is based on various factors, such as risks, benefits, costs and others. If the decision is made in favor of the project, phase 2 follows. Phase 2 – Project Introduction In this phase, the project is initiated and the framework conditions are clarified. This includes available funds, necessary work steps and tasks that need to be completed. Risks and opportunities are also evaluated in more detail. In addition, relevant stakeholders, i.e. people who have a (mostly economic) interest in the project, are informed. Phase 3 – Project Planning In the third phase, the course of the IT project is determined. It is important to understand that this phase is never really finished throughout the duration of the project, as there are constantly new factors that need to be considered. This includes available resources, necessary work steps, and tasks that need to be completed. In other words, project planning is where all the important details that are critical to success are determined. Phase 4 – Project Execution Once all the essential conditions have been clarified, it is time to start the IT project. Here, the project manager takes on an essential role and controls the entire process. Priorities must be set, tasks distributed and resources regularly reviewed. Throughout the duration of the project, the project manager should remain flexible in order to be able to react to problems and unforeseen events. Phase 5 – Project Conclusion and Documentation Once the project is completed, the final phase in the process of an IT project occurs. Here the project is closed. The project manager documents the results and terminates all contracts. Documentation and evaluation are particularly important to record experience and knowledge for future projects. Especially freelance project managers pay close attention to the documentation because they are only assigned to a specific project. Thus, one cannot fall back on the memories of the respective project manager but must rely on the documentation.