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