SAFe? 4.0术语表中文版(二)

-回复 -浏览
楼主 2018-06-20 04:52:39
举报 只看此人 收藏本贴 楼主

Scaled Agile Framework? Terms and Definitions?

规模化敏捷框架术语和定义


? 2016 Scaled Agile, Inc.

All Rights Reserved.

中文简体翻译由? 2011-2016 Scaled Agile, Inc

授权SPC4赵卫翻译。

Scaled Agile Inc. 没有审查或认证这些翻译,对翻译的准确性不做任何保证。

DevOps

DevOps is a mindset, culture, and set of technical practices that stresses communication, collaboration, and close cooperation between Agile development teams and other technology professionals who are necessary for developing, testing, deploying, and maintaining softwareand systems.

DevOps

DevOps是一种心态、文化和一整套技术实践。它强调沟通、协作,以及敏捷开发团队和其他专业技术人员(包括开发、测试、部署和维护软件和系统所必需的人员)的密切合作。

?

Economic Framework

An economic framework is a set of decision rules that aligns everyone to the financial objectives of the mission,including budget considerations driven from the program portfolio. SAFe’s first Lean-Agile principle is to take an economic view; the economic framework captures the essential economic elements for successful solution development.

经济框架(Economic Framework)

经济框架是一组决策规则,它能使每个人都与使命的财务目标保持一致,其中包括项目群投资组合驱动的预算考虑。SAFe的第一个精益-敏捷原则就是采取经济视角,经济框架代表了成功的解决方案开发的基本经济要素。

?

Enabler Capability

Enabler capabilities occur at the value stream level, where they capture work of that type. As these enablers are a type of capability, they share the same attributes, including a statement of benefits and acceptance criteria, and they must be structured so as to fitwithin a single PI.

使能能力(Enabler Capability)

使能能力出现在价值流层,它们表示价值流层的工作类型。使能能力作为能力的一种类型,它们和能力一样具有相同的属性,包括收益声明、接收标准(acceptance criteria),同时也必须对它们进行结构化,从而可以适合单个PI的执行。

?

Enabler Epic

Enabler epics are a type of epic, and as such are written using the value statement format defined for epics. They tend to cut across value streams and PIs. They require a light weight business case to support their implementation. They are identified and tracked through the portfolio Kanban system.

使能史诗(Enabler Epic)

使能史诗是史诗的一种类型,与编写和定义史诗所采取的价值声明格式相同。它们倾向于跨越多个价值流和PI。使能史诗要求轻量业务案例来支持其实现,它们通过投资组合看板系统来进行识别和跟踪。

?

Enabler Feature

Enabler features occur at the program level, where they capture work of that type. As these enablers are a type of feature, they share the same attributes, including a statement of benefits and acceptance criteria, and are structured so as to fit within a single PI.

使能特性(Enabler Feature)

使能特性出现在项目群层,它们表示项目群层的工作类型。使能特性作为特性的一种类型,他们和特性一样具有相同的属性,包括收益声明、接收标准,同时也必须对它们进行结构化,从而可以适合单个PI的执行。

?

Enabler Story

Enabler stories, as a type of story, must fit in iterations. However, while they may not require user voice format, they have acceptance criteria to clarify their requirements and support demonstration and testing.

使能故事(Enabler Story)

使能故事作为故事的一种类型,必须适合迭代执行。然而,虽然有可能不需要采取用户故事的格式,但它们有接收标准来澄清需求,并支持演示和测试。

?

Enablers

Enablers encapsulate the exploration and the architectural and infrastructure development activities necessary to support some future solution capability. They occur at all levels of the framework and are described as enabler epics, enabler capabilities, enabler features, and enabler stories, depending on their level.

使能(Enablers)

使能封装了支持未来解决方案能力所必须的探索(exploration)、架构(architectural)和基础设施(infrastructure)开发活动。它们出现在SAFe框架的所有层级,根据不同的层级,分别被描述为使能史诗(enabler epics)、使能能力(enabler capabilities)、使能特性(enabler features)和使能故事(enabler stories)。

?

Enterprise

The enterprise represents the business entity that has the ultimate strategy, fiduciary, and governance authority forthe value streams that constitute a SAFe? portfolio. Each SAFe?portfolio exists in the broader enterprise context; that is the source of the business strategy that the portfolio must address. The enterprise also provides the general governance model for all portfolios.

企业(Enterprise)

企业代表商业实体,它拥有最终战略、受托和治理权力,从而执行价值流并构成SAFe的投资组合。每个SAFe?投资组合都存在于更广泛的企业环境中,企业环境是投资组合必须要解决的业务战略的来源。企业也对所有的投资组合提供了总体治理模型。

