How to Write Status Reports - Nice Article

Posted:
Tue Sep 04, 2007 1:27 pm
by DJ

Posted:
Tue Sep 04, 2007 1:40 pm
by 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.
Nice Article

Posted:
Tue Sep 04, 2007 9:40 pm
by 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.