| No. | Item | Definition |
|---|---|---|
| 1. | acceptance | formal approval for release |
| 2. | alert | automatic warning of a problem |
| 3. | allocation | assignment of resources |
| 4. | approval | permission to continue |
| 5. | artifact | file produced by the build |
| 6. | audit | formal review of records |
| 7. | automation | use of tools for tasks |
| 8. | availability | time service is usable |
| 9. | backlog | queued work awaiting action |
| 10. | backout | planned reversal of a change |
| 11. | baseline | approved starting reference point |
| 12. | blocker | obstacle preventing progress |
| 13. | bottleneck | point limiting overall flow |
| 14. | branch | separate line of code history |
| 15. | briefing | short informative meeting or note |
| 16. | build | compiled version of the software |
| 17. | change | modification to systems or software |
| 18. | checklist | list of required steps |
| 19. | code freeze | halt on code changes |
| 20. | commit | saved code change in version control |
| 21. | communication | sharing information clearly |
| 22. | compatibility | ability to work together |
| 23. | configuration | settings controlling system behavior |
| 24. | contingency | backup response for problems |
| 25. | coordination | organizing people and tasks |
| 26. | cutover | switch to the new system |
| 27. | deadline | latest acceptable completion time |
| 28. | defect | flaw in software |
| 29. | dependency | required external component or library |
| 30. | deployment | putting software into production |
| 31. | documentation | written information about the system |
| 32. | downtime | period when service is unavailable |
| 33. | environment | configured system context |
| 34. | escalation | raising issue to higher support |
| 35. | estimate | predicted effort or duration |
| 36. | failover | automatic switch to backup |
| 37. | fallback | alternative plan if needed |
| 38. | forecast | expected future outcome |
| 39. | go-live | moment production use begins |
| 40. | governance | oversight and decision framework |
| 41. | handoff | transfer of responsibility |
| 42. | health check | quick system condition review |
| 43. | hotfix | urgent fix for production issue |
| 44. | impact | effect on systems or users |
| 45. | incident | unplanned event affecting service |
| 46. | integration | combining parts into a whole |
| 47. | issue | problem needing attention |
| 48. | latency | delay before response |
| 49. | launch | public start of availability |
| 50. | lead time | time from request to delivery |
| 51. | load test | test under expected demand |
| 52. | logging | recording system events |
| 53. | merge | combine code changes together |
| 54. | metric | measurable performance value |
| 55. | milestone | major project checkpoint |
| 56. | mitigation | action reducing harm or risk |
| 57. | monitoring | continuous observation of systems |
| 58. | orchestration | coordinated automation across steps |
| 59. | outage | unexpected service interruption |
| 60. | owner | person responsible for something |
| 61. | package | bundled software for distribution |
| 62. | patch | small corrective software update |
| 63. | performance | speed and efficiency of operation |
| 64. | pipeline | automated delivery workflow |
| 65. | policy | official rule or guideline |
| 66. | priority | relative importance for action |
| 67. | procedure | defined sequence of actions |
| 68. | production | live environment for users |
| 69. | readiness | state of being prepared |
| 70. | release | deployment of software to users |
| 71. | repository | storage for code or packages |
| 72. | requirement | needed feature or condition |
| 73. | resource | person, tool, or system asset |
| 74. | risk | chance of negative impact |
| 75. | rollback | reverting to a previous version |
| 76. | runbook | documented operational procedures |
| 77. | schedule | planned timing of work |
| 78. | scope | defined boundaries of work |
| 79. | severity | level of seriousness |
| 80. | sign-off | official approval to proceed |
| 81. | smoke test | basic check of core functions |
| 82. | staging | preproduction testing environment |
| 83. | stakeholder | person affected or interested |
| 84. | status | current condition or progress |
| 85. | tag | named marker for a version |
| 86. | telemetry | collected operational measurement data |
| 87. | testing | evaluating software behavior |
| 88. | throughput | amount processed over time |
| 89. | ticket | record of work or issue |
| 90. | timeline | sequence of planned dates |
| 91. | tracking | monitoring progress or issues |
| 92. | triage | prioritizing and routing issues |
| 93. | update | new information on progress |
| 94. | upgrade | move to a newer version |
| 95. | uptime | time service remains available |
| 96. | validation | checking against requirements |
| 97. | vendor | external supplier or provider |
| 98. | version | specific numbered software state |
| 99. | workaround | temporary alternative solution |
| 100. | workflow | ordered process of tasks |