?

Enterprise Architect

The Enterprise Architect works with business stakeholders and Solution and System Architects to drive holistic technology implementation across value streams. The Enterprise Architect relies on continuous feedback, fosters adaptive design and engineering practices, and drives collaboration of programs and teams around a common technical vision.

企业架构师(enterprise Architect)

企业架构师和业务利益相关者、解决方案架构师以及系统架构师一起工作来驱动跨价值流的整体技术实施。企业架构师依靠持续的反馈促进适应性设计和工程实践,并驱动项目群和团队围绕共同的技术愿景协作。

?

Epic

Epics are significant initiatives that help guide value streams toward the larger aim of the portfolio. They areinvestment intensive and far ranging in impact. They require a formulation and analysis of cost, impact, and opportunity in a lightweight business case, as well as financial approval before implementation. There are two kinds of epics: business epics and enabler epics, and they may appear at the portfolio, valuestream, and program levels.

史诗(Epic)

史诗是重大的举措,它帮助引导价值流朝着更大的投资组合目标前进。他们是密集型投资,并且对价值流和解决方案具有深远影响。史诗的轻量业务案例里需要规划、成本分析、影响和机会分析,同时史诗在实现之前也需要财务的审批。有两种类型的史诗:业务史诗和使能史诗,它们会出现在投资组合层、价值流层和项目群层。

?

Epic Owners

Epic Owners have the responsibility of shepherding epics through the portfolio Kanban system. They develop the business case and, when approved, work directly with the key stakeholders on the affected trains to help realize the implementation.

史诗负责人(Epic Owners)

史诗负责人通过投资组合看板系统来跟踪史诗。他们开发业务案例,当史诗被审批通过后,与受影响的火车上的关键利益相关者一起工作,以此来帮助史诗的实现。

?

Feature

A Feature is a service provided by the system that fulfills stakeholder needs. Each is developed by a single Agile Release Train. They are maintained in the program backlog and are sized to fitin a program increment so that each PI delivers conceptual integrity. Each feature includes a statement of benefits and defined acceptance criteria..

特性(Feature)

特性是由系统提供的服务来满足利益相关者的需要。每个特性由单个敏捷发布火车开发。它们在项目群待办事项列表(program backlog)中维护,并且特性的规模大小适合一个项目群增量,从而保证每个PI交付概念上的完整性。每个特性都包含收益声明和定义的接收标准。

?

Implementing 123

Implementing SAFe? 1-2-3 is aproven, successful pattern for SAFe? implementation. It describes three basic steps: (1) train implementers andLean-Agile change agents; (2) train all executives, managers, and leaders; (3)train teams and launch Agile Release Trains.

实施步骤123(Implementing 123)

实施SAFe? 的1-2-3步骤,对于实施SAFe?来说是一个经过验证的成功模式。它描述了三个基本步骤:(1)培训实施者和精益-敏捷变革推动者(change agents);(2)培训所有的高管、经理和领导(3)培训团队和启动敏捷发布火车。

?

Innovation and Planning Iteration

SAFe? provides for periodicinnovation and planning iterations, which serve a variety of purposes. They provide an estimating buffer for meeting objectives, a dedicated time for inspect and adapt and PI Planning activities, a cadence-based opportunity for innovation, time for continuing education, time for working on the technical infrastructure and other impediments, and time for backlog refinement.

创新与计划迭代(Innovation and Planning Iteration)

SAFe?提供了许多周期性的创新与计划迭代,服务于各种用途。它们为实现目标提供预估的缓冲时间,为检视和调整,以及PI计划活动提供了专有的预留时间,为创新提供了基于节奏的机会,为持续教育提供了时间,为开发技术基础设施和消除其他障碍提供了时间,也为待办事项列表的优化(backlog refinement)提供了时间。

?

Inspect and Adapt

Inspect and adapt (I&A) is a regular event, held at the end of each PI, that provides timeto demonstrate the solution; get feedback; and then reflect, problem solve, and identify improvement actions. The improvement items can then be immediately incorporated into PI planning.

检视和调整(Inspect and Adapt)

检视和调整(Inspect and Adapt, I&A)是一个周期性的事件,在每个PI结束的时候举行。它提供时间来展示解决方案、获取反馈,然后省思、解决问题,以及识别改进行动。识别出的改进行动可以立即被纳入到PI计划活动中。

?

Iteration Execution

