Changes between Version 13 and Version 14 of PROCESS_R3


Ignore:
Timestamp:
03/19/09 09:25:02 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PROCESS_R3

    v13 v14  
    137137The internal backlog structure may be found and linked in this document instead of bullet listing it. 
    138138 
     139As team splitting is different now, the Teams subpage should contain different information: 
     140{{{ 
     141== Teams == 
     142=== Team splitting === 
     143We define three teams for improved performance and management while developing Sophie 2.  
     144The three teams are as follows: 
     145 * Analysis team - responsible for analysing the tasks for the current and the next iteration and for the testing reviews. 
     146 * Functional team - designing and implementating the tasks from the product backlog. 
     147 * Release Team - responsible for the releases, the reviews of the implementation phase, the testing phase and bug fixing(See [wiki:PROCESS#TaskStates]). 
     148For now the analysis reviews are made internally in the team which is responsible for the corresponding task(i.e. S2S_TESTING_SERVER_R0 analysis review is made by the server team). The design reviews are done by a functional team member(not necessary from the same team).  
     149 
     150The teams are not fixed, it is recommended to change the team members each iteration or for every several iterations. 
     151 
     152== Team Roles == 
     153 
     154For each team there is team leader defined. They are not fixed also and can be changed even during the process depending on their productivity as team leaders. The other developers are called team members. The team leader should: 
     155 * be responsible for the progress of his/her team on the progress checks 
     156 * represents team members on the weekly meetings if they are not present 
     157 * gives direction to the team members if they don't know which task to take 
     158 * helps the team members if they have questions and obscurities or directs them to the person who can help them. 
     159 
     160The team members for each task can be in the role of: 
     161 * reviewers - a person who is assigned to review a task 
     162 * implementors - the workers on a given task 
     163 * freelancers - remote implementors (or reviewers) with different working time 
     164 
     165The Release team has an internal process described in [wiki:ITERATION_03/Release/Process]. [[BR]] 
     166Here is the Analysis team working process: [wiki:ITERATION_03/Analysis/Process]. 
     167}}} 
    139168= Implementation = 
    140169^(Implementation results should be described and linked here (from the wiki or the repository))^