Pre-implementation phase for projects managed using the Scrum methodology

The aim of this thesis is to find out how agile projects are managed before the implementation phase and what leads managers to do so. The thesis focuses on the individual pre-implementation processes of IT projects managed primarily using the agile Scrum methodology in the Czech Republic with a narrower focus on supplier-customer relationships. The work uses qualitative research, specifically a multiple case study design with data collection through semi-structured interviews, of which 8 were conducted. The data was processed using reflective thematic analysis. The output consists of thematic tables and accompanying reports containing respondent statements, commentary and recommendations. The results point to an ambiguous definition of the beginning, completion and content of the pre-implementation phase processes in Scrum-managed projects. In doing so, the boundary of the transition between phases is not perceived as sharp. Furthermore, it was found that during this phase processes from both the agile and predictive approaches are applied for reasons that are on the side of the beneficiary, the supplier and the relationship between them. In particular, if the beneficiary is a large enterprise, there is a tendency to proceed predictively, but the outputs of the processes (e.g. schedule, scope) end up being more conceptual, less detailed and anticipating changes, which is consistent with the agile approach. The final shape of the phase, i.e. whether predictive or agile processes are more represented, is also influenced by the trust between the parties, the willingness and level of readiness to follow the Scrum methodology, the pricing model, whether a new product or component is being developed into the beneficiary's existing system, and the fit of the project into the beneficiary's overall corporate management system.