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