This is an AI translated post.
[SI Developer Story] 07. Weekly Report Story
- Writing language: Korean
- •
-
Base country: All countries
- •
- Information Technology
0000-00-00 00:00:00
Select Language
Summarized by durumis AI
- SI projects report progress to clients through weekly reports, which are used to track project progress and as evidence in case of problems.
- The weekly report includes this week's work content, next week's work content, WBS progress, and special circumstances, and it is important to write it in a way that even non-IT people can understand.
- New developers should familiarize themselves with the weekly report writing guidelines in advance to prepare for the situation where they will have to write the weekly report directly in the future.
SI Developer Story
#7. Weekly Report Story
Basically, the SI project is a task of developing the program that the client wants.
Therefore, the client company conducts weekly reports every week to judge the progress of the work and to monitor whether the
performing company is doing it properly.
The following contents are included in the weekly report.
- Work done this week
- Work to be done next week
- Progress rate on WBS
- Special matters
Roughly, it shows what work was done this week, what work will be done next week, and whether the work is being delayed or proceeding steadily according to the WBS (schedule).
If you meet a good client, you can find a way to adjust even if the schedule is delayed, and resolve it through negotiation, but if you meet a devilish client, you will feel like a cow being dragged to the slaughterhouse during the weekly report.
Therefore, when writing the contents of the weekly report, avoid using development-related terms, write it in an easy-to-understand way for non-IT personnel, and inflate it more than what you actually did. If the client starts a barrage of questions about the work content that they don't understand, you will lose valuable development time.
And these weekly reports accumulated every week are included in the deliverables at the end of the project, and they are evidence that can defend me in case of problems. For example, if there is a situation where the client has agreed to ~~. The client's signature on the agreed contents in the weekly report will be evidence to prove this, so make sure to write down the agreed contents or schedule-related contents accurately and get the client's signature.
Weekly reports are mostly written by the PM, but in my case, I wrote them after a year and reported directly to the client. Fortunately, I met a good client and most of the weekly reports went smoothly, but the pressure I felt when I first started cannot be expressed in words. Therefore, if you understand the wording necessary for the weekly report, the tricks for organizing the work content, etc., from the beginning, you will be able to prepare for the situation where you will have to do the weekly report yourself in the distant future.
