| 12 | | |
| 13 | | = Rules = |
| | 13 | == SCRUM == |
| | 14 | |
| | 15 | We are continuing to use SCRUM (info at [http://en.wikipedia.org/wiki/SCRUM]). What is new: |
| | 16 | |
| | 17 | * Becoming much more strict (and unfortunately increasing the process overhead). |
| | 18 | * Trying to have much higher quality. |
| | 19 | * The sprint backlogs will be on the wiki page ([wiki:ITERATION_01] for example). |
| | 20 | * The four states of a story/task are analyzing, designing, implementing, and testing. |
| | 21 | * Each passage between states requires a review. |
| | 22 | |
| | 23 | We create the internal backlog which should track: |
| | 24 | |
| | 25 | * Impediments backlog |
| | 26 | * Documentation backlog |
| | 27 | * Smells |
| | 28 | * Open Questions |
| | 29 | |
| | 30 | Here is the document: [http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en Backlog] |
| | 31 | |
| | 32 | == Teams == |
| | 33 | We define six teams for improved performance and management while developing sophie 2. The team diagram showing the splitting of the developers to teams is located here: http://sophie2.org/trac/browser/manage/sched/teams.odg [[BR]] |
| | 34 | The six teams are as follows: |
| | 35 | * Analysis team - responsible for analysing the tasks for the current and the next iteration. |
| | 36 | * Base team - responsible for the Platform, Core and Base categories. |
| | 37 | * Main team - responsible for Main and End Product categories. |
| | 38 | * Server Team - responsible for Supporting, SCS and S2S categories. |
| | 39 | * Release Team - responsible for the releases and the reviews of the implementation phases(See [wiki:PROCESS#Workflow]). |
| | 40 | Note: The categories are described in the work breakdown structure: [source:/manage/sched/sophie2_wbs.py] |
| | 41 | == Rules == |
| 77 | | = SCRUM = |
| 78 | | |
| 79 | | We are continuing to use SCRUM (info at [http://en.wikipedia.org/wiki/SCRUM]). What is new: |
| 80 | | |
| 81 | | * We are becoming much more strict (and unfortunately increasing the process overhead). |
| 82 | | * Trying to have much higher quality. |
| 83 | | * We expect that the lost of speed will be compensated by removing the loss of momentum that we have suffered from. |
| 84 | | * The sprint backlogs will be on the wiki page ([wiki:ITERATION_01]). |
| 85 | | * The four states of a story/task are analyzing, designing, implementing, and testing. |
| 86 | | * Each passage between states requires a review. |
| 87 | | |
| 88 | | We create the internal backlog which should track: |
| 89 | | |
| 90 | | * Impediments backlog |
| 91 | | * Documentation backlog |
| 92 | | * Smells |
| 93 | | * Open Questions |
| 94 | | |
| 95 | | Here is the document: [http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en Backlog] |
| 96 | | |
| 97 | | = Task States = |
| | 105 | |
| | 106 | |
| | 107 | == Task States == |
