...
Group Leads coordinate and schedule development relevant to their group. They should have developers assigned to work on features in the order necessary to meet ACME's deliverables. Group leads should make sure developers are finishing their work and getting it merged to the ACME "master" branch.
Group Leads, Chief Scientist, and Chief Computational Scientist coordinate the order that major new features (especially from two or more tasks teamsgroups) are added to the model, relevant testing criteria, and when the master should be tagged (using the Branch, Tag, and Version name conventions) all timed to meet ACME deliverables. Integrators should be aware of the overall schedule for their component.
A branch for every feature: Developers should find some unit of work that is Group leads and developers should define units of code development that are big enough to be relevant to others, but simple enough that it can be called one feature (or perhaps a couple of highly-interdependent features) and make a branch for it. The each unit of work. These branches are called "feature branches" in our documentation. The developer should make commits that are minimal atomic units of work to complete the feature that the branch seeks to implement. This separation makes it easier to review and debug later. New development should always start as branch from "master". Try to avoid Avoid creating "large" branches that contain many features and touch dozens of files. If a large branch is needed for some major development, the SE hub should be involved in planning.
...