Create adocumentationand share withthe teamMeetteamofflineReport arequirementbug anddiscuss it withthe team toclose it outLead ameeting andend it ontime or lessAsk thetestability ofticketsduring sprintplanningImplement aprocessimprovementComplete aproject withup to datetest casesAutomate10 UI testcasesHelp outa teammemberInvestigateto find rootcause of abugAsk thetestability oftickets duringgroomingsessionRead QAarticles/books/watchvideos and share tothe teamLead atrainingsessionCompletetest casesbefore QAteam testingphase startsLearn a newtool/somethingnew onexisting toolsSend20tacosCompletetest casesbeforedevelopmentstartsLead aprojectReport a designbug anddiscuss it withthe team andhave the mock-up updatedAnalyze testcases for taggingRegression-P1after your projectis completedAutomate10 APItest casesClose a bugthat's been inthe Backlogfor some timenowSuggest aprocessimprovementUpdateexisting testcases whenimpacted bynew changesCreate adocumentationand share withthe teamMeetteamofflineReport arequirementbug anddiscuss it withthe team toclose it outLead ameeting andend it ontime or lessAsk thetestability ofticketsduring sprintplanningImplement aprocessimprovementComplete aproject withup to datetest casesAutomate10 UI testcasesHelp outa teammemberInvestigateto find rootcause of abugAsk thetestability oftickets duringgroomingsessionRead QAarticles/books/watchvideos and share tothe teamLead atrainingsessionCompletetest casesbefore QAteam testingphase startsLearn a newtool/somethingnew onexisting toolsSend20tacosCompletetest casesbeforedevelopmentstartsLead aprojectReport a designbug anddiscuss it withthe team andhave the mock-up updatedAnalyze testcases for taggingRegression-P1after your projectis completedAutomate10 APItest casesClose a bugthat's been inthe Backlogfor some timenowSuggest aprocessimprovementUpdateexisting testcases whenimpacted bynew changes

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