Last-MinuteBusinessRequests3 WeekIterationsSuggestedNotEnoughTime ForTestingPretendingLike We'reAll Here InDecemberNot BeingAble to TellBusiness"No!"EnvironmentIssuesOverloadingIterationsDemo takingup morethan half ofthe meetingRTE Says"GoodFeedback"Someone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneSays "CanYou See MyScreen?"Old RetroFeedbackNot BeingAddressSomeone'sCode BreaksDuring theDemoTeamCollaborationWas GreatRTE Says"Take ThisOffine"Needing HelpFrom DevsFrom OtherTeams, ButThey Are BusyLate-NightDeploymentsSpicyArgumentsBetweenLeadersSomeoneAccidentallyTurns TheirCamera OnAcceptanceCriteriaUnclearFirat or Allenscreenshotssomethingfor a memeSomeoneSays "We'reLearning andGrowing!"Notenoughtime forRetroAllen notpayingattentionLast-MinuteBusinessRequests3 WeekIterationsSuggestedNotEnoughTime ForTestingPretendingLike We'reAll Here InDecemberNot BeingAble to TellBusiness"No!"EnvironmentIssuesOverloadingIterationsDemo takingup morethan half ofthe meetingRTE Says"GoodFeedback"Someone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneSays "CanYou See MyScreen?"Old RetroFeedbackNot BeingAddressSomeone'sCode BreaksDuring theDemoTeamCollaborationWas GreatRTE Says"Take ThisOffine"Needing HelpFrom DevsFrom OtherTeams, ButThey Are BusyLate-NightDeploymentsSpicyArgumentsBetweenLeadersSomeoneAccidentallyTurns TheirCamera OnAcceptanceCriteriaUnclearFirat or Allenscreenshotssomethingfor a memeSomeoneSays "We'reLearning andGrowing!"Notenoughtime forRetroAllen notpayingattention

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