Learnedsomethingnewdependencyon US/otherteamsTimemanagementandprioritizationof tasksMaintainingqualitystandardsConfidentin thetools andprocessesInternalPR-reviewdoneproperlyIdentify andresolveimpedimentsGreat teamcollaborationscopechange/scopecreepClarity onscope andbusinessvalue of auser storyFollowingbestcodingpracticesFinishedPBIsearlySpoke upin eveningcalls withUS teamIdentifiedchallengesContinuouslearning anddevelopmentToo manymeetingsto attendAware ofscrumvalues andimplementthemMisseddeadlineFeelingburnedout/stressedmissed toattend anyof the sprintceremoniesPre-refinementGotpositivefeedbacksTechnicalDebtImplementedlessonslearnedHelpedmy teammateLearnedsomethingnewdependencyon US/otherteamsTimemanagementandprioritizationof tasksMaintainingqualitystandardsConfidentin thetools andprocessesInternalPR-reviewdoneproperlyIdentify andresolveimpedimentsGreat teamcollaborationscopechange/scopecreepClarity onscope andbusinessvalue of auser storyFollowingbestcodingpracticesFinishedPBIsearlySpoke upin eveningcalls withUS teamIdentifiedchallengesContinuouslearning anddevelopmentToo manymeetingsto attendAware ofscrumvalues andimplementthemMisseddeadlineFeelingburnedout/stressedmissed toattend anyof the sprintceremoniesPre-refinementGotpositivefeedbacksTechnicalDebtImplementedlessonslearnedHelpedmy teammate

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