| 英文 | 中文 |
| A/B Testing | A/B测试
|
| Acceptance Stage | 验收阶段
|
| Acceptance Test-Driven Development (Atdd) | 验收测试驱动开发
|
| Acceptance Tests | 验收测试
|
| Accident | 事故
|
| Affinity | 亲和
|
| Agile | 敏捷
|
| Andon Cord | 安灯拉绳
|
| Anomaly Detection Techniques | 异常探测技术
|
| Antifragility | 抗脆弱性
|
| Application Deployment | 应用部署
|
| Artifact Management | 构件制品库管理
|
| Artifacts | 制品
|
| Automated Tests | 自动化测试
|
| Automation | 自动化
|
| Backlog | 待办事项列表
|
| Bad Apple Theory | 坏苹果理论
|
| Bad Paths | 失败路径
|
| Batch Sizes | 批次尺寸、批量大小
|
| Blame | 责备
|
| Blameless Post Mortem | 免责事后分析
|
| Blamelessness | 免责
|
| Blue-Green Deployment | 蓝绿部署
|
| Blue-Green Deployment Pattern | 蓝绿部署模式
|
| Branching Strategy | 分支策略
|
| Brownfield | 棕地
|
| Build | 构建
|
| Business Value | 业务价值
|
| Canary Release | 金丝雀发布
|
| Canary Release Pattern | 金丝雀发布模式
|
| Card | 卡片
|
| Change Categories | 变更类别
|
| Change Schedules | 变更计划
|
| Cloud Computing | 云计算
|
| Cloud Configuration Files | 云配置文件
|
| Cluster Immune System Release Pattern | 集群免疫系统发布模式
|
| Code Branch | 代码分支
|
| Code Review Forms | 代码审查表
|
| Codified Nfr | 成文的非功能需求
|
| Collaboration | 协作
|
| Commit Stage | 提交阶段
|
| Commit Code | 提交代码
|
| Compliance Requirement | 合规性要求
|
| Compliance Checking | 合规性检查
|
| Compliancy Officer | 合规检测官
|
| Configuration Management | 配置管理
|
| Container(S) | 容器
|
| Continuous Deployment | 持续部署
|
| Continuous Integration | 持续集成(CI)
|
| Continuous Delivery | 持续交付(CD)
|
| Conways Law | 康威定律
|
| Cycle Time | 周期时间
|
| Defect Tracking | 缺陷跟踪
|
| Definition Of Done (Dod) | 完成的定义
|
| Dev Rituals | 开发仪式
|
| Developer | 开发人员
|
| Development | 开发
|
| Devops Transformation | DevOps转型
|
| Downstream/Upstream | 下游/上游
|
| Downwards Spiral | 恶性循环
|
| E-Mail Pass-Around | 电子邮件轮查
|
| Expand/Contract Pattern | 扩张/收缩模式
|
| Exploratory Test | 探索性测试
|
| Fast Feedback | 快速反馈
|
| Feature | 特性
|
| Feature Flag | 特性标志
|
| Feature Toggles | 特性开关
|
| Feedback/Feedback Loop | 反馈/反馈回路
|
| Feedforward/Feedforward Loop | 前馈/前馈回路
|
| Flow | 流
|
| Gated Commit | 门控提交
|
| Gaussian Distribution | 高斯分布
|
| Green Build | 绿色构建
|
| Greenfield | 绿地
|
| Handoff | 交接
|
| Hand-Off Readiness Review | 交接就绪评审
|
| Happy Paths | 快乐路径
|
| Hypothesis-Driven Development | 假设驱动开发
|
| Incident | 事件
|
| Information Radiators | 信息辐射器
|
| Infosec | 信息安全
|
| Infrastructure Automation | 基础架构自动化
|
| Infrastructure As Code | 基础设施即代码
|
| Integration Tests | 集成测试
|
| I-Shaped, T-Shaped, E-Shaped | I型，T型，E型
|
| Iteration | 迭代
|
| Itsm (It Service Management) | IT服务管理
|
| Ji-Kotei-Kanketsu (Jkk) | 质量检查（JKK）
|
| Just Culture | 公正文化
|
| Just-In-Time (Jit) | 准时制
|
| Kaizen (In Lean) | 持续改善
|
| Kaizen Blitz (Or Improvement Blitz) | 持续改善闪电战
|
| Kanban | 看板
|
| Kata | Kata
|
| Large Batch Size Merge | 大批量合并
|
| Latent Defects | 潜在缺陷
|
| Lauching Guidance | 发布指导
|
| Launch Readiness Review | 投产就绪评审
|
| Lead Time | 前置时间
|
| Lean | 精益
|
| Learning Culture | 学习文化
|
| Logging Levels | 日志级别
|
| Loosely Coupled Architecture | 松耦合架构
|
| Micro-Services | 微服务
|
| Minimum Viable Product | 最小化可行产品
|
| Monitoring Framework | 监控框架
|
| Monolithic Applications | 单体应用
|
| Monolytics | 单体应用
|
| Mttr | 平均恢复时间
|
| Non-Functional Requirement (Nfr) | 非功能性需求
|
| Non-Functional Requirement (Nfr) Testing | 非功能需求测试
|
| (Non) Ideal Testing Pyramid | （非）理想测试金字塔模型
|
| One-Piece-Flow | 单件流
|
| Operations | 运维
|
| Operations Story | 运维故事
|
| Ops Liaison | 运维联络人
|
| Organisational Typology Model | 组织结构模型
|
| Organization Archetypes | 组织原型
|
| Organizational Learning | 组织级学习
|
| Over-The-Shoulder | 观察者评审
|
| Packages | 包
|
| Pair Programming | 结对编程
|
| Peer Review | 同行评审
|
| Pilot | 试点
|
| Pipeline | 流水线
|
| Plan-Do-Check-Act Cycle (Pdca Cycle) | 计划-实施-检查-改进 （戴明环）
|
| Post Mortems | 事后回顾
|
| Post-Mortem | 事后剖析
|
| Process Time | 处理时间
|
| Product Owner | 产品负责人
|
| Pull Request Process | 拉动请求流程
|
| Qa | 质量保证
|
| Reduce Batch Size | 降低批次尺寸
|
| Reduce Number Of Handoffs | 减少交接次数
|
| Regression Test | 回归测试
|
| Release Branch | 发布分支
|
| Release Managers | 发布经理
|
| Release Patterns | 发布模式
|
| Retrospective | 回顾
|
| Rhythm | 节奏
|
| Roll-Back | 回滚
|
| Sad Path | 悲伤路径
|
| Safety Culture | 安全文化
|
| Safety Conditions | 安全条件
|
| Scaling | 规模化
|
| Scrum | Scrum
|
| Scrum Master | Scrum Master
|
| Security Testing | 安全测试
|
| Self Service Capability | 自服务能力
|
| Service Deployment | 服务部署
|
| Service Level Agreement (Sla) | 服务级别协议(SLA)
|
| Shared Goals | 共享目标
|
| Shared Operations Team (Sot) | 共享运维团队
|
| Shared Version Control | 共享版本控制
|
| Single Repository | 单一存储库
|
| Smoke Testing | 冒烟测试
|
| Sprint | 冲刺
|
| Staging | Staging
|
| Staging Environments, Sit | 准生产环境
|
| Stakeholder | 利益干系人
|
| Standard Deviation | 标准差
|
| Standard Operations | 标准运维
|
| Static Code Analysis | 静态代码分析
|
| Swarm | 聚集、聚焦、会诊、围观（动词）
|
| Swarming | 聚集
|
| System Of Engagement (Soe) | 交互系统
|
| System Of Records (Sor) | 记录系统
|
| Technical Debt | 技术债务
|
| Technology Adaption Curve | 技术适应曲线
|
| Technology Executives | 技术主管
|
| Telemetry | 遥测
|
| Test Coverage Analysis | 测试覆盖率分析
|
| Test Story | 测试故事
|
| Test-Driven Development | 测试驱动开发
|
| The Downward Spiral - Tds | 下行螺旋
|
| The Agile Manifesto | 敏捷宣言
|
| The Lean Movement | 精益运动
|
| The Simian Army: Chaos Gorilla, Chaos Kong, Conformity Monkey, Doctor Monkey, Janitor,Monkey, Latency Monkey, Security Monkey | 猿猴军团（可靠性监控服务），Chaos Gorilla（混沌大猩猩）， Chaos Kong（混沌金刚）, Conformity Monkey（一致性猴子）, Doctor Monkey（医生猴子）, Janitor Monkey（看门猴子）, Latency Monkey（延迟猴子）, Security Monkey（安全猴子）
|
| The Three Ways | 三步工作法
|
| Theory Of Constraints | 约束理论
|
| Ticketing System | 工单系统
|
| Tightly-Coupled | 紧耦合
|
| Tool-Assisted Review | 工具辅助评审
|
| Tools | 工具
|
| Toyota Production System (Tps) | 丰田生产系统
|
| Toyoto Kata | 丰田套路
|
| Transformation Team | 转型团队
|
| Trunk | 主干
|
| User Story | 用户故事
|
| Value Stream Mapping | 价值流映射
|
| Value Stream | 价值流
|
| Velocity | 速率
|
| Version Control | 版本控制
|
| Virtualized Environment | 虚拟化环境
|
| Visible | 可视的
|
| Visualisation | 可视化
|
| Waste | 浪费
|
| Waste Reduction | 减少浪费
|
| Waterfall | 瀑布式
|
| Wip (Work In Progress / Process) | 在制品
|
| Wip Limit | 在制品限制
|
| Work Center | 工作中心 |
|
|
|
|
| 参与修订说明 |
|
|
|
转播
分享
淘帖
()