All geek questions in one place

Teamwork methodology

I need a methodology to organize my team for a university assignment.

I am a university student and already have some programming experience. My experience working in teams of more than 2 people on a relatively large project is that everything is usually done very quickly and poorly last week or so due to problems of planning, organization and communication. In January, I will need to make a (rather difficult for my skill) programming project (Java application for Oracle) in a team of 6. I already know the members of my team and was elected project manager. It will not be realistic to expect that people will gather for some significant amount of time - everyone is free at different times and probably nothing more than weekly one-hour meetings are realistic. People are hardworking and devoted to success, but each has its own circumstances. Most likely, this is a distributed work.

I looked at XP, Scrum, but they should all sit together (unlikely), aimed at the full development of the project (people have other tasks and work on a part-time basis) and customer participation (we will have written specifications and, as far as experience is concerned) , emails from the teacher will be answered at best in 2-3 days).

Any suggestions on how to organize people and share work? I am seriously studying this topic, because in the future it will be much more.

Any help was appreciated.

+3
source share
4 answers

(6 ). , .

, -, , SVN .. - ( ), . // , , . , , , , , . , "" , , , . , , , ... .

, . , ( ) . TODO , , . , (, MoSCoW), , , / .. , , ( ). , , " ", , . , , ... , "" (.. " , , , blablabla" )... , .

+4

, - 5 . , , . , , , ( " ", , ):

  • . , , : , , , . , , " ". uni , , , , . , , " ". , " ".
  • , . , , . , , , .
  • . , , , ( 90 ). , . , , , . , , , . ...
  • , - . ( ), , , .
  • . , , , . , , , - , , - , . , . , , , , .

, :

  • - - "" // ; , , . - . , , , . , .
  • sgolodetz, . , , , / , / .
  • , , , , , , . , , , "" .

, . , .

, , , - , , . , , (.. , , ..) "" - . , , .

+5

:

  • - , IRC wiki
  • - , , .
  • - , , , ; , (, ) - , .
  • - , (, ), , , .
+3

. , , , , , - -, , .

. , , . , , .

, , - . . , .

Plan what should be done in what order. Make sure that the people who develop the things on which everything else depends are the most reliable developers on your team and that they will meet their early dates or that no one will be able to fulfill their roles.

Week of weekly progress and don't be afraid to call someone because he is not fulfilling his role. The sooner you identify a person without pulling his weight, the sooner you can solve the problem.

+1
source

Source: https://habr.com/ru/post/1776079/

More articles:


All Articles