Needing HelpFrom DevsFrom OtherTeams, ButThey Are BusySpicyArgumentsBetweenLeadersLate-NightDeploymentsRTE Says"GoodFeedback"NotEnoughTime ForTestingOld RetroFeedbackNot BeingAddressRTE Says"Take ThisOffine"PretendingLike We'reAll Here InDecemberNot BeingAble to TellBusiness"No!"SomeoneAccidentallyTurns TheirCamera OnEnvironmentIssuesSomeone says"Your FeedbackIs Valuable"Once The RetroIs CancelledOverloadingIterationsAllen notpayingattentionDemo takingup morethan half ofthe meetingSomeone'sCode BreaksDuring theDemoNotenoughtime forRetroTeamCollaborationWas GreatAcceptanceCriteriaUnclearFirat or Allenscreenshotssomethingfor a meme3 WeekIterationsSuggestedSomeoneSays "CanYou See MyScreen?"Last-MinuteBusinessRequestsSomeoneSays "We'reLearning andGrowing!"Needing HelpFrom DevsFrom OtherTeams, ButThey Are BusySpicyArgumentsBetweenLeadersLate-NightDeploymentsRTE Says"GoodFeedback"NotEnoughTime ForTestingOld RetroFeedbackNot BeingAddressRTE Says"Take ThisOffine"PretendingLike We'reAll Here InDecemberNot BeingAble to TellBusiness"No!"SomeoneAccidentallyTurns TheirCamera OnEnvironmentIssuesSomeone says"Your FeedbackIs Valuable"Once The RetroIs CancelledOverloadingIterationsAllen notpayingattentionDemo takingup morethan half ofthe meetingSomeone'sCode BreaksDuring theDemoNotenoughtime forRetroTeamCollaborationWas GreatAcceptanceCriteriaUnclearFirat or Allenscreenshotssomethingfor a meme3 WeekIterationsSuggestedSomeoneSays "CanYou See MyScreen?"Last-MinuteBusinessRequestsSomeoneSays "We'reLearning andGrowing!"

PI4 I&A Bingo! - 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
17
18
19
20
21
22
23
24
  1. Needing Help From Devs From Other Teams, But They Are Busy
  2. Spicy Arguments Between Leaders
  3. Late-Night Deployments
  4. RTE Says "Good Feedback"
  5. Not Enough Time For Testing
  6. Old Retro Feedback Not Being Address
  7. RTE Says "Take This Offine"
  8. Pretending Like We're All Here In December
  9. Not Being Able to Tell Business "No!"
  10. Someone Accidentally Turns Their Camera On
  11. Environment Issues
  12. Someone says "Your Feedback Is Valuable" Once The Retro Is Cancelled
  13. Overloading Iterations
  14. Allen not paying attention
  15. Demo taking up more than half of the meeting
  16. Someone's Code Breaks During the Demo
  17. Not enough time for Retro
  18. Team Collaboration Was Great
  19. Acceptance Criteria Unclear
  20. Firat or Allen screenshots something for a meme
  21. 3 Week Iterations Suggested
  22. Someone Says "Can You See My Screen?"
  23. Last-Minute Business Requests
  24. Someone Says "We're Learning and Growing!"