Build Process The process of converting source code files into standalone software artifact(s) that can be run on a computer. Build process, in terms of agile development, refers to the process of converting files into a reliable software product. The build process might include the compilation of files, production of installers, or creation of database schema. The build process is automated, however, is executed under the responsibility of a developer. Traditionally the build process was a manual task executed by developers. As software development techniques evolved to require many builds per day however, the effort required to manually build the software outweighed the value of doing so. Therefore, automation of the build process became paramount. Developers now commonly build software many times per hour during the development cycle. The build process is run locally on developer environments but often coupled with a build server such as Jenkins, TFS, Team City, Bamboo to name just a few. This enables much larger code bases to be built – often when multiple developers are contributing changes to the codebase. With the advent of devops, continuous delivery, and continuous development, the build process has evolved from just looking at building software to more advanced concepts such as release pipelines, infrastructure as code, and platform as a service. In the Solutioneers workshop called Agile Testing Foundations we go into detail on many of these concepts in addition to how they relate to continuous delivery using techniques such as Kanban.