Struggle withinterconnecteddependenciesNobugstaggedComplexityinprocessingthe APIsCompletionof the UserStoriesUnparalleledeffort of theteam outsidethe shiftInconsistentAPIsUnforeseenproblemswith regardsto therequirementsMissingresourcesLearningmoreabout APIHard tofinderrorsCollaborativeDebuggingEffectiveimprovisationsConfusingrequirementsResponsivenessof the teamSmoothShowcasingof the sprintDelay indeploymentStruggle withinterconnecteddependenciesNobugstaggedComplexityinprocessingthe APIsCompletionof the UserStoriesUnparalleledeffort of theteam outsidethe shiftInconsistentAPIsUnforeseenproblemswith regardsto therequirementsMissingresourcesLearningmoreabout APIHard tofinderrorsCollaborativeDebuggingEffectiveimprovisationsConfusingrequirementsResponsivenessof the teamSmoothShowcasingof the sprintDelay indeployment

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