- Nobel Prize winning work of fiction describing details of where you think you are against plan
- Overly optimistic view of what you will do next week.
Yes, yes, I know I am being facetious, but I see so many weekly reports that seem to follow the above template.
The first thing you need to determine, as with any report, is who is your audience? There can be many types of audience, your boss, your customer, your Project Board. If you know your audience and what they want to see and why they want to see it, then you will know what level of detail to put into your report.
My current project board is comprised of very visual people and they like to see graphs, so I present graphs which show progress against plans, with a minimum of textual explanation and am prepared (hopefully) to explain anything that they require further information on. They also like to see percentages (e.g. 45% of all tests executed, 65% of predicted bugs found in 50% of the allocated time) and then any risks/issues that I see in what the figures mean.
So, there isn't really a clear answer to your question, you need to determine what is required.
Fields are as follows:
Reported for weekending: (Date)
Activities for this week:
Report: (describes the amount of work you performed) Ex: Completed 1000 testcases
Issues (If Any):
Activities for next week: