1. Taken from Michael Bolton's Rapid Software Testing notes
2. reporting considerations
   1. reporter safety
      1. what will they think if I made no progress?
   2. client
      1. who am I reporting to and how do I relate to them?
   3. rules
      1. what rules and traditions are there for reporting here?
   4. significance of the report
      1. how will my report influence events?
   5. subject of the report
      1. how do other reports affect mine?
   6. other agents of reporting
      1. how do other reports affect mine?
   7. medium
      1. how will my report be seen, heard, and touched?
   8. precision and confidence levels
      1. what distinctions make a difference?
3. Reporting structure examples
   1. 3 level test story
      1. status of the product
         1. what it does
         2. how it failed
         3. how it might fail
         4. in what ways will it matter to your clients
      2. testing
         1. how you operated and observed it
         2. how you recognized the problems
         3. what you have and have not tested yet
         4. what you won't test at all (unless the clients object)
      3. value
         1. the risks and costs of testing or not testing
         2. what made testing harder or slower
         3. how testable (or not) the product is
         4. what you need and what you recommend
   2. Rapid testing style
      1. General
         1. Testing heuristics
         2. Risk Catalog
      2. Project specific
         1. Product coverage outline
         2. Risk list
         3. Test strategy reference
         4. schedule
         5. issues
         6. bugs
         7. status dashboard
      3. rapid report example
   3. Mike Kelly's MCOASTER
      1. mission
      2. coverage
      3. obstacles
      4. audience
      5. status
      6. techniques
      7. environment
      8. risk
   4. Test results reporting
      1. Observation
      2. Risk
      3. Implication
   5. scenario testing
      1. Mission
      2. Testers
      3. Setup
      4. Activities
      5. Oracle notes
      6. Test results
   6. Exploratory charters
      1. SBTM method for exploratory charters
         1. Past
            1. what happened during the session?
         2. Results
            1. What was achieved?
         3. Obstacles
            1. What got in the way or slowed things down?
         4. Outlook
            1. What's next? What remains to be done?
         5. Feelings
            1. How does the tester feel about all this?
      2. Informal charter format
         1. Strategy ideas
            1. prelude to exploratory testing
            2. motivation for tests
            3. perceived risks for DecideRight
         2. Issues
            1. Problems encountered that hampered testing
            2. Bugs encountered, raised or yet to raise
         3. Platform
            1. Platforms used for testing the product
         4. Process
            1. Test areas/functions of the product explored
            2. e.g. Functional analysis, Functional exploration
            3. References to test data
         5. Other interesting elements
4. Reporting styles
   1. dashboards for status of a project
   2. Coverage matrices
      1. quality criteria coverage matrix example
      2. product element coverage matrix
   3. Bug taxonomies
   4. Annotated diagrams
   5. Risk & Strategy based reporting
      1. Create a table with 2 columns - risk, strategy
      2. Describe the risk in the first column and propose the strategy in the second column
      3. example