1. Determine the purpose
   1. Fit for purpose
   2. Find out why this report is needed
   3. Who needs a report
      1. think about personalization
2. What actions we expect after reporting
   1. Make a right decision
      1. Team
      2. Business
      3. what bugs will be fixed ?
3. Use recipe for good bug
   1. https://www.xmind.net/m/kwhk
4. Follow Heuristics
   1. MCOASTER
      1. Mission, Coverage, Obstacles, Audience, Status, Techniques, Environment, Risk
5. Context for numbers
   1. Everyone likes numbers
   2. Be careful!
      1. Measure elements that are NOT inconsistent in size or composition
      2. Do not Jump to conclusions
6. Think about emotions
   1. should be the same for all participants
7. sourses
   1. https://www.softwaretestinghelp.com/how-to-write-good-bug-report/
   2. https://www.ministryoftesting.com/dojo/lessons/why-bug-reports-fail-by-neil-studd
   3. https://www.ravnbak.net
8. “The point of writing problem report(bug report) is to get bugs fixed” Cem Kaner