FinishedPBIsearlyClarity onscope andbusinessvalue of auser storyLearnedsomethingnewImplementedlessonslearnedscopechange/scopecreepAware ofscrumvalues andimplementthemIdentifiedchallengesmissed toattend anyof the sprintceremoniesGreat teamcollaborationGotpositivefeedbacksFollowingbestcodingpracticesTimemanagementandprioritizationof tasksMisseddeadlineContinuouslearning anddevelopmentHelpedmy teammateInternalPR-reviewdoneproperlyFeelingburnedout/stressedMaintainingqualitystandardsConfidentin thetools andprocessesPre-refinementToo manymeetingsto attendSpoke upin eveningcalls withUS teamdependencyon US/otherteamsIdentify andresolveimpedimentsTechnicalDebtFinishedPBIsearlyClarity onscope andbusinessvalue of auser storyLearnedsomethingnewImplementedlessonslearnedscopechange/scopecreepAware ofscrumvalues andimplementthemIdentifiedchallengesmissed toattend anyof the sprintceremoniesGreat teamcollaborationGotpositivefeedbacksFollowingbestcodingpracticesTimemanagementandprioritizationof tasksMisseddeadlineContinuouslearning anddevelopmentHelpedmy teammateInternalPR-reviewdoneproperlyFeelingburnedout/stressedMaintainingqualitystandardsConfidentin thetools andprocessesPre-refinementToo manymeetingsto attendSpoke upin eveningcalls withUS teamdependencyon US/otherteamsIdentify andresolveimpedimentsTechnicalDebt

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