Supplier’s guide for communication in software projects

Abstract

In the modern age of digitalization an increasing number of companies is stepping into the world of software development. This also means companies of various technical skills levels. To create successful software systems, there needs to be adequate skill but also sufficient trust between the buyer of software development and the supplier. This is why the software development procurement process is very important. New buyers rarely want to take a lot of risk with software projects, which is why a lot of bad practices have stuck in the industry. There should be enough information and trust already in the procurement process, where the first mistakes are made. For this purpose special buyer’s guides have emerged to help new software buyers navigate this unknown ground and learn about software development and what creates value. The intent behind this thesis is to act as a so-called ”supplier’s guide” that teaches software companies how to improve their communication strategies towards a better procurement and development process. The result is an improved communication model consisting of a list of guidelines and directions to their application. This improved model gives advice on where to concentrate communication during the procurement and development process and how to communicate in the best way. Finally, this improved model is validated in the writer’s own professional network and adjustments to the model are presented.