Clarity onscope andbusinessvalue of auser storyInternalPR-reviewdoneproperlyContinuouslearning anddevelopmentFeelingburnedout/stressedGotpositivefeedbacksscopechange/scopecreepIdentifiedchallengesMaintainingqualitystandardsSpoke upin eveningcalls withUS teamToo manymeetingsto attendFollowingbestcodingpracticesIdentify andresolveimpedimentsTechnicalDebtConfidentin thetools andprocessesImplementedlessonslearnedLearnedsomethingnewPre-refinementMisseddeadlinemissed toattend anyof the sprintceremoniesdependencyon US/otherteamsFinishedPBIsearlyAware ofscrumvalues andimplementthemHelpedmy teammateTimemanagementandprioritizationof tasksGreat teamcollaborationClarity onscope andbusinessvalue of auser storyInternalPR-reviewdoneproperlyContinuouslearning anddevelopmentFeelingburnedout/stressedGotpositivefeedbacksscopechange/scopecreepIdentifiedchallengesMaintainingqualitystandardsSpoke upin eveningcalls withUS teamToo manymeetingsto attendFollowingbestcodingpracticesIdentify andresolveimpedimentsTechnicalDebtConfidentin thetools andprocessesImplementedlessonslearnedLearnedsomethingnewPre-refinementMisseddeadlinemissed toattend anyof the sprintceremoniesdependencyon US/otherteamsFinishedPBIsearlyAware ofscrumvalues andimplementthemHelpedmy teammateTimemanagementandprioritizationof tasksGreat teamcollaboration

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