Completionof the UserStoriesHard tofinderrorsInconsistentAPIsMissingresourcesCollaborativeDebuggingEffectiveimprovisationsStruggle withinterconnecteddependenciesResponsivenessof the teamComplexityinprocessingthe APIsDelay indeploymentConfusingrequirementsNobugstaggedLearningmoreabout APIUnforeseenproblemswith regardsto therequirementsUnparalleledeffort of theteam outsidethe shiftSmoothShowcasingof the sprintCompletionof the UserStoriesHard tofinderrorsInconsistentAPIsMissingresourcesCollaborativeDebuggingEffectiveimprovisationsStruggle withinterconnecteddependenciesResponsivenessof the teamComplexityinprocessingthe APIsDelay indeploymentConfusingrequirementsNobugstaggedLearningmoreabout APIUnforeseenproblemswith regardsto therequirementsUnparalleledeffort of theteam outsidethe shiftSmoothShowcasingof the sprint

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