Developers love Git. But as Git adoption grows in the enterprise, the complexity can become overwhelming, and in retrospect, some say more thought should have been given to things like access control.

While centralized version control systems remain popular, Git is gaining traction fast, especially among agile teams. Since more enterprise tool vendors are integrating their IDEs, ALM suites and SCM products with Git, and open-source innovation never stops, it is now easier for teams to integrate Git into their daily workflows.

As always, what suits individual developers doesn’t always suit enterprise teams, at least without some adjustments. But in today’s agile world where speed matters, there is less tolerance for things like broken builds and central repository failures that delay commits and other things that negatively impact team productivity.

(Related: What’s in the latest version of Git)

“Git almost eliminates some of the previous issues [with centralized version control systems], and it encourages collaboration,” said Eric Wittman, general manager of development tools at Atlassian. “Since modern development teams are highly distributed, having a more distributed development model is incredibly important.”

Git’s flexible branching and merging capabilities are attractive because more work can be done in parallel with less risk, whether it’s using local branches to build new features or experimenting with new ideas. Developers love it because it’s fast, as all operations are performed locally.

John Riordan, CTO of business phone service OnSip, said his organization migrated from Subversion (SVN) to Git based on its comparative performance and simplicity.

“Git is a tremendous time-saver from a programmer standpoint,” he said. “And branching and merging are really easy.”