EffectiveimprovisationsResponsivenessof the teamComplexityinprocessingthe APIsCollaborativeDebuggingUnforeseenproblemswith regardsto therequirementsHard tofinderrorsUnparalleledeffort of theteam outsidethe shiftMissingresourcesCompletionof the UserStoriesInconsistentAPIsLearningmoreabout APIDelay indeploymentConfusingrequirementsStruggle withinterconnecteddependenciesSmoothShowcasingof the sprintNobugstaggedEffectiveimprovisationsResponsivenessof the teamComplexityinprocessingthe APIsCollaborativeDebuggingUnforeseenproblemswith regardsto therequirementsHard tofinderrorsUnparalleledeffort of theteam outsidethe shiftMissingresourcesCompletionof the UserStoriesInconsistentAPIsLearningmoreabout APIDelay indeploymentConfusingrequirementsStruggle withinterconnecteddependenciesSmoothShowcasingof the sprintNobugstagged

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