| 26 | | |
| | 26 | * create a file named statistics.py |
| | 27 | * contains statistics computed from daily reports. |
| | 28 | * should be put in one of the directories m0*, where * = 1...12 , in order to see the results. |
| | 29 | * Contains the following things: |
| | 30 | * Time spent (in hours) working. |
| | 31 | * All the tasks a person has worked on throughout the sprint. These include an, an-re, de, de-re etc... This section is a union of the following subsections: |
| | 32 | * Implemented tasks - the tasks that are '''NOT re''' |
| | 33 | * Reviewed tasks - the tasks that are '''re''' |
| | 34 | * Note: 'an-re SCS_INFORMATION_R0' goes in reviewed tasks while 'im SCS_INFORMATION_R0' goes in implemented tasks. |
| | 35 | * Reviews and implementations - this is the intersection of the prior sections. This indicates whether a person has spent time on doing both reviews and implementations of a phases of a task. |
| | 36 | * Untracked things - these include tasks that do not have corresponding issues in the issue tracker. |
| | 37 | * Comments - this sections includes things that have to be improved. For the time being we have: |
| | 38 | * Untracked activities - we should avoid doing things that are untracked. In general this means we are not going towards the goal. DO NOT PAY ATTENTION TO THINGS LIKE UNTRACKED_SPRINT_OPEN since this is a plausible untracked activity. |
| | 39 | * Things that are done over and over again like an2, de2, im2. This means that a task is not done accurately of the fly. Phases like an-re2 that have '''re''' part are not included since the person reviewing is not guilty for not passing things that are not done correctly. |
