In performance reporting, we often need to find a balance between too much information and too little detail. Some of us may love looking at the numbers and understanding them, while others just want to get to the bottom line. This is often complicated by the fact that we have both types of persons reading performance reports on many of our projects. How should we be thinking about and drafting our performance reports to balance the amount of detail (both in terms of calculations and in terms of project technical specifics) given to try to meet the differing needs and desires? How does earned value add value in performance reporting? Also, are there other parts of a project plan (think about the knowledge areas) that might help inform our report writing strategy?
At least 2 references
The response repetition rate should not exceed 10%