A build is a compilation of the software system that results in an executable program.

A compiler compiles one piece of code (in a file) from source code to object code.

A build compiles many pieces of code (in many files) from source code to object code, and links them together such that the entire software system can be run.

Most "Help", "About" screens show the build number.

Usually, an IDE (Integrated Development Environment) will have an option to automatically increment the build number every time that the project is compiled.

To keep projects from getting bogged down, Microsoft uses daily builds.

The daily build attempts to minimize the problems of getting a large amount of code working. It was working yesterday, so it should work today. Windows 2000 was a few years late, but build 2195 being sent to manufacturing in December, 1999. Microsoft likes to have at least one build done every working day, for their sync and stabilize software development strategy, so this took a few years.

No one wants their code to "break" the build.

If your part of project causes the build to fail, or not work properly, you usually get to stay late that day.

Briefly explain the Microsoft sync and stabilize approach to software development and how it compares to an iterative and incremental software development process.