Successfullyrolled backa changeWrotecomprehensivedocumentationFound ahiddenconfigurationbugInfrastructureas CodeupdatedImprovedtestcoverageUpgradeda legacysystemReduceddeploymenttimeAdded anewmonitoringmetricAttendeda DevOpswebinarImplementeda newautomationMonitoringalerttriggeredat 2 AMFixed acriticalsecurityissueTeamcelebrated asuccessfuldeploymentDeploymentfailedPulledan all-nighterRefactoreda messyscriptExploreda newDevOpsframeworkLearned anew toolor scriptResolveda trickymergeconflictIncidentresponsecompletedwithin SLAHelped ateammatedebugCode reviewimprovedperformanceDebuggedaproductionissueCI/CDpipelineissueresolvedSuccessfullyrolled backa changeWrotecomprehensivedocumentationFound ahiddenconfigurationbugInfrastructureas CodeupdatedImprovedtestcoverageUpgradeda legacysystemReduceddeploymenttimeAdded anewmonitoringmetricAttendeda DevOpswebinarImplementeda newautomationMonitoringalerttriggeredat 2 AMFixed acriticalsecurityissueTeamcelebrated asuccessfuldeploymentDeploymentfailedPulledan all-nighterRefactoreda messyscriptExploreda newDevOpsframeworkLearned anew toolor scriptResolveda trickymergeconflictIncidentresponsecompletedwithin SLAHelped ateammatedebugCode reviewimprovedperformanceDebuggedaproductionissueCI/CDpipelineissueresolved

DevOps Sprint - 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. Successfully rolled back a change
  2. Wrote comprehensive documentation
  3. Found a hidden configuration bug
  4. Infrastructure as Code updated
  5. Improved test coverage
  6. Upgraded a legacy system
  7. Reduced deployment time
  8. Added a new monitoring metric
  9. Attended a DevOps webinar
  10. Implemented a new automation
  11. Monitoring alert triggered at 2 AM
  12. Fixed a critical security issue
  13. Team celebrated a successful deployment
  14. Deployment failed
  15. Pulled an all-nighter
  16. Refactored a messy script
  17. Explored a new DevOps framework
  18. Learned a new tool or script
  19. Resolved a tricky merge conflict
  20. Incident response completed within SLA
  21. Helped a teammate debug
  22. Code review improved performance
  23. Debugged a production issue
  24. CI/CD pipeline issue resolved