Clarity onscope andbusinessvalue of auser storyGotpositivefeedbacksFeelingburnedout/stressedTechnicalDebtLearnedsomethingnewToo manymeetingsto attenddependencyon US/otherteamsPre-refinementIdentify andresolveimpedimentsFollowingbestcodingpracticesMisseddeadlineAware ofscrumvalues andimplementthemGreat teamcollaborationscopechange/scopecreepImplementedlessonslearnedIdentifiedchallengesHelpedmy teammatemissed toattend anyof the sprintceremoniesConfidentin thetools andprocessesMaintainingqualitystandardsInternalPR-reviewdoneproperlySpoke upin eveningcalls withUS teamContinuouslearning anddevelopmentTimemanagementandprioritizationof tasksFinishedPBIsearlyClarity onscope andbusinessvalue of auser storyGotpositivefeedbacksFeelingburnedout/stressedTechnicalDebtLearnedsomethingnewToo manymeetingsto attenddependencyon US/otherteamsPre-refinementIdentify andresolveimpedimentsFollowingbestcodingpracticesMisseddeadlineAware ofscrumvalues andimplementthemGreat teamcollaborationscopechange/scopecreepImplementedlessonslearnedIdentifiedchallengesHelpedmy teammatemissed toattend anyof the sprintceremoniesConfidentin thetools andprocessesMaintainingqualitystandardsInternalPR-reviewdoneproperlySpoke upin eveningcalls withUS teamContinuouslearning anddevelopmentTimemanagementandprioritizationof tasksFinishedPBIsearly

Sales GCC 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
25
  1. Clarity on scope and business value of a user story
  2. Got positive feedbacks
  3. Feeling burned out/stressed
  4. Technical Debt
  5. Learned something new
  6. Too many meetings to attend
  7. dependency on US/other teams
  8. Pre-refinement
  9. Identify and resolve impediments
  10. Following best coding practices
  11. Missed deadline
  12. Aware of scrum values and implement them
  13. Great team collaboration
  14. scope change/scope creep
  15. Implemented lessons learned
  16. Identified challenges
  17. Helped my team mate
  18. missed to attend any of the sprint ceremonies
  19. Confident in the tools and processes
  20. Maintaining quality standards
  21. Internal PR-review done properly
  22. Spoke up in evening calls with US team
  23. Continuous learning and development
  24. Time management and prioritization of tasks
  25. Finished PBIs early