In SAFe?, iterations have a fixed, two-week timebox. Agile Teams take items from the iteration backlog and define, build, and test them into the system baseline during this two-weekperiod.

迭代执行(Iteration Execution)

在SAFe?里,迭代有一个固定的、为期两周的时间盒。敏捷团队在这两周期间,从迭代待办事项列表(iteration backlog)中领取待办事项,并对其进行定义、构建和测试,以达到系统基线的要求。

?

Iteration Goals

Iteration goals are a high-level summary of the business and technical goals that the team and Product Owner agree to accomplish in an iteration. In SAFe?, iteration goals are integral to the effective coordination of an Agile Release Train as a self-organizing, self-managing team of teams.

迭代目标(Iteration Goals)

迭代目标是业务和技术目标的概要总结,团队和产品负责人达成共识,可以在一个迭代内完成这些目标。在SAFe?中,迭代目标是对敏捷发布火车进行有效协调的组成部分,而敏捷发布火车又是通过多个团队所组成的自组织和自管理团队。

?

Iteration Planning

Iteration planning is the ceremony during which all team members plan the upcoming iteration. The output of the meeting includes the iteration backlog, consisting of the stories and acceptance criteria committed to in the iteration; a statement of iteration goals; and acommitment by the team to the work needed to achieve those goals.

迭代计划(Iteration Planning)

迭代计划是一个仪式,在这期间所有的团队成员一起对即将执行的迭代进行计划。这个会议的产出物包括:迭代待办事项列表、在迭代期间内承诺完成的故事和接收标准、迭代目标声明、以及为了实现这些目标团队对所需工作的承诺。

?

Iteration Retrospective

The iteration retrospective is a shortteam meeting held at the end of an iteration, wherein team members gather in a private, SAFe? environment to discuss the efficacy of their practices and define improvements for the upcoming period.

迭代回顾(Iteration Retrospective)

迭代回顾是迭代结束时的一个用时较短的团队会议,团队成员聚在一个私密的SAFe?安全环境,讨论他们的实践效果以及定义在即将开始的迭代期间要做的改进。

?

Iterations

Iterations (sprints in Scrum)are a strict timebox in which teams deliver incremental value in the form of working, tested software and systems. Each iteration has a standard pattern:plan the iteration; commit to a goal; execute; demo the work to the key stakeholders; and, finally, hold a retrospective, wherein the team analyzes and determines actions necessary to improve their performance.

迭代(Iterations)

迭代(在Scrum中叫Sprint冲 刺)是一个严格的时间盒,在时间盒中,团队可以交付增量价值,这些增量价值通过工作的、经过测试的软件和系统的方式得以体现。每个迭代有一个标准模式:迭 代计划、承诺目标、执行、向关键利益相关者演示、最后举行回顾会议,在回顾会议中,团队分析和决定一些必要的改进行动,从而提升他们的绩效。


注:欢迎大家对翻译的内容进行反馈。本文是基于2016年7月的英文版,最新的英文术语表是2016年11月29日版本,请参阅:http://www.scaledagileframework.com/glossary/


有关SAFe的文章:

SAFe?敏捷不敏捷?

SAFe和LeSS不同思路之思辨


SAFe? 4.0术语表中文版

SAFe? 4.0术语表中文版(一)


赵卫:

  • IBM大中华区首席技术官办公室,敏捷及DevOps卓越中心主管,敏捷教练及顾问。

  • 认证规模化敏捷框架咨询师SPC4(Certified SAFe4.0 Program Consultant),认证Scrum专家(CSP),CSM,认证看板(Certified Kanban Training),IBM设计思维实践者。

  • 赵卫先生是国内最早最有经验的规模化敏捷框架SAFe的精益敏捷教练之?,拥有丰富的大规模组织(>500人)敏捷转型经验。赵卫先生拥有16年以上的通信及IT行业经验,曾作为诺基亚西门子研发经理和部门敏捷转型负责人,实践团队级别和部门级的敏捷转型。作为敏捷咨询师为通信、银行、金融、电商、汽 车以及电器工厂等各行业客户常年提供敏捷咨询服务。从2006年第一届敏捷中国开始,每年的敏捷中国都积极参与。并且参与了ScrumGathering 的多次会议。2015年在日本札幌ProMAC项目管理国际大会进行有关产品开发流的演讲。2016年澳大利亚ProMAC项目管理国际大会发表有关大规 模敏捷转型变革框架的文章。


欢迎联系赵卫,和IBM组织级敏捷转型专家交流。


Presented to you by IBM GBS GCG Agile/DevOps Center of Excellence.


我要推荐
转发到