Not BeingAble to TellBusiness"No!"PretendingLike We'reAll Here InDecemberNotenoughtime forRetroDemo takingup morethan half ofthe meetingEnvironmentIssues3 WeekIterationsSuggestedLast-MinuteBusinessRequestsFirat or Allenscreenshotssomethingfor a memeSomeoneSays "We'reLearning andGrowing!"RTE Says"Take ThisOffine"AcceptanceCriteriaUnclearSpicyArgumentsBetweenLeadersOverloadingIterationsNotEnoughTime ForTestingRTE Says"GoodFeedback"Late-NightDeploymentsNeeding HelpFrom DevsFrom OtherTeams, ButThey Are BusySomeoneAccidentallyTurns TheirCamera OnSomeone'sCode BreaksDuring theDemoOld RetroFeedbackNot BeingAddressTeamCollaborationWas GreatAllen notpayingattentionSomeone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneSays "CanYou See MyScreen?"Not BeingAble to TellBusiness"No!"PretendingLike We'reAll Here InDecemberNotenoughtime forRetroDemo takingup morethan half ofthe meetingEnvironmentIssues3 WeekIterationsSuggestedLast-MinuteBusinessRequestsFirat or Allenscreenshotssomethingfor a memeSomeoneSays "We'reLearning andGrowing!"RTE Says"Take ThisOffine"AcceptanceCriteriaUnclearSpicyArgumentsBetweenLeadersOverloadingIterationsNotEnoughTime ForTestingRTE Says"GoodFeedback"Late-NightDeploymentsNeeding HelpFrom DevsFrom OtherTeams, ButThey Are BusySomeoneAccidentallyTurns TheirCamera OnSomeone'sCode BreaksDuring theDemoOld RetroFeedbackNot BeingAddressTeamCollaborationWas GreatAllen notpayingattentionSomeone says"Your FeedbackIs Valuable"Once The RetroIs CancelledSomeoneSays "CanYou See MyScreen?"

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