strict adherence to product requirements

faster releases that have minimal features

early customer involvement

increased code quality

It allows for branching and merging so that different tasks are worked on in isolation before they are merged into a feature or master branch.

It provides tooling to automate application builds and infrastructure provisioning.

It allows multiple engineers to work against the same code and configuration files and manage differences and conflicts.

It provides a system to track User Stories and allocate to backlogs.

It allows developers to write effective unit tests.

It supports tracking and comparison of changes in binary format files.

It allows new team members to access the current code and history.

It supports comparisons between revisions of source code files.

It provides wiki collaboration software for documentation.

It allows old versions of packaged applications to be hosted on the Internet.

checkout of code

merge of code

committing code

branching code

facilitates resolving conflicts when merging code

ensures that unit tests are written

prevents over-writing code or configuration files

forces the practice of trunk-based development