You writean articleon the QAWikiSomethingfrom the QAbacklog getsresolvedQA comes upwith a processfor dealing witha problematicissue which isfollowedNo build onyour project issent withoutrelease notesfor a sprintYou end 5days in a rowwith 0 ‘Actionon Me’issuesYou writea blogentry onthe QAWikiHave a QAmeetingwithout beinginterruptedComplete aproject andsuccessfullymove ontoanotherVerify asupport andmaintenanceissueSpend 1hour on QAresearchunrelated toa project5 criticalbugs areraised in aweek (1 aday)5 projectstandups in arow last lessthan 10minutesFinish aproject withup to datetest casesLearn a newtool whichbenefits QAYou spend 2hours workingin the officewithoutinterruptionYou get100 bugsin a weekGo a wholeweek withoutbeing blockedon testingSpend 1 hourassisting anothermember of QA ona project you arenot assigned toyouDefault CAFJIRAworkflowgets updatedNo QA memberbreaks JIRA byimporting testcases in 2weeksQA manages toget a logo forJIRA/ConfluenceYou completean IAT runwith no Majoror Criticalbugs foundEverymember ofthe teamrates theweek ≥ 6No developershave to askyou for moredetails on anybug in a weekYou writean articleon the QAWikiSomethingfrom the QAbacklog getsresolvedQA comes upwith a processfor dealing witha problematicissue which isfollowedNo build onyour project issent withoutrelease notesfor a sprintYou end 5days in a rowwith 0 ‘Actionon Me’issuesYou writea blogentry onthe QAWikiHave a QAmeetingwithout beinginterruptedComplete aproject andsuccessfullymove ontoanotherVerify asupport andmaintenanceissueSpend 1hour on QAresearchunrelated toa project5 criticalbugs areraised in aweek (1 aday)5 projectstandups in arow last lessthan 10minutesFinish aproject withup to datetest casesLearn a newtool whichbenefits QAYou spend 2hours workingin the officewithoutinterruptionYou get100 bugsin a weekGo a wholeweek withoutbeing blockedon testingSpend 1 hourassisting anothermember of QA ona project you arenot assigned toyouDefault CAFJIRAworkflowgets updatedNo QA memberbreaks JIRA byimporting testcases in 2weeksQA manages toget a logo forJIRA/ConfluenceYou completean IAT runwith no Majoror Criticalbugs foundEverymember ofthe teamrates theweek ≥ 6No developershave to askyou for moredetails on anybug in a week

QA Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. You write an article on the QA Wiki
  2. Something from the QA backlog gets resolved
  3. QA comes up with a process for dealing with a problematic issue which is followed
  4. No build on your project is sent without release notes for a sprint
  5. You end 5 days in a row with 0 ‘Action on Me’ issues
  6. You write a blog entry on the QA Wiki
  7. Have a QA meeting without being interrupted
  8. Complete a project and successfully move onto another
  9. Verify a support and maintenance issue
  10. Spend 1 hour on QA research unrelated to a project
  11. 5 critical bugs are raised in a week (1 a day)
  12. 5 project standups in a row last less than 10 minutes
  13. Finish a project with up to date test cases
  14. Learn a new tool which benefits QA
  15. You spend 2 hours working in the office without interruption
  16. You get 100 bugs in a week
  17. Go a whole week without being blocked on testing
  18. Spend 1 hour assisting another member of QA on a project you are not assigned to you
  19. Default CAF JIRA workflow gets updated
  20. No QA member breaks JIRA by importing test cases in 2 weeks
  21. QA manages to get a logo for JIRA/Confluence
  22. You complete an IAT run with no Major or Critical bugs found
  23. Every member of the team rates the week ≥ 6
  24. No developers have to ask you for more details on any bug in a week