Productionjob failedoutside ofworkinghoursHad a standup whereeveryonesaid "Noblockers"Improved aquery'sperformancesignificantlystayed uplate for adeadlineFinished ataskahead ofscheduleDiscovered adata qualityissue inproductionSee up orimprovedlogging/monitoringAddedsubtasks toall youruser storiesHad PTOThissprintSolveda toughbugCreated newairflow Dagor similarorchestrationtoolHad to rollback adeploymentReceived acomplimentfrom astakeholderor analystattended ameeting thatcould'vebeen andemailHelped ateammatetroubleshootIntergrateda newdatasourceWrotedocumentationfor a previouslyundocumentedprocessGotblockedWrote orupdated adatavalidationtestDiscoveredunexpecteddataDiscovered aduplicatedataingestionissueLearned anewpython orspark trickSuccessfullydeployed adatapipelineFoundand fixeda schemamismatchProductionjob failedoutside ofworkinghoursHad a standup whereeveryonesaid "Noblockers"Improved aquery'sperformancesignificantlystayed uplate for adeadlineFinished ataskahead ofscheduleDiscovered adata qualityissue inproductionSee up orimprovedlogging/monitoringAddedsubtasks toall youruser storiesHad PTOThissprintSolveda toughbugCreated newairflow Dagor similarorchestrationtoolHad to rollback adeploymentReceived acomplimentfrom astakeholderor analystattended ameeting thatcould'vebeen andemailHelped ateammatetroubleshootIntergrateda newdatasourceWrotedocumentationfor a previouslyundocumentedprocessGotblockedWrote orupdated adatavalidationtestDiscoveredunexpecteddataDiscovered aduplicatedataingestionissueLearned anewpython orspark trickSuccessfullydeployed adatapipelineFoundand fixeda schemamismatch

Sprint 3 Retro 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. Production job failed outside of working hours
  2. Had a stand up where everyone said "No blockers"
  3. Improved a query's performance significantly
  4. stayed up late for a deadline
  5. Finished a task ahead of schedule
  6. Discovered a data quality issue in production
  7. See up or improved logging/monitoring
  8. Added subtasks to all your user stories
  9. Had PTO This sprint
  10. Solved a tough bug
  11. Created new airflow Dag or similar orchestration tool
  12. Had to roll back a deployment
  13. Received a compliment from a stakeholder or analyst
  14. attended a meeting that could've been and email
  15. Helped a teammate trouble shoot
  16. Intergrated a new data source
  17. Wrote documentation for a previously undocumented process
  18. Got blocked
  19. Wrote or updated a data validation test
  20. Discovered unexpected data
  21. Discovered a duplicate data ingestion issue
  22. Learned a new python or spark trick
  23. Successfully deployed a data pipeline
  24. Found and fixed a schema mismatch