You are currently viewing Daily Status Reports. They’re supposed to be read.

Daily Status Reports. They’re supposed to be read.

  • Post published:January 15, 2014

vteams engineers send status reports to clients every day. There is a good reason for that. The daily report not only tells the clients what progress has been made, but also informs them of other observations, suggestions and forecasts.

The problem with receiving a daily report is that you have to read it daily. Sometimes, that part ignored and appears as unintended consequences. Sometimes a big disaster can be avoided by taking a small step at the right time.

A case in point is a little New Year surprise that hit the engineers on vteam #247 on January 1, 2014.

Engineers on team number 247 had just developed an online reservations portal using VB.NET, ASP.NET, WebForms and MS-SQL 2008. The system was performing normally for many week. But on New Year’s day, the end users complained that they were not able to make reservations. This complaint got to our client and he tried to reach out to us in an emergency.

We got this news and immediately started going through our emergency tracking protocol to find out engineer and get him to the development center. Once the engineer got into the office –at midnight his time– he started scrambling to find a solution.

  • The first place he looked was security of the system. That checked OK.
  • The second place he looked was his last code updates. No problems found.
  • Then he looked at the DLLs and if they were loading ok.

Finally, Imran –the developer– went through all possibilities and remembered that he had made a recent request in a Daily Status Report. He had asked the client that the drive was getting filled up and more space needed to be made available.