How to Write Status Reports - Nice Article

[DJ]

I really liked this article which explains how to build an effective status report. Have a look at it!

http://www.itbusiness.ca/it/client/en/h ... p?id=44925

http://www.itbusiness.ca/it/client/en/h ... &PageMem=3

[Dave]

Here are the five questions they talk about in the first article:

1. Has the scope of any project task changed?(Yes/No)
2. Will any major activity or milestone date be missed? (Yes/No)
3. Does the project team need any outside skills/expertise? (Yes/No)
4. Are there any unsolved technical problems? (Yes/No)
5. Are there any unresolved user review/approval problems? (Yes/No)

(For all questions marked Yes, explain the problem and recommend possible solutions.)


I think it makes a lot of sense to answer these 5 questions when creating status updates for clients.

[Anil]

Nice one to read. As Dave said he has simplified things. I think all the important imformation for the management team should come in the first section of a status reports. All problems, concerns etc. should be highligted so that it is not missed by the reader.