Overview

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.

Daily report

• 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.
• The naming is case sensitive. Example "tanya-2009-09-13.txt"
• The report should contain several lines, each describing performed activity.
• Each activity should be described on a single line.
• You should be following the format strictly, or the report generating scripts will fail.

Each line should be formated as: <activity> <task_id> <status> <time> [comment]

<activity>:

• one of an, de, im, te, an-re, de-re, im-re, te-re, an2, de2, im2, te2, an-re2, de-re2, im-re2, te-re2, an3..
• which means analisys, design, implementation, test, analisys-review, etc.
• if a review fails, the index of the activity should increas (if "an-re" indicates that "an" fails, then the next is "an2" (which is reviewed in "an-re2", and so on)

<task_id>:

• either a real task ID (according to the WBS or wiki, like PLATFORM_STRUCTURE_R0)
• or an UNTRACKED_BLA_BLA defining what you have done. In this case it should be something that has been nessecary, somehow, but is not a part of a task Spending time in such things is bad indicator

<status>:

• 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.
• 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.

<time>:

• time should always describe the amount taken by the activity
• you should use a number in minutes or hours
• suffix the number with the used unit ('m' for minutes, 'h' for hours). You may use floating point. Examples:
  • 20m
  • 0.5h
  • 12h

<comment>:

• 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.

Other notes:

• if two members work together, they should both log in their reports the work.

Example: (tanya-2008-09-22.txt)

an-re PLATFORM_STRUCTURE_R0	2p 15m 		 Unclear and a bit wrong (self conflicting).
an-re PLUGIN_SUPPORT_LIB_BASE_R0 2p 5m 		 Not on the template, not clear enough.
an2 CORE_MVC_BASE_R0 100% 40m			 Refactored.
an2 BASE_MODEL_FRAME_CONTENT_R0 100% 40m	 Refactored.
de BASE_MODEL_FRAME_CONTENT_R0 100% 70m		 Should be ready.
an-re PLATFORM_STANDARDS_REPOSITORY_R0 2p 15m	 Some parts of the analysis are missing.
an-re PRO_LIB_CORE_TUTORIAL_R0 2p 5m		 Does not apply to the template.
an-re BASE_BOUND_CONTROLS_R0 2p 10m 	         This analysis is for the whole task.
an-re BOOK_WINDOW_R0 1p 0.25h			 Does not apply to the template, other problems also.

Iteration report

• The name of the file where it is stored should follow the format: <name>-<milestone_id>-final.txt where:
  • <name> is the name of the person whose report is written in the file.
  • <milestone_id> is the id of the milestone for example: m01, m02 ... m11, m12
  • final points out that this is the final report for current iteration.
• It should be written after the sprint is over and prior the next has started.
• Example:

  tanya-m01-final.txt
  

• The first part of the report is for statistics and things are arranged in the following order:
  • work-time - total time spent working in hours.
  • reported-time - total time according to reports in hours.
  • reported-factor - reported-time/work-time (in percents).
  • tracked-work - the total reported time spent on tracked tasks followed by the list of tasks that the person has worked on.
  • untracked-work - the total reported time spent on untracked tasks followed by the list of tasks that the person has worked on.
  • There are four formulae that when summed represent the score one accumulates over the sprint:
    • Let 'P' be a task. It provides some attributes used in the formulae to obtain the score. The common things for the formulae are:
      • P-effort - represents the effort of every task.
      • P-part - is the part of the task
    • analysis-score:
      • represents the score one accumulates for done analysis.
      • is calculated by the formula: