100 likes | 247 Views
Presenting and Communicating Information. Do not “overload” people with information Pick three or four areas (from your “goals”) and make it a regular, constant list : ( e.g. ) Schedule Status (by Software Dev. Activities) Requirements Completeness Status (by functionalities)
E N D
Presenting and Communicating Information • Do not “overload” people with information • Pick three or four areas (from your “goals”) and make it a regular, constant list : ( e.g. ) • Schedule Status (by Software Dev. Activities) • Requirements Completeness Status (by functionalities) • Quality Status (by testing results by functional areas) • Budget Status (by person hours expended) • Risk Items Status (by open/closed) • Team Morale/Productivity Status (by person or by groups)
Information Portrayal • In what form? • list & table • bar chart and histogram • pie chart • control chart • How often and when to communicate ? • regular once a week, once a month, daily, etc. • irregular and spur of the moment (extraordinary and special cases) • What media should one use ? • phone ? • paper-ppt-presentations? • e-mail ?
Activity Based, Time Related Information in “Table” form Note : 1) Should Target dates and Actual dates be next to each other? 2) Should there be agreed to “codes” for “Current Status” or “Assessment” columns?
Time Related Information in “Bar Chart” Note: 1) provides a quick “global” view 2) should there be some color coding scheme ?
Control and Run Chart Note : gives us a way to be easily “alerted”:high defects, over-expense, low productivity, etc.
Note: Provides a quick summary for “categorization” of information
Bar Chart and Histogram for Comparison Note: May be rearranged by height and convert to a Pareto diagram for easier viewing
Multiple-Attributes using Kiviat Diagram Transaction Performance Rate Defect Rate Customer Acceptance Rate