Geek Answers Handbook

Source control when starting a new project

when you start with a project and use a control source, it’s hard for me to separate things that people are working on, so they don’t write duplicate code or think that it should be called one, etc. this problem decreases over time because the common foundation is in place and it is easier to separate tasks so that they do not overlap so much

How do you manage work with source control in the initial phase?

EDIT: I see that this has nothing to do with version control, but it becomes more apparent when you have source control. therefore, the question becomes more like “how do you manage to separate the tasks so that they do not overlap too much. I think it’s really difficult, and I didn’t see much how to do it.

+5
source share
3 answers

Well, as for version control, someone should take the lead and set up the basic structure of the project, directories, etc. and report this to the team. In projects that I work on, this is usually an architect or senior developer, someone who knows the best practices for organizing a project for a team / company.

, , , ; - , , . / , , , .

, , , 2-6 ; scrum - , Crystal Clear:

  • ()/ .
  • Architect (s)/designer (s) /, " ", .
  • 1-3 / ( )
  • , .
  • /

/ -, , .

+2

, ( , "", - - , , " " , , , ). (, , , Pivotal Tracker - , ! -), . , , Tracker , , stand-ups, .

+1

, , , , , , . .

0

More articles:


All Articles