I apologize for the lengthy question! The point is that I would like to ask book recommendations for my thesis where it is described how to introduce changes in an existing software development process. For details, please read the lengthy part.
I'm going to write my thesis (MBA) about how my team innovated our software development process by switching from TFVC to git and introducing more fine grained work tracking structure to be able to make more data driven decisions. It is subject of technology management science. What we did is process innovation. The main topic of my thesis is the process how to introduce new procedures, methods in an already existing process. For example: What are the steps you take? What are the parameters of your decision? How POCs can help? Where is the point of no return? Etc.
Due to that the university where I study more manufacturing focused than software development, the literature I got by my teaching material is also rather manufacturing focused. And also expected from the pupil (myself) that he/she should display that by his/her thesis he/she has an understanding about the available literature of the given science. What I have now is An implementation model for reducing resistance to technological change written by Mica R. Endsley and published in 1994. It is an excellent start, but as I said it is rather manufacturing focused and written before dot com crisis.
Despite the fact software development and software delivery took its methods (Could I say that its initial steps?) from manufacturing we don't have those restrictions (let's says, they are lightened in various extend) in software development as manufacturing has. For example, in SD you will have a failed build or dropped MVP having little cost, however the same dead end might cost significantly more in manufacturing. My point is, what is described by Endsley is a good start, but the change process in SD shall not be that rigid as it is described. As a consequence, I have to make a fine distinction between manufacturing processes and software development processes and shed on light that introducing change in software development process has similarities to that described by Endsley's and also it has differences too. In order to support the point above, I need literature from software development area about the suggested way of making changes in an already existing process. Beside that the thesis will have a conclusion where my experiences will be shown. Unfortunately, I can't recall any books about this topic because those I read are about introducing kanban, scrum and technology related stuff. Making changes in processes are driven by common sense in my world, but it is not enough in a thesis.
You might say PDCA cycle should be good. It is not applicable here because switching TFVC to git is rather a big bang thing than an iterative enhancement.
Many thanks for any help!