DeploymentfailedUpgradeda legacysystemImplementeda newautomationSuccessfullyrolled backa changeReduceddeploymenttimeTeamcelebrated asuccessfuldeploymentIncidentresponsecompletedwithin SLAAttendeda DevOpswebinarImprovedtestcoverageExploreda newDevOpsframeworkHelped ateammatedebugPulledan all-nighterResolveda trickymergeconflictMonitoringalerttriggeredat 2 AMFixed acriticalsecurityissueAdded anewmonitoringmetricWrotecomprehensivedocumentationFound ahiddenconfigurationbugDebuggedaproductionissueCode reviewimprovedperformanceInfrastructureas CodeupdatedCI/CDpipelineissueresolvedRefactoreda messyscriptLearned anew toolor scriptDeploymentfailedUpgradeda legacysystemImplementeda newautomationSuccessfullyrolled backa changeReduceddeploymenttimeTeamcelebrated asuccessfuldeploymentIncidentresponsecompletedwithin SLAAttendeda DevOpswebinarImprovedtestcoverageExploreda newDevOpsframeworkHelped ateammatedebugPulledan all-nighterResolveda trickymergeconflictMonitoringalerttriggeredat 2 AMFixed acriticalsecurityissueAdded anewmonitoringmetricWrotecomprehensivedocumentationFound ahiddenconfigurationbugDebuggedaproductionissueCode reviewimprovedperformanceInfrastructureas CodeupdatedCI/CDpipelineissueresolvedRefactoreda messyscriptLearned anew toolor script

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