Learned anew toolor scriptRefactoreda messyscriptCI/CDpipelineissueresolvedResolveda trickymergeconflictInfrastructureas CodeupdatedFound ahiddenconfigurationbugDeploymentfailedImprovedtestcoverageFixed acriticalsecurityissueIncidentresponsecompletedwithin SLASuccessfullyrolled backa changeAdded anewmonitoringmetricHelped ateammatedebugPulledan all-nighterWrotecomprehensivedocumentationReduceddeploymenttimeDebuggedaproductionissueTeamcelebrated asuccessfuldeploymentExploreda newDevOpsframeworkUpgradeda legacysystemAttendeda DevOpswebinarImplementeda newautomationMonitoringalerttriggeredat 2 AMCode reviewimprovedperformanceLearned anew toolor scriptRefactoreda messyscriptCI/CDpipelineissueresolvedResolveda trickymergeconflictInfrastructureas CodeupdatedFound ahiddenconfigurationbugDeploymentfailedImprovedtestcoverageFixed acriticalsecurityissueIncidentresponsecompletedwithin SLASuccessfullyrolled backa changeAdded anewmonitoringmetricHelped ateammatedebugPulledan all-nighterWrotecomprehensivedocumentationReduceddeploymenttimeDebuggedaproductionissueTeamcelebrated asuccessfuldeploymentExploreda newDevOpsframeworkUpgradeda legacysystemAttendeda DevOpswebinarImplementeda newautomationMonitoringalerttriggeredat 2 AMCode reviewimprovedperformance

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