Completionof the UserStoriesLearningmoreabout APIConfusingrequirementsCollaborativeDebuggingEffectiveimprovisationsSmoothShowcasingof the sprintMissingresourcesComplexityinprocessingthe APIsHard tofinderrorsNobugstaggedUnparalleledeffort of theteam outsidethe shiftInconsistentAPIsUnforeseenproblemswith regardsto therequirementsDelay indeploymentResponsivenessof the teamStruggle withinterconnecteddependenciesCompletionof the UserStoriesLearningmoreabout APIConfusingrequirementsCollaborativeDebuggingEffectiveimprovisationsSmoothShowcasingof the sprintMissingresourcesComplexityinprocessingthe APIsHard tofinderrorsNobugstaggedUnparalleledeffort of theteam outsidethe shiftInconsistentAPIsUnforeseenproblemswith regardsto therequirementsDelay indeploymentResponsivenessof the teamStruggle withinterconnecteddependencies

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