This few days of blog is too unstable, it is really annoying. Try to limit the number of reports you ask other team members to write. Be sure that every report you ask for will provide more value to you or the company than would be lost by interrupting the writer's work. There is a very worth the effort to write And reading reports are the review report of the project, that is, the development team has written in the product. The analysis report is mainly for "what we can learn from the original project?" This kind of theme is discussed, and the topic of this type is discussed, and where we are doing it (just do this), where to do it wrong (how to avoid it next time) . Write a project review report, in addition to the issues that are discovered, it is also recommended to prevent this problem, write detailed steps, so that the next project will progress and do not repeat the same mistakes. It is best not to wait until the project has completed it. It's worth writing (not good for forgetting a big half), you should encounter problems every time, and find that it can be solved, let's write this discovery, why should you wait? Do you have to learn at the end of the project? The accumulation of experience is at any time.
Postmortem reports are invaluable when you do them correctly. Unless your postmortem reports explain exactly how you intend to fix known problems or exploit known improvements, though, the reports probably are not worth doing.Before you call a meeting, be sure the results you think you'll get from that meeting are worth the disruption to the work of the people who would have to attend. Be particularly wary of any regular meeting. Regular, standing meetings often are not worth the time to walk to them, much less attend.If you must hold a meeting, minimize the amount of interruption it will cause. Schedule the meeting so that it will not break up an otherwise large block of time.Whenever you call a meeting, be sure you know ahead of time exactly What You're Trying to Accomplish, And The Make Sure You Do AccompLish It. Remember Also That Conditional Decisions. The views of the conference seem to have already mentioned in the first chapter. This time is just an explanation. More more detailed.
