PM Reports – Tips & tricks

Copy this template to make your PM Weekly Report – https://cheitgroup.atlassian.net/l/cp/1szAKcP1

Bring the table structure to the same view for everyone – the order of the columns is as follows: Scope/Projects, Status, Deadline, Budge (Estimated, Spent), Additional Requests (Estimated, Spent), Team, Update

Use Statuses – ON TRACK, PAUSED, WITH RISK; If it’s support or internal project just add it to the status like that ON TRACK (support)
Use colors – https://i2.paste.pics/OOE4N.png

Check the fields Status, Budget, ETA – we often copy reports from the previous week, and change the information in the Update column, forgetting about all the others (also new projects)

Sort your projects in a table by the number of hours – Current budget (from the top – the largest, from the bottom those that support, pause, etc.)

Make sure that the formatting of the text helps in the readability of the report (in the Update column, all points are divided by a bullet list, a new line begins with a capital letter, a period or other punctuation at the end of each bullet point is not necessary; all columns are of the required width so that the text is not cut off; if cell is empty put “-“)

If you are replacing someone on a project, add these projects and their statuses to your report + add this person on “CC” to your email

Before sending, read your report again, make sure that the details you have wrote comprehensively describe the current situation on the project, without going into unnecessary details

Pro-tips:

Remember for whom you are sending reports, and what information this person needs, try to read your report through the eyes of this person (for example, do you need information about every bug on the project – NO , do you need information about problems with the budget or responsiveness developer/client – YES )

A report on projects for our management != (not equal to) a report for the client, you should pay more attention to the team (if you notice burnout in someone, weak progress, or on the contrary, you should praise someone), you feel that something is not working as it should be in the processes – mention this information in the report, and of course it is important to notice the nuances of the budget/overtime and always keep your finger on the pulse

If there is a problem, add a note about the steps you plan to take to solve it – show your proactivity

And finally, remember what Alex/Slava most often ask you about in DMs or at meetings, you definitely need to pay attention to this in the report