Changes between Version 56 and Version 57 of REPORTS


Ignore:
Timestamp:
10/15/09 23:28:39 (15 years ago)
Author:
lpandeff
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • REPORTS

    v56 v57  
    33 
    44== Overview == 
    5 Since we need a way to track one's activities for every day and for every sprint as a whole, we have defined two kinds of reports. Every report aims to give an tight and important information about people. The two kinds of reports are called '''daily report''' and '''iteration report'''. The daily reports provide information about everyone's everyday work. The iteration reports provide an overall picture of one's work during the iteration and provides some statistics about time, productivity etc.  
     5Since we need a way to track each developer's activities on a daily basis and also for each sprint as a whole, we have defined two kinds of reports. Each of these two types of reports aims to provide tight and important information about the developers and their activities. The two kinds of reports are '''daily report''' and '''iteration report'''. Daily reports provide information about everyone's daily work. Iteration reports provide an overall snapshot of a developer's work during the iteration and provides some statistics about time, productivity, etc.  
    66 
    77== Daily report == 
    88 
    9  * All reports should be put in a file named "<user>-<YYYY-MM-DD>.txt" where <user> is the user id, and the rest is the date of today in the iso format.  
     9 * All reports must be put in a file named "<user>-<YYYY-MM-DD>.txt" where <user> is the user id, and the rest is the date of today in the iso format.  
    1010 * The naming is case sensitive. Example "tanya-2009-09-13.txt" 
    11  * The report should contain several lines, each describing performed activity.  
    12  * Each activity should be described on a single line. 
    13  * You should be following the format strictly, or the report generating scripts will fail. 
    14  * In order to check the consistency of a daily report, one should run the '0check.py' file which is locate in '/manage/reports/'. 
    15   * in order to run this file one should have pytnon installed. 
    16   * on Windows: open Command Prompt and enter "python 0check.py" 
    17   * on Linux: open Terminal and enter "python2.5 0check.py" 
    18   * the python script outputs whether there are mistakes and where they are located. 
    19  
    20 Each line should be formated as: 
     11 * The report must contain several lines, each describing a performed activity.  
     12 * Each activity must be described on a single line. 
     13 * You must follow the format strictly, or the report generating scripts will fail. 
     14 * In order to check the consistency of a daily report, one must run the '0check.py' file which is locate in '/manage/reports/'. 
     15 * In order to run this file one must have Python installed. 
     16 * On Windows: open Command Prompt and enter "python 0check.py" 
     17 * On Linux: open Terminal and enter "python2.5 0check.py" 
     18 * The Python script outputs whether there are mistakes and where they are located. 
     19 
     20Each line must be formated as: 
    2121<activity> <task_id> <status> <time> [comment] 
    2222 
    … …  
    2929 * either a real task ID (according to the WBS or wiki, like PLATFORM_STRUCTURE_R0) 
    3030 * or an UNTRACKED_BLA_BLA defining what you have done.  
    31  ** In this case it should be something that has been nessecary, somehow, but is not a part of a task 
    32  ** Spending time in such things is bad indicator 
     31 ** In this case, it should be something that has been determined to be necessary for whatever reason but is not a part of a given task. 
     32 ** Spending time on such things is a negative indicator. 
    3333 
    3434<status>: 
    3535 * If the activity is work (not review) the current progress is (after the performed work) in percentage. Like "30%", or "100%". Please give realistic estimates. 
    36  * If the activity is review, use 1p, 2p, 3p, 4p, or 5p for the score of the review. 1p or 2p means not acceptable, 3p, 4p or 5p means acceptable. 
     36 * If the activity is review, use 1p, 2p, 3p, 4p, or 5p for the score of the review. 1p or 2p means not acceptable, 3p, 4p, or 5p means acceptable. 
    3737 
    3838<time>: 
    39  * time should always describe the amount taken by the activity 
    40  * you should use a number in minutes or hours 
    41  * suffix the number with the used unit ('m' for minutes, 'h' for hours). You may use floating point. Examples: 
    42   * 20m 
    43   * 0.5h 
    44   * 12h 
     39 * Time should always describe the amount of time required by the activity. 
     40 * You should use a number in minutes or hours. 
     41 * Suffix the number with the used unit ('m' for minutes, 'h' for hours). You may use floating point. For example: 
     42 * 20m 
     43 * 0.5h 
     44 * 12h 
    4545 
    4646<comment>: 
    47  * Put a brief comment in free text. You can write whatever you want till the end of the line. In case of review, it can be only summary of the remarks given in the task log. 
     47 * Put a brief comment in free text. You can write whatever you want till the end of the line. In case of review, it can only be a summary of the remarks provided in the task log. 
    4848 
    4949Other notes: 
    50  * if two members work together, they should both log in their reports the work. 
     50 * If two developers work together, they should both log in their reports on the work. 
    5151 
    5252Example: (tanya-2008-09-22.txt)