Aware ofscrumvalues andimplementthemLearnedsomethingnewInternalPR-reviewdoneproperlySpoke upin eveningcalls withUS teammissed toattend anyof the sprintceremoniesGotpositivefeedbacksImplementedlessonslearnedPre-refinementFeelingburnedout/stressedMisseddeadlineFinishedPBIsearlyIdentifiedchallengesClarity onscope andbusinessvalue of auser storyTimemanagementandprioritizationof tasksscopechange/scopecreepConfidentin thetools andprocessesdependencyon US/otherteamsGreat teamcollaborationIdentify andresolveimpedimentsHelpedmy teammateTechnicalDebtContinuouslearning anddevelopmentMaintainingqualitystandardsFollowingbestcodingpracticesToo manymeetingsto attendAware ofscrumvalues andimplementthemLearnedsomethingnewInternalPR-reviewdoneproperlySpoke upin eveningcalls withUS teammissed toattend anyof the sprintceremoniesGotpositivefeedbacksImplementedlessonslearnedPre-refinementFeelingburnedout/stressedMisseddeadlineFinishedPBIsearlyIdentifiedchallengesClarity onscope andbusinessvalue of auser storyTimemanagementandprioritizationof tasksscopechange/scopecreepConfidentin thetools andprocessesdependencyon US/otherteamsGreat teamcollaborationIdentify andresolveimpedimentsHelpedmy teammateTechnicalDebtContinuouslearning anddevelopmentMaintainingqualitystandardsFollowingbestcodingpracticesToo manymeetingsto attend

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