PetaSoft Knowledge Base


1. General

1.1. Project Manager and Developer are the roles in the project.

1.2. Depends on the project uses one of two reporting systems – Daily Reporting System [2] or Timer Reporting System [3]

1.3. Both of the reporting systems need for (a) controlling the status of the project[s] by Manager, (b) reporting for the clients by Manager, (c) increasing the accuracy of estimates by Developer.

1.4. Developer should estimate each task which he do and compare the estimated time with real time spent for some task to develop the skill of estimating the time which needed for some kinds of tasks.

2. Daily Reporting System

2.1. The general principles of Daily Reporting System are:

2.1.1. Developer should make the report for current day and plan their next work day in last 5 minutes of the current day

2.1.2. Developer should add task which he planned for some [work] hour, made in some [work] hour, write status (done/progress)

2.1.3. Project Manager can see daily reports and should form weekly reports by projects and control the status of the project.

2.2. Developer saves reports in folder which visible for Project Manager and him.

2.3. Developer saves each new week in new Google Spreadsheets sheet.

2.4. The template of report for week located at Google Drive.

2.5. The instance of report for week located at Google Drive.

2.6. Main principles of writing the report:

2.6.1. 1 week in 1 sheet. Sheet name should have the name with first and last date of the week (for instance, "01/02–01/08").

2.6.2. In 1 sheet should be 7 block – 1 for each day.

2.6.3. Each block has header with date (mm/dd/yyyy) and first letter of weekday (M, T, W, T, F, S, S).

2.6.4. Each block has 3 columns – Planned, Made, Status. Planned – what you planned for some hour (when you plan next work day, you fill only this one). Made – what you really did. Status – "process" (or "in process") if task which you made not done and "done" in other case.

2.6.5. If you planned task execution for more than 1 hour, duplicate task name for next for.

2.6.6. Your work hours should have yellow background.

2.6.7. If you made tasks which you planed, you can put "#" in "Made" column.

3. Timer Reporting System

3.1. We use timer by Toggl for this reporting system.

3.2. The general principles of Timer Reporting System are:

3.2.1. Developer should click "Start" button when he start some task and click "Stop" button when he done some task or pause the work.

3.2.2. Developer should write the description for each task, select the project for each time interval and attach the tags list if needed.

3.3. Projects list

3.3.1. For each project Developer should create new project.

3.3.2. Project's name in Toggl consists of ordinal number, project's name and if it needed project's version or type of tasks which Developer do. For instance, "1. Project1", "2. Project2. Design", "3. Project3 v2.3

3.3.4. The default Toggl project should be "Communication", "Research", "Organizing", "Other"

3.4. Tags

3.4.1. Tags are not important for usage.

3.4.2. Tags uses to provide additional information.

3.4.3. Default list of tags: "QA", "backend", "frontend", "research", "meeting", "markup", "fixes", "design", "writing", "refactoring", "communication".

3.5. Toggl have next (but not excluded) features list: export to PDF/CSV (Reports -> Detailed -> Export), start and stop time interval, change description/project/tags/time of time interval, removing the time interval, removing few time intervals, data visualisation, filtering (Reports -> Detailed), creating publish bookmarks .

3.6. Developer should export report to CSV-file for the week at the end of current week or in the beginning of next week and load this file to public folder in Google Drive.