Reform of Software Development Process in Metropolia IT
Hakkarainen, Tero (2019)
Hakkarainen, Tero
2019
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2019111321150
https://urn.fi/URN:NBN:fi:amk-2019111321150
Tiivistelmä
This thesis is a report on a reform process that was done into the software development process of Metropolia IT department’s software development team. The development task was done from the year 2016 to 2018.
The Metropolia IT software development team was a small development team and there were problems both with the working methods and the tools used in the development process. The starting point for the development task was a crisis with the personnel of the development team. The target was to develop a practical software development process for the Metropolia IT software development team in a situation where the development team was. A secondary target for the development task was to start using agile development methods as the main software development method and prepare the team to DevOps methods.
The development process was done in small steps and the members of the rebuilt development team were encouraged to give their input to the process. Reforms were done both to the processes and development support tools in the process and the steps taken were evaluated by the team before taking them into use. A big emphasis was addressed to develop communication in the development team and to obtain better software documentation methods both in source code and in technical documentation.
One key finding of the development task was that there exists no single correct universal software development process. The software development team must find what is the best method for them. Another key finding was that the process of re-developing software development methods in the development team is a continuous process. Software development tools and processes should be developed continuously. If the development of the software development team’s working methods is stopped, the organization will collect knowledge debt which is similar to technological debt, when the software system is left unmaintained.
The Metropolia IT software development team was a small development team and there were problems both with the working methods and the tools used in the development process. The starting point for the development task was a crisis with the personnel of the development team. The target was to develop a practical software development process for the Metropolia IT software development team in a situation where the development team was. A secondary target for the development task was to start using agile development methods as the main software development method and prepare the team to DevOps methods.
The development process was done in small steps and the members of the rebuilt development team were encouraged to give their input to the process. Reforms were done both to the processes and development support tools in the process and the steps taken were evaluated by the team before taking them into use. A big emphasis was addressed to develop communication in the development team and to obtain better software documentation methods both in source code and in technical documentation.
One key finding of the development task was that there exists no single correct universal software development process. The software development team must find what is the best method for them. Another key finding was that the process of re-developing software development methods in the development team is a continuous process. Software development tools and processes should be developed continuously. If the development of the software development team’s working methods is stopped, the organization will collect knowledge debt which is similar to technological debt, when the software system is left unmaintained.