GIT has been developed by Linus Torvalds because of conflicts with the open nature of Linux with the requirements of the source repository. On Linux, it is very well supported and has been a huge hit since.
At this moment, the windows support is a bit limited and not up to level of the Linux support. Given the fact that one should use a linux server to host the repository, using GIT on windows is still a valid option. There are plenty of good clients available on windows and the situation is improving constantly.
Git has a major advantage to its main contender SVN: it supports all kinds of development models, works well with remote teams and allows easy forking. I have not enough experience in forking and re-publishing with Git to give in-depth insight in the advanced features, but feel free to read the articles linked from this site.
Because of the different models GIT supports, one will have to make a decision on what model to impose inside his company, and limit to this. GIT focuses on placing the power in the hands of the individual developer, without jeopardizing the ability to obtain absolute stability. A huge organization may want to limit the power of its employees. GIT should not be an objection except if the organization lacks the senior developers that act as an integrator.
If you are working with GIT, following sites could be of interest.
The git reference: http://gitref.org/.
The git user-manual: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html.
Search this site by typing git in the search box.