MissingresourcesLearningmoreabout APIUnparalleledeffort of theteam outsidethe shiftCollaborativeDebuggingInconsistentAPIsResponsivenessof the teamStruggle withinterconnecteddependenciesUnforeseenproblemswith regardsto therequirementsDelay indeploymentHard tofinderrorsCompletionof the UserStoriesEffectiveimprovisationsNobugstaggedConfusingrequirementsSmoothShowcasingof the sprintComplexityinprocessingthe APIsMissingresourcesLearningmoreabout APIUnparalleledeffort of theteam outsidethe shiftCollaborativeDebuggingInconsistentAPIsResponsivenessof the teamStruggle withinterconnecteddependenciesUnforeseenproblemswith regardsto therequirementsDelay indeploymentHard tofinderrorsCompletionof the UserStoriesEffectiveimprovisationsNobugstaggedConfusingrequirementsSmoothShowcasingof the sprintComplexityinprocessingthe APIs

Carl - 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
  1. Missing resources
  2. Learning more about API
  3. Unparalleled effort of the team outside the shift
  4. Collaborative Debugging
  5. Inconsistent APIs
  6. Responsiveness of the team
  7. Struggle with interconnected dependencies
  8. Unforeseen problems with regards to the requirements
  9. Delay in deployment
  10. Hard to find errors
  11. Completion of the User Stories
  12. Effective improvisations
  13. No bugs tagged
  14. Confusing requirements
  15. Smooth Showcasing of the sprint
  16. Complexity in processing the APIs