EffectiveimprovisationsMissingresourcesDelay indeploymentStruggle withinterconnecteddependenciesInconsistentAPIsNobugstaggedUnparalleledeffort of theteam outsidethe shiftComplexityinprocessingthe APIsConfusingrequirementsSmoothShowcasingof the sprintCompletionof the UserStoriesResponsivenessof the teamUnforeseenproblemswith regardsto therequirementsHard tofinderrorsLearningmoreabout APICollaborativeDebuggingEffectiveimprovisationsMissingresourcesDelay indeploymentStruggle withinterconnecteddependenciesInconsistentAPIsNobugstaggedUnparalleledeffort of theteam outsidethe shiftComplexityinprocessingthe APIsConfusingrequirementsSmoothShowcasingof the sprintCompletionof the UserStoriesResponsivenessof the teamUnforeseenproblemswith regardsto therequirementsHard tofinderrorsLearningmoreabout APICollaborativeDebugging

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