1 / 9

Presenting and Communicating Information

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)

Download Presentation

Presenting and Communicating Information

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 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)

  2. 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 ?

  3. 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?

  4. Time Related Information in “Bar Chart” Note: 1) provides a quick “global” view 2) should there be some color coding scheme ?

  5. Control and Run Chart Note : gives us a way to be easily “alerted”:high defects, over-expense, low productivity, etc.

  6. Note: Provides a quick summary for “categorization” of information

  7. Bar Chart and Histogram for Comparison Note: May be rearranged by height and convert to a Pareto diagram for easier viewing

  8. Multiple-Attributes using Kiviat Diagram Transaction Performance Rate Defect Rate Customer Acceptance Rate

  9. Tree Map Representation: Software Sub-Components

More Related