Investigateto find rootcause of abugLead aprojectRead QAarticles/books/watchvideos and share tothe teamLead ameeting andend it ontime or lessLead atrainingsessionAsk thetestability ofticketsduring sprintplanningUpdateexisting testcases whenimpacted bynew changesCompletetest casesbefore QAteam testingphase startsMeetteamofflineAutomate10 APItest casesReport arequirementbug anddiscuss it withthe team toclose it outAutomate10 UI testcasesCompletetest casesbeforedevelopmentstartsImplement aprocessimprovementHelp outa teammemberLearn a newtool/somethingnew onexisting toolsSuggest aprocessimprovementSend20tacosAnalyze testcases for taggingRegression-P1after your projectis completedClose a bugthat's been inthe Backlogfor some timenowReport a designbug anddiscuss it withthe team andhave the mock-up updatedAsk thetestability oftickets duringgroomingsessionComplete aproject withup to datetest casesCreate adocumentationand share withthe teamInvestigateto find rootcause of abugLead aprojectRead QAarticles/books/watchvideos and share tothe teamLead ameeting andend it ontime or lessLead atrainingsessionAsk thetestability ofticketsduring sprintplanningUpdateexisting testcases whenimpacted bynew changesCompletetest casesbefore QAteam testingphase startsMeetteamofflineAutomate10 APItest casesReport arequirementbug anddiscuss it withthe team toclose it outAutomate10 UI testcasesCompletetest casesbeforedevelopmentstartsImplement aprocessimprovementHelp outa teammemberLearn a newtool/somethingnew onexisting toolsSuggest aprocessimprovementSend20tacosAnalyze testcases for taggingRegression-P1after your projectis completedClose a bugthat's been inthe Backlogfor some timenowReport a designbug anddiscuss it withthe team andhave the mock-up updatedAsk thetestability oftickets duringgroomingsessionComplete aproject withup to datetest casesCreate adocumentationand share withthe team

Ascenda QA - 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. Investigate to find root cause of a bug
  2. Lead a project
  3. Read QA articles/books/watch videos and share to the team
  4. Lead a meeting and end it on time or less
  5. Lead a training session
  6. Ask the testability of tickets during sprint planning
  7. Update existing test cases when impacted by new changes
  8. Complete test cases before QA team testing phase starts
  9. Meet team offline
  10. Automate 10 API test cases
  11. Report a requirement bug and discuss it with the team to close it out
  12. Automate 10 UI test cases
  13. Complete test cases before development starts
  14. Implement a process improvement
  15. Help out a team member
  16. Learn a new tool/ something new on existing tools
  17. Suggest a process improvement
  18. Send 20 tacos
  19. Analyze test cases for tagging Regression-P1 after your project is completed
  20. Close a bug that's been in the Backlog for some time now
  21. Report a design bug and discuss it with the team and have the mock-up updated
  22. Ask the testability of tickets during grooming session
  23. Complete a project with up to date test cases
  24. Create a documentation and share with the team