Programmer's Daily Report

When dozens of people work on a project, it is difficult to keep track of who does what. If the team is distributed across countries and / or cities, then it becomes even more difficult to get an idea of ​​what people from another city and / or another country are doing.

Targets and goals

1. Timely detect obstacles encountered by engineers in the performance of their tasks.
2. Find dependencies between tasks of different engineers.
3. Determine in time what task the engineer is engaged in - the one that the manager or the lead programmer gave him, or the one that he invented for himself.
4. Objectively evaluate the performance of each employee.

rules

The project manager creates a special “Daily Reports” distribution group and signs all project participants on it. Each engineer at the end of his working day spends 5 minutes of time in order to write a daily report and send it to the distribution group.

Report template

In a daily report, an employee must consistently answer three questions:
')
1. What blocks my work?

When answering this question, the engineer lists the risks, threats, obstacles or dependencies that block his work on the current task.

EXAMPLES:

Task "67 - Navigation System - Main Menu - Update Icons" is blocked due to the lack of new icons
Task "83 - Navigation System - Zip Code Search - Add Zip Code Search Screen" cannot be completed, because Work on the task “82 - Navigation system - Develop a zip code search module” has not yet begun

2. What did I do today?

Answering this question, the engineer lists the tasks that he was engaged in on the current work day. Information about the task should include the task identifier, the name and, if possible, a hyperlink to its description in the task control system. The name will allow the reader of the report (manager or another engineer) to get an idea of ​​what this person was doing. The task identifier and the hyperlink will help you quickly find additional information on the task in the task control system.

EXAMPLES:

119 - Navigation system - Route building - Understand why the Ring Road is not used when building a route from Nepokorenny Avenue to Ladoga Station with time optimization enabled
91 - Navigation system - Address search - Understand why there are several intersections of Nevsky Prospect and Kazan Street.

3. What am I going to do tomorrow?

Answering the third question, the engineer lists the tasks to which he is going to begin the next working day, or indicates that there are no tasks if there are no tasks.

EXAMPLES:

131 - Navigation system - Navigation - When moving along the route, the arrow should not jump to perpendicular streets and change its direction by 90 degrees
107 - Navigation system - Navigation - Understand why when driving along Civil Ave., the arrow sticks not to the main road element, but to the “pocket”