Spend 1 hourassisting anothermember of QA ona project you arenot assigned toyouLearn a newtool whichbenefits QASpend 1hour on QAresearchunrelated toa projectGo a wholeweek withoutbeing blockedon testingNo QA memberbreaks JIRA byimporting testcases in 2weeksNo developershave to askyou for moredetails on anybug in a weekYou spend 2hours workingin the officewithoutinterruptionSomethingfrom the QAbacklog getsresolvedYou end 5days in a rowwith 0 ‘Actionon Me’issuesHave a QAmeetingwithout beinginterruptedYou writean articleon the QAWikiYou completean IAT runwith no Majoror Criticalbugs foundQA manages toget a logo forJIRA/ConfluenceComplete aproject andsuccessfullymove ontoanotherEverymember ofthe teamrates theweek ≥ 6Default CAFJIRAworkflowgets updatedFinish aproject withup to datetest casesQA comes upwith a processfor dealing witha problematicissue which isfollowed5 projectstandups in arow last lessthan 10minutes5 criticalbugs areraised in aweek (1 aday)Verify asupport andmaintenanceissueYou get100 bugsin a weekNo build onyour project issent withoutrelease notesfor a sprintYou writea blogentry onthe QAWikiSpend 1 hourassisting anothermember of QA ona project you arenot assigned toyouLearn a newtool whichbenefits QASpend 1hour on QAresearchunrelated toa projectGo a wholeweek withoutbeing blockedon testingNo QA memberbreaks JIRA byimporting testcases in 2weeksNo developershave to askyou for moredetails on anybug in a weekYou spend 2hours workingin the officewithoutinterruptionSomethingfrom the QAbacklog getsresolvedYou end 5days in a rowwith 0 ‘Actionon Me’issuesHave a QAmeetingwithout beinginterruptedYou writean articleon the QAWikiYou completean IAT runwith no Majoror Criticalbugs foundQA manages toget a logo forJIRA/ConfluenceComplete aproject andsuccessfullymove ontoanotherEverymember ofthe teamrates theweek ≥ 6Default CAFJIRAworkflowgets updatedFinish aproject withup to datetest casesQA comes upwith a processfor dealing witha problematicissue which isfollowed5 projectstandups in arow last lessthan 10minutes5 criticalbugs areraised in aweek (1 aday)Verify asupport andmaintenanceissueYou get100 bugsin a weekNo build onyour project issent withoutrelease notesfor a sprintYou writea blogentry onthe QAWiki

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