EnvironmentIssues3 WeekIterationsSuggestedDemo takingup morethan half ofthe meetingNeeding HelpFrom DevsFrom OtherTeams, ButThey Are BusyPretendingLike We'reAll Here InDecemberRTE Says"GoodFeedback"Old RetroFeedbackNot BeingAddressOverloadingIterationsNot BeingAble to TellBusiness"No!"SomeoneSays "We'reLearning andGrowing!"NotEnoughTime ForTestingAllen notpayingattentionTeamCollaborationWas GreatSpicyArgumentsBetweenLeadersNotenoughtime forRetroLate-NightDeploymentsSomeone'sCode BreaksDuring theDemoLast-MinuteBusinessRequestsAcceptanceCriteriaUnclearRTE Says"Take ThisOffine"SomeoneSays "CanYou See MyScreen?"Someone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneAccidentallyTurns TheirCamera OnFirat or Allenscreenshotssomethingfor a memeEnvironmentIssues3 WeekIterationsSuggestedDemo takingup morethan half ofthe meetingNeeding HelpFrom DevsFrom OtherTeams, ButThey Are BusyPretendingLike We'reAll Here InDecemberRTE Says"GoodFeedback"Old RetroFeedbackNot BeingAddressOverloadingIterationsNot BeingAble to TellBusiness"No!"SomeoneSays "We'reLearning andGrowing!"NotEnoughTime ForTestingAllen notpayingattentionTeamCollaborationWas GreatSpicyArgumentsBetweenLeadersNotenoughtime forRetroLate-NightDeploymentsSomeone'sCode BreaksDuring theDemoLast-MinuteBusinessRequestsAcceptanceCriteriaUnclearRTE Says"Take ThisOffine"SomeoneSays "CanYou See MyScreen?"Someone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneAccidentallyTurns TheirCamera OnFirat or Allenscreenshotssomethingfor a meme

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