[{"title":"Agile","question":"什么是敏捷？","description":"一种重视适应性和持续交付的软件开发方法。","date":"2024-11-10","categories":["agile"],"published":true,"slug":"agile","content":"

🔍 定义

敏捷是一种软件开发哲学，专注于通过适应性、协作和快速响应变化，持续向客户交付价值。

🚀 起源

敏捷的起源可以追溯到2000年代初，2001年创建敏捷宣言是一个关键事件。

🧠 运动

它开始是作为对传统项目式软件开发方法的局限性和挑战的回应，这些传统方法被称为瀑布方法，它们是顺序的且不灵活的。

🔁 方法

敏捷基于迭代和增量开发方法，将范围划分为小部分，并频繁交付，以适应变化的需求。

🤝 协作

敏捷专注于团队协作和客户在整个开发过程中的参与。

📈 好处

它以提高产品质量、员工和客户满意度以及开发速度而闻名。

📚 敏捷框架

敏捷包含并与各种方法和框架相关，如Scrum、Kanban和Lean。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Agile Coach","question":"什么是敏捷教练？","description":"敏捷教练是指导团队和组织灵活性的人。","date":"2024-11-10","categories":["role","agile"],"published":true,"slug":"agile-coach","content":"

🔍 定义

敏捷教练是敏捷性的专家，指导个人、团队和组织采用敏捷原则和实践。

📅 起源

敏捷教练这一角色由肯特·贝克在1999年他的书《极限编程解释：拥抱变化》中首次提出。

📈 历史发展

这一角色最初侧重于指导团队采用敏捷实践，并已发展为包括更广泛的组织变革。

🪓 职责

他们促进敏捷框架如Scrum或Kanban的采用，推广自我组织，并领导组织的敏捷转型。

🔑 能力

敏捷教练必须具备促进、培训、指导、沟通和变革管理的技能。

🌐 重要性

他们的角色在帮助组织应对敏捷转型的复杂性和实现可持续变革中至关重要。

👤 关键人物

莉莎·阿德金斯是敏捷教练职业发展中最著名的人物之一。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Agile Manifesto","question":"什么是敏捷宣言？","description":"它是一份关于新的软件开发方式的4个价值观和12个原则的声明。","date":"2024-11-10","categories":["agile","scrum","kanban","manifesto","values","principles"],"published":true,"slug":"agile-manifesto","content":"

📜 定义

敏捷宣言是一份于2001年2月12日由17位软件开发专家创建的文件，概述了一种优先考虑灵活性和客户合作的软件开发新方法。

🌐 背景

这是对传统软件开发方法局限性的回应，旨在更好地满足数字时代用户迅速变化的需求。

🏔️ 地点

该文件在美国犹他州Snowbird滑雪度假村制定。从这次面对面会议中产生了4个价值观，后来12个原则通过远程方式发展而来。

💎 价值观

首先，它重视人际互动超过流程；其次，它优先考虑有效的软件超过详尽的文档；第三，它更喜欢与客户直接合作而非合同谈判；第四，它强调适应变化的重要性超过遵循计划。

🛠 原则

敏捷宣言的12个原则补充其价值观，促进频繁交付，即使在后期阶段，也将变化作为竞争优势，并围绕有动机的个体构建项目。这些原则旨在实现客户满意度、开发的可持续性和技术卓越。

📄 访问敏捷宣言

为了深入了解这些已经彻底改变软件开发的价值观和原则，建议直接阅读敏捷宣言。通过此链接到敏捷宣言免费访问完整文档。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"ALM","question":"ALM代表什么？","description":"代表应用生命周期管理。","date":"2024-11-10","categories":["ALM","development","software","DevOps"],"published":true,"slug":"alm","content":"

📜 定义

ALM，即应用生命周期管理，指的是从软件应用的初步设计和开发到最终退役的管理过程。

🔑 关键方面

它涉及各个阶段，如想法的构思、设计、开发、测试、生产、支持和最终的停用。

📈 重要性

了解ALM对于高效的软件开发至关重要，确保应用程序满足业务目标，并在其整个生命周期中得到成功管理。

🎯 构思

利益相关者在初期阶段定义他们对应用程序的需求，通常通过用户故事。

🛠️ 开发

团队协作将需求转化为功能应用程序，包括设计、编码和质量分析等任务。

🧪 测试

应用程序经过严格测试，确保满足规定的要求并且无缺陷。

🚀 部署

开发并测试过的应用程序被发布给最终用户，通常涉及版本管理和部署计划。

🔧 维护

一个持续的阶段，支持和开发团队共同解决问题，计划更新和改进产品。

🤖 自动化

根据DevOps方法的原则，ALM的许多常规任务应该自动化，以确保其质量并将其设立为确保质量的标准。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Antipattern","question":"什么是反模式？","description":"一个降低生产力、沟通或质量的不良实践。","date":"2024-11-10","categories":["best practice","agile"],"published":true,"slug":"antipattern","content":"

🎯 定义

反模式指的是常见问题或不良实践，妨碍敏捷框架的成功实施。

🚫 影响

反模式可能导致生产力下降、交付质量低下，并且无法充分实现敏捷实践的好处。

🔍 示例

一个常见的敏捷反模式是“功能工厂”，它专注于交付功能而不考虑其真实价值。

\n","language":"zh","alternativeLangs":["cs","da","de","en","fi","fr","it","ja","ko","no","pl","pt","ru","sv","tr"]},{"title":"API","question":"什么是 API？","description":"代表应用程序编程接口。","date":"2024-11-10","categories":["it","dev"],"published":true,"slug":"api","content":"

🤖 定义

API，即应用程序编程接口，是一套允许不同软件应用程序相互通信的规则和协议。

🔗 目的

APIs 充当应用之间的桥梁，实现数据和功能交换，对现代软件和网络应用至关重要。

🔄 功能

API 通过定义软件模块的交互方式来工作：一个应用程序发出请求，另一个提供响应，所有这些都遵循 API 设定的规则。

🤝 合同

为确保通信的一致性和安全，定义了应用程序之间的服务合同，概述了请求和响应的结构应该如何。

🌐 网络服务

所有网络服务都是 API，但不是所有 API 都是网络服务，因为 API 也可用于本地应用程序之间的通信。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Asana","question":"什么是 Asana？","description":"它是一款实现看板方法的项目管理软件。","date":"2024-11-10","categories":["tool","kanban","information radiator"],"published":true,"slug":"asana","content":"

🎯 定义

Asana 是一款项目管理工具，通过可视化看板加强团队协作与任务管理。

🚀 功能

Asana 提供任务分配、进度追踪和团队沟通功能，支持多种项目管理方法包括敏捷和传统模式。

🌐 可访问性

Asana 可在线使用，方便远程和分布式团队。

🔄 与看板的关系

Asana 通过允许任务在看板上可视化，作为信息显示器，实施看板方法。这些看板提供了工作流程和每个任务进度的清晰视图。

🔗 访问

访问 Asana，请访问他们的网站

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"ASAP","question":"ASAP 是什么意思？","description":"尽可能快。","date":"2024-11-10","categories":["expression"],"published":true,"slug":"asap","content":"

🔍 意义

ASAP 表示“尽快”（As Soon As Possible），是一个缩写词，用于表示请求或任务的紧迫性。

📧 使用

在电子邮件中常用以表示某事需要紧急关注或完成。

💬 非正式场合

它也用于非正式沟通，如短信和聊天，以传达对快速响应或行动的需求。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Backlog","question":"什么是Backlog？","description":"它是一个有序的任务列表。","date":"2024-11-10","categories":["scrum","agile","product"],"published":true,"slug":"backlog","content":"

📋 定义

Backlog是从路线图和其需求衍生的开发团队的有序工作列表。

🔑 重要性

它作为项目工作项的列表，帮助计划迭代，并促进集体优先级的确定。

🎯 优先排序

Backlog项应根据客户价值或实现难度等标准进行优先排序。

📝 详述

最重要的项目详细描述更多，优先级较低的则详细描述较少，通常位于Backlog的底部。

🔄 生活列表

它是一个活列表，应随着其项目的开发进度而变化。

🏉 Scrum

在Scrum中，有两种使用Backlog概念的工件：产品Backlog和Sprint Backlog。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"BDD","question":"什么是BDD？","description":"BDD代表行为驱动开发。","date":"2024-11-10","categories":["dev","it","bdd","software development","testing","gherkin","collaboration"],"published":true,"slug":"bdd","content":"

📜 定义

行为驱动开发（BDD）是一种软件开发过程，旨在改善协作。它关注从用户的角度定义系统的行为，使用自然语言编写的规格说明。

🌐 背景

BDD是从测试驱动开发（TDD）演化而来，对需求和系统行为采取更加以用户为中心的方法。这种方法有助于确保软件开发更好地与最终用户的期望和需求对齐。

🏔️ 从TDD到BDD的演变

从TDD到BDD的过渡以关注点从仅基于代码的测试转向基于用户视角的系统行为的测试为特征。这有助于更深入地理解用户的需求以及系统应如何表现以满足这些需求。

💎 Gherkin语言

BDD使用Gherkin语言以技术和非技术团队成员都能理解的方式编写规格说明。这允许规格说明作为共享的真理来源，提高沟通效率并减少误解。

📄 对齐

BDD促进对预期软件行为的共同理解，确保所有涉及方，包括非技术利益相关者，都对项目的目标有一个清晰的理解。这种方法有助于避免业务需求与开发团队交付结果之间的差异。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Beta","question":"什么是beta版本？","description":"它是向一组选定的用户提供的软件预发布版本，用于测试。","date":"2024-11-10","categories":["version","alpha","development","mvp","software","feedback"],"published":true,"slug":"beta","content":"

🔬 定义

Beta版本，也称为预览版，是一种软件预发布版本，向一组选定的用户提供，用于测试。

🛠️ 目的

它允许开发者收集反馈，识别并修复漏洞，并在软件正式向公众发布之前确保其稳定性和功能性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Backend for Frontend - BFF","question":"什么是Backend for Frontend BFF？","description":"一种架构模式，为每种类型的前端界面创建特定的后端服务。","date":"2024-11-10","categories":["BFF","architectural pattern","backend services","user experience"],"published":true,"slug":"bff","content":"

🔄 定义

Backend for Frontend（BFF）是一种架构模式，涉及为每种类型的前端界面创建特定的后端服务，优化并适应每个前端的独特需求。

📱 目的

BFF用于通过定制后端服务以满足不同前端界面的需求（如Web、移动或第三方应用）来改善用户体验。

🔧 实施

BFF通过引入一层后端服务来实现，这些服务作为主后端和前端之间的中介，管理每个前端的特定请求和响应。

🚀 优势

BFF增强了软件应用的适应性、前后端团队的独立性、性能和易于进化。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Blended Learning","question":"什么是混合学习？","description":"它是一种教育方法，将面对面教学与在线学习活动相结合。","date":"2024-11-10","categories":["blended learning","b-learning","education","online learning","educational technology"],"published":true,"slug":"blended-learning","content":"

🔍 定义

混合学习（也称为B-learning），是一种教育方法，结合了面对面教学和在线学习活动。

🎯 目的

这种方法旨在整合两种教育世界的最佳元素，以丰富学生的学习体验。

💻 在线组件

培训的在线部分并不取代面对面课程，而是补充它们，提供更灵活、更互动的学习体验。

🔄 翻转课堂

翻转课堂是指一种学习方法，学生在家通过在线资源学习新内容，然后在课堂上在老师的指导下应用这些内容。

📈 优势

混合学习的一些好处包括互动、灵活性、学生参与度和可访问性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Blue / Green","question":"什么是Blue / Green部署？","description":"这是一种软件部署方法，涉及维护两个完全相同的生产环境。","date":"2024-11-10","categories":["deployment","CI","CD","DevOps","ALM"],"published":true,"slug":"blue-green","content":"

🔄 定义

这是一种软件部署方法，涉及维护两个完全相同的生产环境，其中一个环境（蓝色）运行应用程序的当前版本，另一个（绿色）运行新版本。

🚦 流量切换

在任何给定时间，只有一个环境接收实时流量，所有生产流量都指向它，而不活跃的环境用于测试和推出新变更。

🔁 回滚

如果新版本出现问题，可以立即将流量切换回之前的实时环境，最小化停机时间和风险。

🌐 目标

该方法旨在通过立即将请求从一个环境重定向到另一个环境来减少部署期间的停机时间。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Bottom-Up","question":"什么是自下而上的转型方法？","description":"它涉及从团队到组织的高层的转变。","date":"2024-11-10","categories":["transformation","agile","approach","empowerment"],"published":true,"slug":"bottom-up","content":"

⬆️ 定义

在敏捷转型中，自下而上的方法意味着团队和个人启动敏捷实践，转型逐渐向上渗透，通常通过管理层，遍及整个组织。

👥 授权

此方法强调在团队级别进行授权和变革，允许自我组织和敏捷原则的自然采用。

📈 进展

自下而上的转型通常从一个或多个试点团队开始，允许逐步的敏捷实施方法和在规模化前调整过程的能力。

🚀 灵活性

团队可以根据组织的具体需求量身定制敏捷方法，可能导致更定制化和有效的转型。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Bug","question":"什么是bug？","description":"它是代码中的一个错误，导致程序功能障碍。","date":"2024-11-10","categories":["bug","development","software","qa","test"],"published":true,"slug":"bug","content":"

🐛 定义

在软件领域，bug指的是代码中的错误或缺陷，导致程序功能障碍。

💻 起源

“bug”这个术语最早由托马斯·爱迪生在1889年使用，用来描述技术问题，自那时起在计算机中被用来描述软件问题。

🔍 调试

找到并修复bug的过程称为调试，开发者使用称为调试器的工具来完成这一目的。

💡 重要性

Bug可以有重大的影响，从小问题到大的安全漏洞。

🪲 字面意义

词“bug”字面意思是昆虫，在1947年一只飞蛾在计算机继电器中引起问题时，幽默地用来描述技术问题。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Build","question":"什么是build？","description":"它是创建和编译软件的过程，结果是程序的可执行版本。","date":"2024-11-10","categories":["software development","build","automation","software quality"],"published":true,"slug":"build","content":"

📜 定义

在软件开发领域，build指的是创建和编译软件的过程，该过程产生程序的可执行版本。这个过程对于软件发布前的测试和调试至关重要。

📦 结果

“build”这个术语也指构建过程的结果，即软件版本。这个结果对于测试的不同阶段和软件的最终实施至关重要。

🔄 自动化

可以使用Make、Gradle、Ant或Maven等工具自动化构建，以便进行重复且可靠的软件构造。构建自动化对于保持软件开发中的效率和质量至关重要。

🔍 类型

存在不同类型的构建，包括开发构建、测试构建和生产构建，每种都在软件开发生命周期中服务于特定的目的。

👩‍💻 重要性

构建对于软件发布前的测试和调试至关重要，确保其质量和功能。它们允许开发者在软件向用户发布前识别和修复问题。

🔍 质量保证

测试构建对于质量保证（QA）团队特别重要，以确保软件满足所需的质量标准。

📈 持续集成

在持续集成（CI）过程中使用构建自动化工具有助于维护软件质量和可靠性，允许更快、更高效地交付更新和新功能。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Burndown Chart","question":"什么是燃尽图？","description":"它是随时间推移剩余工作量的视觉表示。","date":"2024-11-10","categories":["scrum","metric","progress tracking"],"published":true,"slug":"burndown-chart","content":"

📜 定义

燃尽图是一种视觉表示，显示随时间推移剩余的工作量，常用于Scrum中跟踪项目进度。

⏳ 时间与工作

该图表展示了待办工作量与完成它的可用时间之间的关系，帮助团队管理工作并满足既定的截止日期。图表的横轴代表时间，纵轴代表剩余的工作量。

🔄 迭代跟踪

图表在整个冲刺期间定期更新，以反映实际进展。

🎯 理想趋势

它包括代表理想进展的线，显示如果一切按计划进行，工作量应如何随时间减少。

📈 实际趋势

实际剩余工作与理想趋势进行对比，提供了完成计划范围的期望的清晰可视化。

🔧 绩效分析

该图表还用作评估团队绩效和识别改进领域的工具。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Burnup Chart","question":"什么是燃尽图？","description":"它是随时间推移完成工作量的视觉表示。","date":"2024-11-10","categories":["agile","scrum","metrics"],"published":true,"slug":"burnup-chart","content":"

📜 定义

燃尽图是一种视觉表示，显示随时间推移完成的工作量，描绘了项目范围或目标的累积进展。

🔍 解读

x轴代表时间，通常以冲刺或周为单位，而y轴代表完成的工作量，通常以故事点或其他相关指标表示。

🎯 目的

它被团队用来跟踪和预测进度，管理范围变更，并做出数据驱动的决策。

⬇️ 与燃尽图的对比

与燃尽图不同，燃尽图跟踪的是剩余工作而不是完成的工作，理想的范围线随时间减少。

🔄 Scrum

燃尽图是在敏捷框架如Scrum中常用的工具，用于监控和管理交付。

🔢 理想线

画一条直线来代表理想的范围，指示需要完成的总工作量。

♻️ 范围变更

图表更新以反映任何范围的变更，相应调整理想范围线。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Business Agility","question":"什么是商业敏捷性？","description":"它是组织适应和响应变化的能力。","date":"2024-11-10","categories":["business agility","adaptation","innovation","leadership","digital transformation"],"published":true,"slug":"business-agility","content":"

📜 定义

商业敏捷性，或称企业敏捷性，指的是组织以快速、连续和系统的方式适应和响应变化的能力，保持盈利并超越竞争对手。

🔄 适应

它涉及为客户创造和提供新价值，成功满足他们不断变化的需求，从而获得竞争优势。

📈 重要性

在当今数字时代，商业环境的快速和激烈变化要求组织必须具备灵活性和韧性，因此商业敏捷性至关重要。

🎯 以客户为中心

商业敏捷性涉及深入考虑客户需求和致力于为他们提供价值（客户中心性）。

📊 数据

认识到数据的重要性，并将其作为战略资产利用，是商业敏捷性的关键要素。

🌐 市场观察

持续监控市场以适应不断变化的条件和客户需求是必要的。

🔄 决策过程

实施敏捷的决策过程，持续评估商业机会和计划。

📈 项目组合调整

快速调整商业计划组合以满足组织目标是商业敏捷性的关键。

🛠️ 组织结构

调整组织结构以使其更加灵活和响应变化是这种方法的重要部分。

💼 领导重点

商业敏捷性强调在数字转型背景下的领导力以及敏捷性在现代商业中的重要性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Canary Release","question":"什么是金丝雀发布？","description":"这是一种用于最小化风险的部署策略。","date":"2024-11-10","categories":["release","DevOps","deployment","risks"],"published":true,"slug":"canary-release","content":"

🐤 定义

金丝雀发布是软件开发中用于减少引入新版本风险的部署策略，最初只向一小部分用户推出。

📅 起源

这个名称来源于矿工下煤矿时会带一只金丝雀在笼子里。如果有有毒气体泄漏进矿井，金丝雀会先于矿工死去。

🔍 监控

系统被仔细监控问题，如果新版本表现良好，它将逐步向更多用户发布。

🔄 回滚

如果检测到问题，可以回滚发布，并为所有用户恢复旧版本。

👥 选择

使用不同策略选择将哪些用户暴露于新版本，如随机抽样或基于人口统计的选择。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"CD","question":"什么是CD？","description":"代表持续部署。","date":"2024-11-10","categories":["release","deploy","DevOps","automation","alm","ci"],"published":true,"slug":"cd","content":"

🔄 定义

持续部署（CD），或持续交付，是一种软件工程方法，其中代码更改通过一系列自动化测试自动发布到生产环境。

🛠️ 流程

新的代码更改经过测试和检查流程，如果被批准，将直接部署到生产环境。

🚀 优势

持续部署加速了软件的交付，减少了新功能的上市时间，并允许更快的反馈周期。

🐞 纠正

频繁的部署有助于找到并修复bug，因为bug较新且更容易追踪。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"CFD","question":"什么是CFD？","description":"代表累积流程图。","date":"2024-11-10","categories":["kanban","CFD","metric","continuous improvement","kaizen"],"published":true,"slug":"cfd","content":"

📜 定义

累积流程图（CFD）是Kanban中使用的一种视觉工具，用于跟踪系统或团队的表现，显示随时间不同阶段的工作项流动。

🔍 目的

它提供了对工作流程的稳定性和效率的洞察，突出显示改进的领域并帮助识别瓶颈。

📈 元素

该图由代表工作流程不同阶段的带状区域组成，每个带状区域的宽度表示该阶段在任何给定时间的工作项数量。

🔄 CFD分析

可以分析CFD中的趋势，以了解交付时间、周期时间、在制品（WIP），并识别不规则现象或性能问题。

📏 轴线

水平轴代表时间，显示工作项通过工作流程的进展，而垂直轴度量工作项的数量，通常表示每个阶段的WIP。

🔄 前置时间

CFD可以用来分析前置时间，即工作项从开始到完成所需的时间。

🔄 周期时间

它还有助于理解周期时间，即完成单个工作项迭代所需的时间。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"CI","question":"CI是什么意思？","description":"代表持续集成。","date":"2024-11-10","categories":["development","CI","automation","quality","ALM","DevOps"],"published":true,"slug":"ci","content":"

📜 定义

持续集成（CI）是一种软件开发实践，开发者定期将代码更改合并到中央仓库中，随后进行自动构建和测试。它是DevOps哲学的核心实践。

🔨 自动化

CI包括文化组成部分，促进频繁集成，以及自动化组成部分。代码更改触发自动构建过程，以创建可执行软件。

🚀 目标

CI的主要目标是快速发现和修复错误，提高软件质量，以及减少验证和发布新软件更新所需的时间。

🔄 信心

频繁的集成生成对代码库始终处于功能状态的信心。

🔬 测试覆盖

CI应包括一套全面的自动化测试，以覆盖软件的不同方面并确保其QA级别。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"CI/CD","question":"什么是持续集成（CI）和持续部署（CD）？","description":"它们是软件开发中的关键实践，也是DevOps方法的核心支柱。","date":"2024-11-10","categories":["CI","CD","DevOps"],"published":true,"slug":"ci-cd","content":"

🔄 持续集成 (CI)

CI涉及频繁将代码更改集成到共享仓库中，并自动化测试以确保代码的可靠性。

📦 持续交付 (CD)

CD自动化代码更改的测试和交付过程，仅在自动部署到生产环境之前停止。

🔁 CI/CD流水线

流水线是一组连接的测试、过程和检查，包括CI、CD，由敏捷思维、DevOps方法和SRE实践支持。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"CoE","question":"什么是CoE？","description":"代表卓越中心。","date":"2024-11-10","categories":["agile","center of excellence","Kaizen"],"published":true,"slug":"coe","content":"

📜 定义

卓越中心（CoE）是组织内的一个战略单位，提供专业知识和专门技能，以促进和确保其学科实践的卓越。

🎯 目的

CoE的主要目的是推动最佳实践的采用、优化和治理。CoEs在影响组织文化向持续改进方向发展中发挥着关键作用。

🤝 合作

CoEs与团队合作，传播知识和最佳实践，旨在提高组织的质量和一致性。

👩‍🏫 服务

CoE的服务包括培训、流程创建、剧本和指导。

📝 治理框架

CoEs建立治理框架，以确保正确实施并遵守最佳实践。

📈 指标

通常，CoEs衡量其学科实践在组织内的正确性能并识别改进领域。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Commitment Point","question":"什么是承诺点？","description":"它是工作流中准备将工作项纳入系统的阶段。","date":"2024-11-10","categories":["kanban","commitment","efficiency","flow"],"published":true,"slug":"commitment-point","content":"

📜 定义

在Kanban中的承诺点是工作流中的一个阶段，工作项准备纳入系统并通过它流动，代表对工作和交付该项的承诺。

🔄 重要性

这是管理进行中工作和确保团队能够更可预测地释放其承诺工作的关键概念。

📊 视觉表示

承诺点通常在Kanban板上两列之间的划分线上可视化，以提供工作项状态的清晰度并帮助管理工作流。

🛠️ 效率

通过定义承诺点，团队可以避免过多项目负载并保持需求与能力之间的平衡。

📝 明确确认

承诺点需要团队明确确认一个工作项准备开始和交付。

🏉 Scrum

在Scrum中，Kanban承诺点的等效物是创建Sprint Backlog。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Community of Practice - CoP","question":"什么是实践社区？","description":"它是一群分享关注、一系列问题或对某个话题有热情的人。","date":"2024-11-10","categories":["CoP","learning","knowledge"],"published":true,"slug":"cop-comunidad-de-practicas","content":"

📜 定义

CoP（实践社区）是一群分享关注、一系列问题或对某个话题有热情的人，他们通过持续互动来加深该领域的知识和专业技能。

🔍 目的

实践社区的形成旨在促进学习、解决问题和在专业或组织环境中交流最佳实践。

👥 成员

实践社区通常由在特定领域内从事实践的成员组成，他们合作开发共享的资源、经验和工具库。

📚 起源

CoPs 的概念最初是由认知人类学家 Jean Lave 和教育理论家 Etienne Wenger 在1990年代提出的。

👩‍🏫 自然形成

实践社区通常在组织内部自然形成，因为有相似兴趣和挑战的从业者聚集在一起合作。

📅 进化

随着时间的推移，实践社区发展出自己的身份、实践和工作方式，往往成为组织知识管理的一个组成部分。

🔧 促进

一些组织通过提供资源、领导力和一个用于交流和合作的平台，积极支持实践社区的形成。

📈 实践

实践社区专注于在其领域内开发和分享最佳实践和实用知识。

📚 知识管理

实践社区在捕捉和传播组织内的隐性知识方面是有效的。

\n","language":"zh","alternativeLangs":["da","en","es","fi","fr","it","ja","ko","no","pl","pt","ru","sv","tr"]},{"title":"Cost of Delay","question":"什么是延迟成本？","description":"代表了延迟交付随时间造成的经济影响。","date":"2024-11-10","categories":["kanban","lean","SLA","metric","prioritization"],"published":true,"slug":"cost-of-delay","content":"

📜 定义

延迟成本（CoD）代表了产品或服务交付延迟的经济影响。

📊 重要性

它是精益管理和看板方法中用于优先排序工作、减少浪费和理解延迟影响的关键指标。

🎯 目的

提高对延迟的财务影响的认识。

🔢 计算

涉及估计交付每周将产生的收入，并将其除以项目持续时间。

➗ 技巧

CD3是一种帮助优先排序产品积压工作的技术。它通过将延迟成本除以项目持续时间来计算，以获得排序每个PBI（产品积压项目）的量级。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Crystal Method","question":"什么是Crystal Method？","description":"这是一个优先考虑人与人之间互动而非流程和工具的框架。","date":"2024-11-10","categories":["framework","agile"],"published":true,"slug":"crystal-method","content":"

🔍 定义

Crystal Method是一个项目管理框架，优先考虑人与人之间的互动而非流程和工具。

👨‍💻 创建者

Alistair Cockburn于1991年为IBM开发了Crystal方法，以应对对更灵活和适应性更强的项目管理方法的需求。

🌐 方法

Crystal是敏捷思维的一部分，强调适应性和团队合作。

📊 色彩编码

Crystal根据团队大小分为几个色彩编码的组，每个组都有自己的一套指南。

📜 特征

Crystal方法以人为本，适应性强，极简，要求最少的文档并强调灵活性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Customer Centricity","question":"什么是客户中心性？","description":"它是将客户置于中心。","date":"2024-11-10","categories":["strategy","ux","culture"],"published":true,"slug":"customer-centricity","content":"

📜 定义

客户中心性是一种商业策略，优先考虑将客户置于所有运营的中心，目的是提供积极的体验并建立长期关系。

📈 重要性

对企业至关重要，因为它可以增加客户忠诚度，提高留存率，最终实现更大的盈利能力。

📊 数据使用

这种方法的一个关键部分是使用客户可用性和参与数据来理解他们的行为和偏好。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","no","pl","pt","ru","tr"]},{"title":"Cycle Time","question":"什么是周期时间？","description":"它是在给定过程中完成一项任务所需的时间。","date":"2024-11-10","categories":["kanban","metrics","cycle time","delivery rate","throughput","lead time"],"published":true,"slug":"cycle-time","content":"

📜 定义

周期时间指的是一项任务从开始到结束经过生产或开发过程所需的时间。即从开始积极工作到准备交付的时间。

🆚 与前置时间的区别

周期时间与前置时间的主要区别在于测量的范围。

📅 测量

通过记录每个项目在看板上进展的开始和结束日期及时间来测量周期时间。

🔢 计算

周期时间的计算公式是（完成日期 - 开始日期）+ 1，以考虑在同一天开始和完成的项目。

🎯 改进

改善周期时间的策略包括限制进行中的工作和解决瓶颈问题。

📈 平均周期时间

团队可以使用历史数据来计算他们过程的平均周期时间，帮助未来预测。

📈 绩效分析

定期分析周期时间数据可以帮助识别改进领域并验证变更的有效性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Disciplined Agile Delivery - DAD","question":"什么是规范敏捷交付？","description":"它是一种灵活应用敏捷的方法。","date":"2024-11-10","categories":["agile","disciplined agile delivery","PMI","scaling"],"published":true,"slug":"dad---disciplined-agile-delivery","content":"

📜 定义

规范敏捷交付（DAD）是一个工具包，提供了一种在组织内灵活应用敏捷的方法。

📅 起源

Scott Ambler 和 Mark Lines 是规范敏捷交付的共同创造者。

🔄 演变

最初被称为DAD，它已发展成为规范敏捷（DA），现在被视为一个工具包而非一个框架。

🔧 灵活性

它旨在做到不可知论和务实，允许组织根据其特定情况选择最佳工具和方法。

📚 集成

集成了各种框架如Scrum、Kanban、XP、DevOps和SAFe，同时提供指导如何适应和有效使用这些实践。

📈 由PMI收购

项目管理协会（PMI）在2019年收购了规范敏捷，旨在增强和推广其使用。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"DDD","question":"什么是DDD？","description":"它代表领域驱动设计。","date":"2024-11-10","categories":["DDD","TDD","BDD"],"published":true,"slug":"ddd---domain-driven-design","content":"

📜 定义

领域驱动设计（DDD）是一种软件开发方法，专注于创建满足业务需求的高质量软件。

🎯 主要焦点

DDD强调将项目的主要焦点放在业务领域的核心逻辑和概念上。

🤝 合作

DDD促进技术专家和领域专家之间的创造性合作，以确保模型准确反映业务。

📚 参考资料

模型为业务和技术团队提供参考，使用共同的“普遍语言”来描述概念。

🗂️ 模型工件

模型由各种工件组成，如图表、文档和原型，这些都代表了业务领域。

🔄 同步

模型和软件设计必须保持同步，设计中的任何更改都需针对模型进行验证。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Delivery","question":"什么是Delivery？","description":"它是软件的交付。","date":"2024-11-10","categories":["development","alm"],"published":true,"slug":"delivery","content":"

🔄 定义

Delivery指的是团队交付软件的行为。

🎯 关注价值

对于敏捷思维，频繁且早期交付有价值的软件至关重要，以获得即时反馈，利用适应性作为竞争优势。

📈 指标

一些用于衡量团队交付能力的指标包括：领先时间（Lead Time）、周期时间（Cycle Time）和吞吐量（Throughput）。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Design Sprint","question":"什么是Design Sprint？","description":"它是一个在短短五天内允许创建和测试原型的过程。","date":"2024-11-10","categories":["MVP","Product","innovation","Agile","Prototype","design sprint","validation"],"published":true,"slug":"design-sprint","content":"

🚀 定义

Design Sprint 是一个敏捷的产品开发过程，允许在短短五天内创建和测试一个原型。

🔍 起源

Design Sprint 由 Jake Knapp 及其在 Google Ventures 的同事们开发。其起源可追溯到加速初创企业和产品开发团队内部的设计和验证想法的努力。

🗓️ 时间表

该过程通常分为五个关键阶段，每个阶段对应一个工作日。

👩‍💻 团队

需要一个小型的跨功能团队来参与项目，其中包括像引导者和决策者这样的关键角色。

📅 周一 — 理解和规划

定义产品目标并设定现实的目标。

🖊️ 周二 — 绘图

通过个人和团体绘图会议生成各种解决方案和想法。

🔍 周三 — 决策

评估并选择最佳的想法进行跟进，为选定的解决方案创建故事板。

🛠️ 周四 — 原型制作

构建一个高质量的原型，可以用于与用户进行测试。

🧪 周五 — 测试

在真实用户面前展示原型，收集反馈并验证概念。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Design Thinking","question":"什么是Design Thinking？","description":"它是一个解决问题的过程，专注于理解人类需求并创造创新解决方案。","date":"2024-11-10","categories":["process","design thinking","innovation"],"published":true,"slug":"design-thinking","content":"

🎨 定义

Design Thinking 是一个解决问题的过程，专注于理解人类需求并创造创新解决方案，这些解决方案是与客户中心对齐开发的。

📚 起源

Design Thinking 起源于斯坦福大学的d.school，John E. Arnold和Herbert Simon的早期作品。

💡 概念化

该过程包括一个头脑风暴阶段和想法生成，以探索广泛的可能性。

🏗️ 原型制作

迅速将想法转化为可测试和改进的具体原型。

📊 测试和反馈

原型与用户进行测试，以收集反馈并迭代设计。

📈 商业影响

Design Thinking 不仅用于产品设计，还用于商业模式的创新和组织变革。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Developers","question":"什么是Developer？","description":"他们负责编写代码以创建、设计和维护软件应用程序。","date":"2024-11-10","categories":["development","scrum","role"],"published":true,"slug":"developer","content":"

💻 定义

Developer，也称为软件开发者，是编写代码以创建、设计和维护软件应用程序、网站或各种设备的游戏的专家。

📱 重要性

在数字时代，Developer的技能需求很高，因为市场的快速数字化和对创新数字解决方案的需求。

🥷 技能

他们需要在编程语言、设计技术方面的高级知识，并且能够在复杂的技术项目上工作。

👨‍💻 Scrum

在Scrum中，Developer是团队成员，负责创建、设计、实施和交付软件产品。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"DevOps","question":"什么是DevOps？","description":"它是英文词“development”和“operations”的结合。","date":"2024-11-10","categories":["DevOps","agile","development","operations","CI","CD"],"published":true,"slug":"devops","content":"

🛠️ 定义

DevOps是一种软件开发哲学，侧重于软件开发者和IT运营专业人员之间的沟通、协作和整合。

🌐 起源

DevOps这个词最初在2009年由John Allspaw和Paul Hammond在O'Reilly Velocity 09活动中的演讲“每天10次部署”中提出，但这个运动实际上始于2007年，当时独立顾问Patrick Debois经历了开发和运营团队之间的冲突。

📈 进化

DevOps已经演变为包括持续交付和持续部署等实践，旨在提高软件的质量、速度和盈利能力。

🤝 跨功能协作

DevOps需要向传统上独立的开发和运营团队之间的协作和整合转变的文化变革。

🔁 持续集成

持续集成（CI）是DevOps中的一个关键实践，涉及在共享仓库中自动更新代码。其目标是快速发现并修复错误，提高软件质量，加速交付时间。

🚀 持续部署

DevOps范式的另一进化是持续部署（CD），代码变更会自动发布到生产环境中。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Discovery","question":"什么是Discovery？","description":"它是确定要构建哪种产品或服务的过程。","date":"2024-11-10","categories":["innovation","agile","upstream","product","product backlog"],"published":true,"slug":"discovery","content":"

🔍 定义

Discovery是确定要构建哪种产品或服务的过程，侧重于验证用户需求并识别风险和机会。

🔄 敏捷

Discovery常与敏捷方法论一起使用，以确保有效地构建正确的产品。

👥 团队合作

它涉及一个跨功能团队共同努力，理解用户环境和挑战，创造创新且有价值的解决方案。

📈 持续过程

Discovery不是一次性活动，而是一个持续的过程，帮助缓解风险并做出明智的决策。

🔄 双轨方法

Discovery可以在双轨方法中使用，与敏捷实践如Scrum整合，确保开发的产品符合用户需求。

📅 初始阶段

它通常在产品开发生命周期的早期阶段进行，允许在投入大量资源之前验证产品想法。

🛠 精益方法论

Discovery经常利用精益方法论快速测试和迭代想法，与敏捷开发的迭代性质保持一致。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"DoD - Definition of Done","question":"什么是完成的定义（DoD）？","description":"它是一组确定用户故事何时完成的标准。","date":"2024-11-10","categories":["scrum","user story","quality","agile"],"published":true,"slug":"dod-definition-of-done","content":"

🎯 定义

完成的定义（DoD）是一组在Scrum框架内确定用户故事何时被视为完成的标准。

🛠️ 重要性

它确保所有工作按照团队的一致标准完成，并且已准备好发布，提供透明度并确保质量。

🤝 创建

如果组织没有定义好的DoD，开发人员有责任创建它。

📈 测量

允许对完成的工作进行客观评估，并帮助管理团队能力和期望。

📋 可见的标准

DoD通常记录为清单或标准列表，对整个团队可见，并可在整个冲刺过程中参考。

🌱 进化

DoD是一个活动元素，随着学习的增加应该不断改进和扩展。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"DoR - Definition of Ready","question":"什么是就绪的定义（DoR）？","description":"它是一组定义项目在开发前必须满足的要求的标准。","date":"2024-11-10","categories":["scrum","agreement","antipattern","DoD"],"published":true,"slug":"dor-definition-of-ready","content":"

🔍 定义

就绪的定义（DoR）是产品负责人和Scrum中的开发者共同商定的一组标准，这些标准概述了产品待办事项在被选入冲刺待办列表之前必须满足的要求。

📝 就绪标准

DoR确保项目足够精细、易于理解且可行实施，减少在冲刺计划期间出现延迟和误解的风险。

📝 非Scrum组成部分

虽然DoR不是Scrum框架的正式部分，但在某些情况下，它作为一种协作工具，促进产品负责人和开发团队之间的沟通和共识。

🚫 反模式

DoR被视为一个反模式，因为它违背了Scrum中的经验主义原则，阻碍了团队遵循经验过程控制的能力，并可能成为团队沟通和自主的障碍。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Downstream","question":"什么是下游？","description":"从接收请求到交付的活动。","date":"2024-11-10","categories":["lean","kanban","agile","upstream","cycle time","lead time"],"published":true,"slug":"downstream","content":"

⬇️ 下游

指的是在敏捷和精益哲学中，从接收请求到为客户完成服务的活动。

🔄 上游

相比之下，上游涉及实际执行之前的所有活动，例如产品发现或产品积压定义。

🔀 看板

使用下游概念来管理工作流程，专注于可视化和优化整个过程。

📈 指标

用于观察上游效率的一些指标包括领先时间和周期时间。

📦 敏捷开发

尽管未明确提及，Scrum 也通过产品负责人管理产品积压来暗示上游活动。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"DRY","question":"DRY 是什么意思？","description":"DRY 代表不要重复自己。","date":"2024-11-10","categories":["DRY","development","principles","maintainability","scalability"],"published":true,"slug":"dry---dont-repeat-yourself","content":"

📚 原则定义

DRY 代表“不要重复自己”，它是一种软件开发原则，强调减少重复模式和重复代码，支持模块化和可引用代码。

👨‍💻 起源

由 Andy Hunt 和 Dave Thomas 在《务实的程序员》中提出，DRY 旨在确保系统中每一块知识都有一个单一、明确的表述。

⚙️ 重要性

编写 DRY 代码对于可维护性、可扩展性至关重要，以避免相反的 WET 代码（“重复编写一切”）。

🔍 三次规则

一个关于 DRY 代码的好的通用规则是“三次规则”，它建议在遇到某种模式第三次时将代码抽象成一个可重用的单元。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Dual Track","question":"什么是双轨？","description":"它是一种将产品发现与同时交付结合起来的方法。","date":"2024-11-10","categories":["discovery","delivery","upstream","downstream","scrum","agile"],"published":true,"slug":"dual-track","content":"

🔍 定义

一个将敏捷的迭代和灵活性结合的项目管理方法，通过分离上游和下游活动。

🔄 起源

双轨概念最初在2005年由 Lynn Miller 提出，后由 Desirée Sy 在2007年进一步阐述，并由 Marty Cagan 和 Jeff Patton 在2012年正式命名为“双轨敏捷”。

👁️ 发现

在上游阶段，团队的一部分成员，通常包括产品负责人和具有用户体验 (UX) 角色的团队成员，专注于理解用户需求、原型制作和解决方案测试，然后继续进行开发。

🚀 执行

在下游，开发人员将发现阶段的想法实现为产品增量。

🤝 同步

两个轨道并行工作，旨在同步他们的努力，确保一个可持续和高效的工作流程。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Engineer Manager","question":"什么是工程经理？","description":"他们是经验丰富的工程师，负责领导技术活动和管理工程师团队。","date":"2024-11-10","categories":["collaboration","leadership"],"published":true,"slug":"engineer-manager","content":"

👩‍💼 角色定义

工程经理是一位经验丰富的工程师，负责领导技术活动和管理开发者团队。

🔧 技术领导

他们负责进行基于数据的技术决策，并监督技术和设计操作的执行。

👥 团队管理

除了技术任务外，他们还监督并指导多个工程团队，确保项目高效且按计划完成。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Expedite","question":"什么是加急？","description":"这些是需要立即处理的高优先级工作项。","date":"2024-11-10","categories":["kanban","urgency"],"published":true,"slug":"expedite","content":"

⏱️ 定义

在看板中，加急指的是由于紧急性需要立即注意的工作项，通常会打断正常的工作流程。

🚀 看板

团队可以在他们的看板上使用一个加急通道来视觉上分离和优先处理紧急工作项，允许这些工作项在常规流程限制之外被处理。

📈 影响

过多的紧急项可能会负面影响团队的交付能力。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Extreme Programming - XP","question":"什么是极限编程？","description":"它是一个敏捷软件开发框架，注重频繁的反馈和持续的改进。","date":"2024-11-10","categories":["downstream","agile","kaizen","tdd"],"published":true,"slug":"extreme-programming---xp","content":"

🔍 定义

极限编程或XP是一个敏捷软件开发框架，注重频繁的反馈和持续的改进，涉及如成对编程和集体代码所有权等实践。

📅 起源

极限编程（XP）是由敏捷宣言的推动者和签署者肯特·贝克在1990年代为应对紧迫的软件项目挑战而开发的。贝克在1999年出版的《极限编程解释：拥抱变化》一书中介绍了XP，这是一个专注于持续改进、适应性和团队合作的敏捷框架。

📈 质量

XP旨在通过测试和简化交付高质量软件。

🔍 简洁性

XP倡导采用有效的最简单解决方案，避免不必要的技术复杂性。

💎 勇气

鼓励团队成员冒险并在无恐惧的情况下进行必要的更改。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"FDD","question":"什么是FDD？","description":"FDD代表特性驱动开发。","date":"2024-11-10","categories":["FDD","BDD","DDD","TDD","feature"],"published":true,"slug":"fdd---feature-driven-development","content":"

🔍 定义

特性驱动开发，或者说以特性为指导的开发，是一种敏捷软件开发方法，关注于客户价值特性，强调短迭代和频繁发布。

🎯 关键原则

FDD要求每2-10天交付一个特性，确保不断满足客户需求。

🔄 迭代过程

FDD包括五个关键过程，包括创建特性列表、规划、设计和构建，所有这些都在以客户为中心的框架内进行。

🛠️ 团队角色

FDD定义了特定角色，如主架构师、主程序员、领域专家、开发经理、部署者技术作家、领域管理者、语言大师、测试员以及其他支持角色，强调个人和团队在特性开发中的责任。

🔀 与Scrum的区别

FDD以特性为中心，而Scrum则专注于交付产品增量。

📈 客户参与

FDD需要客户的积极参与。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Features","question":"什么是特性？","description":"它是一种提供价值的独特功能部分。","date":"2024-11-10","categories":["agile","mvp","scrum","product backlog","FDD","feature flag"],"published":true,"slug":"feature","content":"

🔍 定义

特性或特征是提供用户价值的功能部分。它是可以细分为更小用户故事的高级需求。

📈 重要性

特性有助于组织和优先处理开发工作，允许团队专注于交付具体的功能价值。

👨‍💼 所有权

产品负责人通常负责在产品积压中定义、管理和排序特性。

🔄 关系

特性通常由多个用户故事组成，这些用户故事是敏捷开发中更细粒度的工作单位。

🚀 发布

产品负责人负责根据业务价值和客户需求决定每次发布中包括哪些特性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Feature Flags","question":"什么是功能标志？","description":"这是一种允许启用或禁用功能的技术。","date":"2024-11-10","categories":["development","CI","CD","A/B Testing"],"published":true,"slug":"feature-flag","content":"

🚩 定义

功能标志，也称为功能开关，是一种技术，允许开发人员在不改变代码库的情况下启用或禁用某些功能。

🔧 实施

它们可以使用配置文件中的布尔值来实现，这些布尔值被条件检查以确定是否应显示和激活功能。

🎯 用例

它们在持续部署（CD）方法、金丝雀发布、A/B测试中使用，并管理不同用户群体的功能可见性。

💡 优势

功能标志允许更安全、更有效的开发，使团队能够部署和测试新功能，而不影响所有用户基础。

📈 发展

随着敏捷、DevOps和软件开发中持续交付实践的兴起，功能标志的使用日益普及。

📝 配置

它们可以使用Bullet Train或Launch Darkly之类的服务来定义，创建一个自定义后端服务，或使用应用程序内的本地文件。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Feedback","question":"什么是反馈？","description":"反馈是对某种刺激的响应，用作评估方式。","date":"2024-11-10","categories":["feedback","communication"],"published":true,"slug":"feedback","content":"

🔊 定义

反馈是对某种刺激的响应，用作评估方式。

♻️ 与敏捷的关系

敏捷提倡尽早获取反馈，通过适应变化利用它作为竞争优势。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Fibonacci Sequence","question":"什么是斐波那契数列？","description":"它是自然数的无限序列。","date":"2024-11-10","categories":["estimation","effort","complexity","planning poker"],"published":true,"slug":"fibonacci","content":"

🔢 定义

斐波那契数列是一个自然数的无限序列，每一项是前两项的和，起始数字为0和1或1和1。

🌿 自然界的设计

该数列在自然现象中可见，如贝壳的螺旋图案和植物上叶子的排列。

🎯 敏捷估算

斐波那契数列常用于敏捷技术中估算工作量和复杂度，如计划扑克。

🧮 示例

0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89...

💻 应用

它在计算、博弈论领域具有实际应用，并作为分析金融市场的工具使用。

📏 黄金比例

连续斐波那契数的比率接近黄金比例，这是一个通常与审美美感相关的数学概念。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Figma","question":"什么是Figma？","description":"它是一个图形设计和原型制作工具。","date":"2024-11-10","categories":["collaboration","design","UX","UI"],"published":true,"slug":"figma","content":"

🎨 设计工具

Figma是一个广泛用于用户界面（UI）设计和开发的图形设计和原型制作工具。

🤝 协作

Figma支持实时协作工作，使团队成员可以共同工作。

💻 可用性

Figma以其直观和用户友好的界面而闻名，受到UX/UI设计师和设计机构的欢迎，用于创建原型和模型。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"FOMO","question":"什么是FOMO？","description":"它代表错失恐惧症。","date":"2024-11-10","categories":["psychology","product","innovation"],"published":true,"slug":"fomo","content":"

🔍 定义

'FOMO'代表'错失恐惧症'，是一种心理状态，特征是不断希望通过社交媒体等方式与他人的活动保持联系。

😟 后果

这种状态可能导致焦虑、抑郁和睡眠障碍，因为个体觉得必须不断检查更新和互动。

📚 起源

FOMO一词最初在90年代末使用，最初指的是害怕错过社交计划的恐惧。

🌐 演变

随着社交媒体和数字连通性的兴起，FOMO已演变成一种更广泛的焦虑，与感觉被排除在他人经历之外有关。

👥 社交联系

FOMO现在被理解为一种社交焦虑形式，个体寻求持续的联系以避免感到被排斥。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Forecast","question":"什么是预测？","description":"它是对未来销售的估计和跟踪。","date":"2024-11-10","categories":["metrics","forecast","predictability"],"published":true,"slug":"forecast","content":"

📈 定义

预测是对产品未来销售的估计和跟踪，通常使用历史销售数据和销售及市场团队的输入。

🔍 目的

预测短期和中期销售，早期发现问题，快速找到解决方案，减少库存，并提高客户服务。

📊 方法

可以使用定量和定性数据进行预测。

📊 定量数据

使用历史销售数据作为预测未来销售的基础，但不保证未来表现。

🧮 定性数据

依靠公司内部的主观评估，如来自销售和市场团队的评估，以通报预测。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Framework","question":"什么是框架？","description":"它是用于规划、同意或决策的一套规则、思想或信仰体系。","date":"2024-11-10","categories":["scrum","agreements","team","shared understanding"],"published":true,"slug":"framework","content":"

🏗️ 含义

框架，或工作框架，是围绕某事物可以构建的支持结构，或用于规划或决策的一套规则、思想或信仰体系。

💻 背景

在计算机系统中，框架是一个实际或概念结构，旨在作为软件应用构建的支持或指导。

📚 概念结构

框架可以是一套基本的概念结构思想或用于规划的规则集。

📝 示例

Scrum 是一个敏捷框架，Laravel 是 PHP 编程语言的一个框架。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"FYI","question":"FYI 是什么意思？","description":"它代表为您的信息。","date":"2024-11-10","categories":["communication","acronyms"],"published":true,"slug":"fyi","content":"

📝 FYI

为您的信息，或 para tu información，是在专业和非正式沟通中常用的缩写，用以指示信息与接收者相关。

🗨️ 使用

它通常用来作为消息或主题行的前缀，以表明内容是为了接收者的知识提供的。

📧 邮件

在电子邮件通信中，FYI 常包含在主题行或邮件正文中，以指示内容是提供信息的，不需要回复。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Gemba","question":"什么是Gemba？","description":"它是一个日本术语，指的是“真实的地方”或“行动发生的地方”。","date":"2024-11-10","categories":["gemba","lean","kaizen"],"published":true,"slug":"gemba","content":"

🏭 定义

Gemba 是一个日本术语，指的是商业环境中的“真实的地方”或“行动发生的地方”。

💼 应用

在商业中，Gemba 是创造价值的地方，例如工厂中的操作员位置或零售环境中的销售区域。

🔄 精益管理

在精益管理中，Gemba 是持续改进努力的焦点，认为问题最好在发生地解决。

📈 与改善的联系

Gemba 与改善（Kaizen）概念密切相关，后者是持续改进的哲学。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Gherkin","question":"什么是Gherkin？","description":"Gherkin是一种用于以非技术利益相关者易于理解的方式指定软件系统行为的语言。","date":"2024-11-10","categories":["gherkin","behavior-driven development (BDD)","test automation"],"published":true,"slug":"gherking---given-when-then","content":"

📝 定义

Gherkin是一种语言，用于以非技术利益相关者容易理解的方式指定软件系统的行为。

🧪 测试方法

它特别与行为驱动开发（BDD）相关，并用于设计测试案例。

➡️ 语法

Gherkin具有特定的语法，使用关键词如Feature（特性）、Scenario（场景）、Given（假设）、When（当）、和Then（那么），用于结构化测试描述。

🔄 自动化

Gherkin经常与如Cucumber等工具一起用于测试自动化。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Git","question":"什么是Git？","description":"它是一个分布式版本控制系统。","date":"2024-11-10","categories":["git","development","ALM"],"published":true,"slug":"git","content":"

🔄 定义

Git 是一个分布式版本控制系统，允许有效跟踪文件变更，特别是在软件开发中。

🔗 仓库

每个开发者的项目本地副本是一个完整的仓库，允许离线工作并促进远程合作。

🔀 合并

Git 提供了合并不同分支、解决冲突并维护干净的仓库历史的工具。

🌐 灵活性

Git 的设计支持非线性开发，具有强大的分支和合并能力。

🔒 数据完整性

Git 使用密码哈希来确保存储数据的完整性，使数据难以被更改或丢失。

📈 流行度

Git 已成为全球版本控制的标准，广泛用于开源和商业软件项目。

📝 提交

Git 通过每次保存创建所有文件的快照，称为提交，形成开发历史的图谱。

🌿 分支

开发者可以在不同的分支上工作，然后将其工作合并回项目的主分支。

🔍 回退

可以将代码回退到以前的提交，检查文件中的更改，并审查如何何时何地进行的更改信息。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"GitFlow","question":"GitFlow是什么意思？","description":"它是Git的一个分支模型。","date":"2024-11-10","categories":["gitflow","git","branches"],"published":true,"slug":"gitflow","content":"

🔄 GitFlow

GitFlow是Git的一个分支模型，帮助管理项目分支和发布。

🚀 起源

GitFlow由Vincent Driessen开发，已成为软件开发中广泛采用的工作流程。

🔗 分支组织

分支被组织为主分支（例如'main'）和开发分支（例如'develop'），以及特性分支、发布分支和热修复。

🔄 初始提案

最初提出作为一个分支模型，GitFlow已演变成一个支持具体命令的工具。

📜 改进和适应

随着时间的推移，开发团队已经对GitFlow进行了改进和调整，以满足他们特定的需求和工作流程。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"GitHub","question":"什么是GitHub？","description":"它是一个托管和管理代码的平台。","date":"2024-11-10","categories":["github","git","gitflow","collaboration","development","version control"],"published":true,"slug":"github","content":"

🖥️ 定义

GitHub是一个为开发者提供托管和管理代码的平台，提供公共和私有仓库。

🤝 合作

它提供协作开发工具，允许多个用户在同一代码库上工作。

🔍 版本控制

GitHub使用Git，一个版本控制系统，来跟踪代码变更和管理项目的不同版本。

💻 服务

GitHub提供额外服务，如问题跟踪、代码审查和软件管理工具。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Hype","question":"什么是Hype？","description":"它是对新事物的强烈期待。","date":"2024-11-10","categories":["hype","marketing","product"],"published":true,"slug":"hype","content":"

🔊 Hype

Hype指的是过度或夸大的兴奋，常在营销中使用，公众对某个功能、产品或新奇事物的宣传。

📈 示例

一个被大量炒作的产品可能会夸大其功能或优点，以产生兴趣和销售。

📚 起源

这个词来源于英语词“hyperbole”，是一种文学上的夸张或过分赞美某物的手法。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Impact Map","question":"什么是影响图？","description":"它是一种用于聚焦目标及如何实现这些目标的技术。","date":"2024-11-10","categories":["impact mapping","design thinking","strategy","product","roadmap"],"published":true,"slug":"impact-mapping","content":"

🎯 定义

影响图是一种视觉技术，帮助团队聚焦他们想要实现的目标及实现方式。

🔄 迭代过程

它通常在开发的早期阶段应用，以创建战略计划和产品路线图。

🧠 协作工具

影响图涉及所有利益相关者的协作讨论，优先考虑将产生最大影响的行动。

📈 四个层级

这项技术围绕四个层级构建——目标、参与者、影响和交付物——来映射“为什么”、“谁”、“如何”和“什么”之间的联系。

🎯 目标

影响图的第一步是定义总体目标，确保它具体、可测量、可行、现实和有时间限制（SMART）。

👥 参与者

确定可以影响项目成功的关键参与者或利益相关者，避免使用像“用户”这样的通用术语，具体到用户类别或角色。

💥 影响

确定已识别参与者如何帮助实现项目目标及将有助于成功的具体影响。

📦 交付物

列出需要开发的高级功能或特征，可以作为初始产品路线图。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Ishikawa","question":"什么是石川图？","description":"它是用来识别事件或问题可能原因的工具。","date":"2024-11-10","categories":["Ishikawa diagram","kaizen","retrospective","post-mortem"],"published":true,"slug":"ishikawa","content":"

📊 定义

石川图，也称为鱼骨图，是一种常用于事后分析或回顾会议中的可视化工具，用于识别和分类特定事件或问题的可能根本原因。

🐟 起源

该图以其创造者石川馨的名字命名，因其类似鱼的骨架而被称为鱼骨图。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Jira","question":"什么是Jira？","description":"它是一个项目管理应用程序。","date":"2024-11-10","categories":["jira","tool","project"],"published":true,"slug":"jira","content":"

🔍 定义

Jira是由Atlassian开发的专有软件应用程序，用于问题跟踪和项目管理。

📈 目的

它被团队用来计划、跟踪和支持软件，提供整个开发生命周期的单一真理来源。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Junior","question":"什么是初级开发者？","description":"他是对语言和技术栈有一定了解的开发者。","date":"2024-11-10","categories":["senior","junior","developer","role"],"published":true,"slug":"junior","content":"

👨‍💻 角色定义

初级开发者通常拥有0到3年的经验，对使用的语言和技术栈有一定了解。然而，经验年数并不决定开发者的专业水平。

💼 职责

初级开发者经常在更有经验或高级团队成员的指导下，处理较小、较不关键的任务。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"JIT - Just In Time","question":"什么是及时制？","description":"它是一种旨在将原材料订单与生产计划对齐的策略。","date":"2024-11-10","categories":["toyota","lean","jit"],"published":true,"slug":"just-in-time---jit","content":"

⏱️ 定义

及时制（JIT），或及时生产，是一种管理策略，旨在将原材料订单与生产计划对齐，尽可能在需要时收到货物。

🏭 起源

及时制由日本汽车制造商丰田在1970年代作为其丰田生产系统的一部分开发。

💰 益处

及时制减少了存储大量库存的需求，带来效率和成本节约，但在供应或需求冲击时可能带来风险。

🔄 过程

及时制需要不断监控需求，并使用如看板等方法促进在简化、效率和质量上的持续改进。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Kaizen","question":"Kaizen 是什么？","description":"它意味着良好的变化或改进。","date":"2024-11-10","categories":["kaizen","continuous improvement","toyota","lean"],"published":true,"slug":"kaizen","content":"

📈 定义

Kaizen 是一个日本词，意味着“良好的变化”或“改进”，它是一个专注于持续改进的商业哲学。

🏭 起源

Kaizen 在战后的日本发展，受到了美国关于质量管理的教导的影响，并显著地由 Toyota 实施。

🔄 方法论

Kaizen 涉及所有员工在公司各个领域的逐步持续改进，旨在消除浪费和改善流程。

🔧 工具

Kaizen 哲学利用各种工具，如 5S 用于工作场所的组织，JIT 和 Kanban 用于库存控制，以及价值流程图用于消除浪费。

📚 扩展

管理咨询顾问 Masaaki Imai 在 1986 年通过他的书《Kaizen：日本竞争成功的关键》将 Kaizen 推向全球。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Kanban","question":"Kanban 是什么？","description":"它是一个用来优化工作流程的 Lean 方法。","date":"2024-11-10","categories":["kanban","agile","lean","services","pull system","flow","wip","kaizen"],"published":true,"slug":"kanban","content":"

📊 定义

Kanban 是一个用来优化工作流程的 Lean 方法。

🔄 方法

Kanban 通过持续改善工作流程，识别和解决工作流程中的问题，提倡 Kaizen 哲学。

🔒 限制在制品

Kanban 的关键实践之一是限制在制品 (WIP)，以提高团队的专注和效率，减少领先时间，并提高交付工作的质量。

🔄 拉动系统

Kanban 的拉动系统鼓励在开始新任务之前完成任务，专注于实际的容量和需求。这种方法通过确保一个工作完成后再接受另一个工作，从右到左简化工作流管理，改善价值交付和效率。

🛠 工具

实施 Kanban 方法最流行的一些数字工具包括：Trello、Asana 和 JIRA。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Kanban Board","question":"什么是看板板？","description":"使用卡片和列在过程的不同阶段视觉上表示工作。","date":"2024-11-10","categories":["Kanban","Lean","Information Radiator"],"published":true,"slug":"kanban-board","content":"

📊 定义

Kanban Board，或者说看板板，是一个工具，使用卡片和列在过程的不同阶段视觉上表示工作。

🔢 WIP 限制

它旨在通过设置在制品（WIP）的限制来帮助团队最大化效率。

👥 团队协调

看板板通过提供一个清晰的工作视图，需要完成的工作，任何阻碍或障碍，以及正在进行或已完成的工作，帮助协调团队。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"KISS","question":"KISS 是什么意思？","description":"它是 Keep It Simple, Stupid 的缩写！","date":"2024-11-10","categories":["KISS","design principle"],"published":true,"slug":"kiss---keep-it-simply-stupid","content":"

🔤 含义

KISS 原则，即 Keep It Simple, Stupid 的缩写，是一个作为设计原则使用的缩写。

🛠️ 设计原则

它主张在系统的设计和开发中保持简单。

📅 起源

它归功于 1960 年美国海军的工程师 Kelly Johnson。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"KPI","question":"KPI 是什么意思？","description":"它代表关键绩效指标。","date":"2024-11-10","categories":["KPI","metric"],"published":true,"slug":"kpi---key-performance-indicator","content":"

🎯 定义

Key Performance Indicator (KPI)，或关键绩效指标，是一种用于特定目标的绩效随时间的量化度量，用于跟踪目标的进展。

🔑 重要性

KPIs 对于团队的对齐、提供业务指标和增加组织内的透明度至关重要。

💼 示例

根据具体的商业目标，KPIs 可以包括收入增长、客户保留率、按地区销售等指标。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Lead Time","question":"Lead Time 是什么？","description":"它是从订单开始到完成的总时长。","date":"2024-11-10","categories":["lean","kanban","cycle Time","metric"],"published":true,"slug":"lead-time","content":"

⏳ 定义

Lead Time，或交付时间，是从订单开始到完成的总时长，常用于衡量操作的效率。

📅 公式

Lead Time = 交货日期 - 订单日期

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Lean","question":"Lean 是什么？","description":"Lean 是将制造原则应用于软件开发的方法。","date":"2024-11-10","categories":["lean","kanban","agile"],"published":true,"slug":"lean","content":"

🔍 定义

Lean 是将制造原则应用于产品和服务的开发和管理的方法。

🎯 目标

最大化对客户和用户的价值提供，同时减少成本和浪费。

🔃 拉动系统

使用拉动系统，由客户请求启动服务，减少过量生产和浪费。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Lean Inception","question":"什么是 Lean Inception？","description":"它是一个协作研讨会，旨在围绕构建最小可行产品达成一致。","date":"2024-11-10","categories":["lean inception","lean","design thinking","mvp"],"published":true,"slug":"lean-inception","content":"

🚀 目的

Lean Inception 是一个旨在围绕开发最小可行产品 (MVP) 在协作研讨会中通过共享理解来使团队达成一致的方法。

🏢 创造者

Lean Inception 由 Paulo Caroli 引入，首次出版日期为 2011 年。

📅 持续时间

Lean Inception 研讨会通常持续一周，专注于快速定义 MVP 并制定其启动计划。

🔄 演变

Lean Inception 经历了各种修改和调整，包括如何为分布式团队远程进行。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"LeSS","question":"LeSS 是什么意思？","description":"它代表大规模敏捷开发。","date":"2024-11-10","categories":["LeSS","scaling","scrum"],"published":true,"slug":"less-large-scale-scrum","content":"

🔍 定义

Large Scale Scrum (LeSS) 是一个用于扩展 Scrum 框架至多个团队同时在同一产品上工作的框架。

🎯 目的

LeSS 旨在尽可能简单地在大型企业环境中应用 Scrum 的原则和实践，保持对价值交付的关注并减少复杂性。

📜 关键原则

LeSS 受 10 个原则的指导，包括实证过程控制、透明度、客户关注和持续改进。

🔄 扩展

LeSS 提供两种配置 - 基本的 LeSS 适用于两到八个团队，LeSS Huge 适用于超过八个团队，为不同组织规模提供可扩展的方法。

👥 团队

LeSS 强调每个团队都应该是跨功能的并高度自我管理。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Management 3.0","question":"什么是 Management 3.0？","description":"它是一种关注组织系统观的领导和管理方法。","date":"2024-11-10","categories":["management 3.0","leadership","continuous improvement"],"published":true,"slug":"management-3-0","content":"

🎯 定义

Management 3.0 是一种领导和管理方法，关注组织的系统观，强调集体对员工绩效和幸福的责任。

🔄 思维方式

它被描述为一种思维方式而不是方法或框架，拥有一套不断发展的工具、游戏和实践，以帮助管理组织。

👥 协作领导

Management 3.0 提倡一种领导模式，管理是一个团队责任，旨在创造一个高效且优先考虑员工幸福的工作环境。

🔧 实际应用

该方法提供了可以在组织中实施的行动建议和工具，强调敏捷管理和持续改进。

🏢 起源

Management 3.0 是由 IT 经理 Jurgen Appelo 在 2010 年创建的管理模式。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Market Fit","question":"Market Fit 是什么？","description":"当产品满足强烈的市场需求时。","date":"2024-11-10","categories":["startup","product","lean startup"],"published":true,"slug":"market-fit","content":"

🎯 定义

Market Fit 发生在一家公司的产品满足强烈市场需求时，客户在一个能够支持增长和盈利的规模上购买、使用并推荐它。

💼 重要性

对于初创公司和成熟公司来说至关重要，因为它减少了失败的风险，促进产品销售，并使关于功能、定价和市场方法的决策更加明智。

📈 测量

通过一系列定性和定量指标测量，包括客户调查、保留率和市场份额。

🔍 过程

实现市场适应性涉及理解目标客户，识别其需求，定义价值主张，并与市场测试产品。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Mindset","question":"Mindset 是什么意思？","description":"它是一套既定的态度、信念和观点。","date":"2024-11-10","categories":["mentality","mindset","philosophy","agile"],"published":true,"slug":"mindset","content":"

🧠 定义

Mindset 或心态，是一套既定的态度、信念和观点，这些塑造了一个人如何解读和响应他们周围的世界。

🌱 类型

两种常见的心态包括成长心态，相信通过努力可以发展能力，和固定心态，相信能力是天生的、不可改变的。

💡 重要性

心态可以显著影响一个人的行为、动机和发展能力，影响他们生活的各个领域。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"MMF","question":"MMF 是什么意思？","description":"它代表最小可市场化功能。","date":"2024-11-10","categories":["MVP","Lean Startup","value","feature"],"published":true,"slug":"mmf---minimum-marketable-feature","content":"

🎯 定义

Minimum Marketable Feature (MMF) 或最小可市场化功能，是产品中可独立提供价值的最小功能集，可以引导用户购买或使用。

📈 重要性

MMF 对于最小可行产品 (MVP) 开发至关重要，帮助确定产品的核心功能，这些功能必须包括以满足特定市场需求或问题。

🔍 过程

设计 MMF 包括确定那些能够解决用户关键问题并促进产品销售的功能。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Mob Programming","question":"什么是 Mob Programming？","description":"它是一种软件开发方法，一群程序员在单个工作站上共同工作。","date":"2024-11-10","categories":["pair programming","collaboration","development","Extreme Programming"],"published":true,"slug":"mob-programming","content":"

🏉 团队协作

Mob Programming 是一种软件开发方法，一群程序员在单个工作站上共同工作。

🔄 角色轮换

类似于配对编程，在 Mob Programming 中，团队经常轮换“驱动员”的角色，驱动员积极编写代码，而其余团队提供实时反馈和指导。

📈 集体智慧

Mob Programming 利用整个团队的集体知识和专业技能解决问题和开发软件，可能导致更高质量的代码。

🔀 分布

与配对编程只涉及两名程序员不同，Mob Programming 涉及更大的群体，通常是三名或更多的程序员同时共同工作。

🌐 远程协作

它也可以远程进行，不同地点的程序员使用协作工具共同工作，如 VSCode 的“Live Share”。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Mockups","question":"Mockup 是什么？","description":"它是产品的静态和视觉表现。","date":"2024-11-10","categories":["mockup","design","UX","UI"],"published":true,"slug":"mockup","content":"

🖼️ 定义

Mockup 是产品的静态表现，通常用于产品设计和开发中展示最终产品可能的外观和使用方式。

🎨 元素

它包括设计元素，如字体、标识、图像、配色方案和导航视觉，这些都是最终用户体验的一部分。

🔍 目的

Mockups 用于呈现和评估设计概念、UI 和 UX，允许在产品完全开发之前进行反馈和迭代。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Muda","question":"Muda 是什么？","description":"它是一个日本词，翻译为浪费。","date":"2024-11-10","categories":["muda","kanban","lean","waste","waste"],"published":true,"slug":"muda","content":"

📉 定义

Muda 是一个日本词，翻译为浪费，指的是流程中任何不增加最终产品或服务价值的活动。

🏭 Lean

Muda 是 Lean 的核心概念，目的是消除浪费以提高效率和生产力。

🚫 浪费类型

有两种主要的浪费类型：那些不增加价值但必须的活动，以及那些不增加价值且不必要、应该被消除的活动。

🔢 TIMWOOD

除上述类型外，根据它们的性质，它们进一步被归类为七种浪费类型，由缩写 TIMWOOD 表示，包括：库存、运输、运动、等待、过度生产、过度加工和缺陷。

🏗️ 起源

Muda 的概念源自丰田生产系统 (TPS)，是 Lean 管理的基本原则。

💰 商业影响

通过减少 Muda，组织可以提高运营效率，降低成本，并提高总体质量。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Multitasking","question":"Multitasking 是什么意思？","description":"它涉及同时执行多个任务。","date":"2024-11-10","categories":["multitasking","wip","wip limit","kanban"],"published":true,"slug":"multitasking","content":"

🧠 定义

Multitasking，或多任务处理，涉及同时执行多个任务，无论是由计算机还是人来执行。

💻 机器

在计算领域，它指的是操作系统同时执行多个任务。

👩‍💼 人类多任务处理

对于人类，它涉及快速切换任务或连续快速执行几项任务。

🚫 生产力

生产力和效率的研究表明，尽管多任务处理似乎有效，但实际上可能会降低生产力并导致更多错误。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"MVP","question":"MVP 是什么？","description":"它代表最小可行产品。","date":"2024-11-10","categories":["MVP","Lean Startup","startup","product"],"published":true,"slug":"mvp---minimum-viable-product","content":"

🎯 定义

Minimum Viable Product (MVP)，或最小可行产品，是以最少的功能发布的产品，以最大限度地测试关键商业假设。

🚀 目的

MVP 的目的是快速推向市场，以验证关键假设并快速学习，强调 Lean Startup 中验证学习的重要性。

🔍 迭代开发

MVP 允许迭代开发，产品以基本功能发布后根据用户反馈进行改进。

💰 成本节约

MVP 有助于最小化投入到可能不成功的产品中的时间和资源。

📈 市场验证

它们允许在进行重大投资之前测试产品或商业想法的市场需求。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Nexus","question":"Nexus 是什么？","description":"它是一个 Scrum 扩展框架。","date":"2024-11-10","categories":["Nexus","Scrum@Scaled","Scrum","Scaling"],"published":true,"slug":"nexus","content":"

🔗 Nexus 框架

Nexus 是由 Ken Schwaber 和 scrum.org 开发的框架，用于扩展 Scrum，最小化和管理多个团队之间的依赖。

🎯 目标

Nexus 的目标是帮助团队通过减少复杂性和依赖性在保持 Scrum 基本原则的同时交付更多价值。

👥 组合

Nexus 涉及大约三到九个 Scrum 团队共同工作交付单一产品。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Niko-Niko","question":"Niko-Niko 是什么？","description":"它是一个用来跟踪团队情绪的视觉工具。","date":"2024-11-10","categories":["Niko-Niko","Team"],"published":true,"slug":"niko-niko","content":"

🗓️ 描述

Niko-Niko 日历是一个用来跟踪团队情绪的视觉工具，也被称为幸福指数。

🔍 起源

Niko-Niko 一词源自日本，意为“微笑”，由福冈市软件技术有限公司的 Sachiko Kuroda 女士在 2005 年创造。

⚒️ 使用

团队成员在每个工作日结束时在日历上放置代表其心情的彩色贴纸或表情符号，并附上简短说明。

📈 好处

这个日历有助于量化士气、心理健康和团队动力，提供了一段时间内团队表现的概览。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"OKRs","question":"OKR 是什么意思？","description":"这个缩写代表目标和关键结果。","date":"2024-11-10","categories":["OKR","KPI","Metric","Objectives"],"published":true,"slug":"okr","content":"

📅 起源

OKRs 由英特尔的 Andrew Grove 在 1970 年代开发，并由 John Doerr 普及，后者将这一概念引入了 Google。

🎯 意义

OKRs（目标和关键结果）是一个框架，用于设定和跟踪组织内部目标及其成果。

🎯 目标

OKRs 中的目标应该是清晰的、有意义的、具有挑战性的。它们应该以一种激励团队的方式制定。此外，它们应与组织的使命和愿景保持一致。一个好的目标虽然可能难以实现，但应该是现实的，并有助于组织的成长和改善。

🔑 关键结果

OKRs 中的关键结果是用来衡量实现目标进度的具体指标。关键结果应该是可量化的，意味着它们应该以某种方式可被测量。例如，一个关键结果可能是“销售额提高 20%”。

🌐 扩展

OKRs 已被许多大型科技组织采纳，这在很大程度上是因为 John Doerr 的影响。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Open Space","question":"什么是 Open Space？","description":"它是一种没有预设议程的活动形式，由参与者自行领导。","date":"2024-11-10","categories":["Agile","Law of Two Feet","self-organization","event"],"published":true,"slug":"open-space","content":"

🔄 定义

Open Space 是一种参与者驱动的活动形式，允许自组织和在 Agile 环境中探讨特定问题或主题。

🎯 目的

快速从大量人群中收集关于特定主题的最佳想法，通常在短时间内完成。

👥 参与者领导

活动的内容和结构由参与者决定，不是组织者。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Pair Programming","question":"什么是 Pair Programming？","description":"它是一种两个程序员一起编码的开发方法。","date":"2024-11-10","categories":["pair programming","collaboration","development","Extreme Programming"],"published":true,"slug":"pair-programming","content":"

🔄 定义

Pair Programming 是一种两个程序员一起在一个工作站上编码的开发方法。

🔄 角色

两名程序员经常互换角色，观察者同时考虑工作的战略方向，而驱动者专注于战术方面。

👥 协作

Pair Programming 是一种需要大量沟通的协作技术，目的是产生更高质量的代码并共享知识。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Parking Lot","question":"什么是 Parking Lot？","description":"它是一种在会议中提高专注度的技巧。","date":"2024-11-10","categories":["technique","timebox"],"published":true,"slug":"parking-lot","content":"

🅰️ 定义

Parking Lot 是一个指定的空间，无论是物理的还是虚拟的，用来记录和处理会议中出现但与当前讨论无关的主题、问题或想法。

🚗 目的

它有助于保持对主要议程的关注，防止讨论偏题，并确保所有相关事宜在适当的时间和约定的时间框内得到处理。

📝 使用

参与者可以在 Parking Lot 中简要记下偏题的项目，由主持人负责在主会议后回顾和处理这些项目。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PBI","question":"PBI 是什么意思？","description":"它代表产品积压工作项。","date":"2024-11-10","categories":["backlog","product backlog","sprint backlog","scrum"],"published":true,"slug":"pbi---product-backlog-item","content":"

📝 定义

Product Backlog Item，或产品积压工作项，是 Scrum 中用来代表需要完成的单个需求或工作的术语。

🎯 重要性

PBIs 对于组织和优先处理需要完成的工作至关重要，为整个团队提供可见性和透明度。

🔄 性质

产品积压是一个活文档，随着开发的进展而演变，根据团队的需求和反馈，PBIs 会被更新、添加或移除。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PI","question":"PI 是什么意思？","description":"它代表项目增量。","date":"2024-11-10","categories":["Release Train","SAFe"],"published":true,"slug":"pi---program-increment","content":"

⏱️ 定义

Program Increment，或项目增量，是一个持续 8 到 12 周的时期，期间一个敏捷发布列车 (ART) 为产品交付增量价值。

📈 目的

为规划、构建和验证完整系统增量提供固定的节奏。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PI Planning","question":"PI Planning 是什么意思？","description":"它是规划项目增量的一个活动。","date":"2024-11-10","categories":["PI","SAFe","scaling"],"published":true,"slug":"pi-planning","content":"

📈 定义

PI Planning，或项目增量规划，是 SAFe 中的一个活动，用于使多个团队与共享的使命和愿景保持一致。

🤝 目的

旨在为下一个项目增量（通常持续 8 到 12 周）创建共享的理解和承诺。

👥 参与者

参与角色包括产品经理、产品负责人、发布列车工程师、Scrum 主管和开发人员，他们协作规划和优先安排工作。

🗓️ 过程

该活动涉及审查积压工作、识别依赖关系并为敏捷发布列车设定清晰目标。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Planning Poker","question":"什么是 Planning Poker？","description":"它是一种用来估算工作量的技术。","date":"2024-11-10","categories":["scrum","estimation","user story","story points","XP"],"published":true,"slug":"planning-poker","content":"

🃏 定义

Planning Poker 是敏捷团队用来估算完成用户故事或任务所需努力的一种技术。

🤝 估算

这项技术涉及团队成员使用一副牌独立估算努力，然后进行讨论和重新估算，直到达成共识。

💬 重要性

这项技术的真正意义不在于达到的分数，而在于它促进的对话，有助于团队成员理解和协作。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PMBOK","question":"PMBOK 是什么？","description":"它代表项目管理知识体系。","date":"2024-11-10","categories":["PMBOK","Projects","PMI"],"published":true,"slug":"pmbok","content":"

📘 定义

PMBOK 是由项目管理协会 (PMI) 开发的项目管理知识体系，为项目经理提供基础概念、最佳实践和项目管理流程。

🌐 重要性

PMBOK 作为项目管理的标准参考，定期更新以反映行业变化，包括敏捷框架和变更管理模型的整合。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PMI","question":"PMI 是什么意思？","description":"它代表项目管理协会。","date":"2024-11-10","categories":["PMI","PMBOK","PMP","Project"],"published":true,"slug":"pmi","content":"

🏢 组织

项目管理协会 (PMI) 是一个专注于提高项目管理知识的非盈利组织。

📜 PMP 认证

PMI 提供 PMP 认证，这是项目经理的全球认可标准。

📚 知识体系

该组织不仅致力于发展，还负责出版 PMBOK，这是项目管理领域中最负盛名和被认可的知识体系。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"PMP","question":"PMP 是什么意思？","description":"它代表项目管理专业人员。","date":"2024-11-10","categories":["PMBOK","PMP","PMI","Project"],"published":true,"slug":"pmp","content":"

🎓 PMP 认证

PMP 是由项目管理协会 (PMI) 提供的认证。

🌍 认可

PMP 认证在 125 个国家得到认可，并在项目管理领域高度重视。

📚 要求

要获得 PMP 认证，候选人必须满足特定的教育、经验和培训标准，并通过严格的考试。

📖 PMBOK 指南

认证基于 PMBOK 指南，该指南汇编了项目管理的最佳实践，并定期更新以反映行业标准。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Portfolio","question":"Portfolio 是什么？","description":"它是项目和程序的战略组合。","date":"2024-11-10","categories":["project","program"],"published":true,"slug":"portfolio","content":"

📊 定义

Portfolio 指的是作为一组管理的项目、程序和其他工作元素的集合，以实现战略业务目标。

🎯 优先级调整

随着业务需求的变化，项目会被重新优先级排序，确保始终处理最有价值的工作。

📈 透明度

Portfolio 管理过程应设计为透明，对项目进展和决策过程有清晰的可见性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Product Backlog","question":"什么是Product Backlog？","description":"它是一个产品需完成工作的优先列表。","date":"2024-11-10","categories":["PBI","scrum","Product Owner"],"published":true,"slug":"product-backlog","content":"

📝 定义

Product Backlog是一个产品需完成工作的优先列表，是Scrum中Product Owner的主要工件。

🎯 目的

它有助于定义并维护产品的整体方向和愿景，并作为Scrum团队工作输入的单一来源。

🔄 迭代精炼

随着团队对如何实现目标的了解加深，Product Backlog条目会被精炼，以符合Product Goal。

🔍 可见性

它为整个Scrum团队提供了需完成的工作的透明度，有助于有效处理Sprint Planning和Sprint Review。

📈 优先级

应优先处理PBIs，以确保首先完成最有价值和最重要的工作。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Product Goal","question":"Product Goal 是什么？","description":"它是描述产品未来状态的长期目标。","date":"2024-11-10","categories":["sprint goal","scrum","Product Owner","Product Backlog"],"published":true,"slug":"product-goal","content":"

🎯 定义

Product Goal，也称为 Product Objective，是描述产品未来状态的长期目标，为 Scrum 团队提供清晰的路径。

📈 战略聚焦

它为团队提供战略焦点，指导他们跨多个 Sprint 的工作。

🔍 透明度

Product Goal 通过 Product Backlog 变得可见，Product Owner 负责其开发和明确的沟通。

📘 起源

在 2020 版 Scrum 指南中，引入了 Product Goal 作为关键元素的概念。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Product Owner","question":"Product Owner 是什么？","description":"他们负责最大化产品的价值。","date":"2024-11-10","categories":["product owner","scrum","product backlog"],"published":true,"slug":"product-owner","content":"

👩‍💼 定义

Product Owner（产品负责人）是 Scrum 中的关键角色，负责最大化产品及 Scrum 团队的工作价值。

📝 工件

产品负责人的工件是 Product Backlog，这是产品待办工作的优先级列表。

📢 沟通

产品负责人负责将产品的愿景和目标传达给团队和利益相关者。

📑 精炼

他们负责精炼 Product Backlog，确保顶层项目清晰且已知，以便有效进行 Sprint 计划。

🎯 目标

定义产品目标，这是产品的宗旨。

🔒 优先级权威

拥有根据认为适当的标准，基于它们将带来的价值，独家优先级排序 Product Backlog 项的权力。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Pull System","question":"什么是Pull system？","description":"这是一种仅在有需求时才启动工作的系统。","date":"2024-11-10","categories":["kanban","jit","lean","wip","waste"],"published":true,"slug":"pull","content":"

🔄 定义

在Kanban中，Pull system是一种仅在有需求时才启动工作的系统，与依赖预测的Push system相对，后者可能导致生产过剩。

📦 及时生产

Pull systems是及时生产(JIT)模型的核心部分，货物生产以满足实际需求，减少过剩库存和浪费。

🚦 Kanban信号

Kanban使用视觉信号，如卡片和wip限制，来指示何时应开始工作，将生产直接与客户需求联系起来。

📉 减少浪费

Pull systems通过将生产与实际需求对齐，帮助最小化浪费，从而更有效地使用资源。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"QA","question":"什么是QA？","description":"QA是一个确保软件质量的过程，通过一系列测试来识别和修复缺陷。","date":"2024-11-10","categories":["testing","sqa","software quality"],"published":true,"slug":"qa---quality-assurance","content":"

📝 定义

QA，或称为质量保证，是一个通过计划和系统地进行测试活动来识别和修复软件缺陷的过程。

🎯 目的

QA的目的是确保产品符合定义的质量标准和客户期望，从而提高用户满意度。

🔍 测试范围

测试包括但不限于功能性测试、性能测试、安全性测试和兼容性测试。

🛠️ 方法

QA过程可能包括自动化测试和手动测试，以确保软件的每个方面都经过检验。

📈 效果

良好的QA实践可以显著提高产品质量，减少后期维护成本，并提高客户信任。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"QBR","question":"什么是QBR？","description":"QBR是一个周期性会议，通常每季度举行一次，用来评估公司特定期间的业绩和结果。","date":"2024-11-10","categories":["QBR","OKR","business","strategy"],"published":true,"slug":"qbr---quarterly-business-review","content":"

📊 定义

Quarterly Business Review (QBR)，或称为季度业务回顾，是一个周期性会议，通常每季度举行一次，用来评估公司的业绩和结果。

🔍 重点

QBR通常涉及关于公司业绩、未来计划及必要的商业策略调整的战略性讨论。

🤝 参与

关键利益相关者通常参与QBR会议，包括客户和公司双方。

🗓️ 常规做法

QBR是标准的商业做法，帮助组织保持与其战略目标的一致，并做出明智的决策。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Release","question":"什么是release？","description":"它是一个已完成、已测试并可供使用的软件特定版本。","date":"2024-11-10","categories":["release candidate","PRO","PRE","staging","software"],"published":true,"slug":"release","content":"

🚀 定义

Release或发布指的是一个已完成、已测试并可供终端用户使用的软件特定版本。

🎯 目标

主要目标是确保软件以受控和可预测的方式交付，满足质量和服务级别要求。

🔄 重要性

发布在软件开发中是重要的里程碑，通常包括新功能、性能改进和错误修复。

🔖 版本与发布

虽然发布是软件的一个版本，但并非所有软件版本都被视为发布；发布是公开供使用的版本。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Release Candidate","question":"什么是Release Candidate？","date":"2024-11-10","categories":["release","development","alm"],"published":true,"slug":"release-candidate","content":"

🚀 定义

Release Candidate (RC)是一个软件程序的版本，几乎已经完成并准备发布，待进行最终测试。

🔍 目的

RC阶段是软件产品发布前的最后一步，作为最终质量检查。

🛠️ 测试

在RC阶段，将进行严格测试，以识别和纠正可能影响软件性能或稳定性的任何关键问题。

📦 命名约定

Release candidates通常以“RC”加版本号的形式表示，如“3.0-RC1”。

👨‍💻 开发阶段

🅰️ Alpha: 软件程序的第一个完整或几乎完整的版本，通常用于内部测试。\n🅱️ Beta: 比Alpha更稳定的版本，发布给更广泛的群体进行测试和反馈。\n🆗 RC: Release Candidate阶段在beta之后，是软件产品正式发布前的最后一步。\n🎯 RTM: 代表“Release to Manufacturing”或“Release to Marketing”，表示软件已准备好分发。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"IT Roadmap","question":"什么是IT roadmap？","description":"在IT中，roadmap是一个战略计划的视觉表示，将组织的技术资源与其短期和长期商业目标对齐。","date":"2024-11-10","categories":["roadmap","IT","strategic planning"],"published":true,"slug":"roadmap","content":"

🗺️ Roadmap定义

在IT中，roadmap是一个战略计划的视觉表示，将组织的技术资源与其短期和长期商业目标对齐。

🔗 与战略的联系

它作为技术相关倡议的指导，概述了必需的技术、开发时间线、资源需求和潜在挑战。

👩‍💻 敏捷工具

Roadmaps在敏捷方法中常用来在组织内部和外部利益相关者之间传达技术战略。

📈 战略规划

它们是管理和传达组织内部技术演变的强大工具。

📱 产品Roadmap

专注于产品的开发和改进的时间线，明确未来产品的方向和更新。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"ROI","question":"什么是ROI？","description":"ROI是衡量投资的财务回报的指标，通常表示为比率或百分比。","date":"2024-11-10","categories":["ROI","finance","investment"],"published":true,"slug":"roi---return-of-invest","content":"

📈 定义

ROI，即投资回报率，是衡量投资财务效益的一种指标，通常表示为比率或百分比。

🎯 目的

ROI的目的是提供一个清晰的衡量投资财务成功的指标，有助于投资决策。

🔄 重要性

ROI对企业至关重要，因为它通过提供清晰的投资财务成功度量，有助于决策。

🎯 应用

它在营销中广泛用于评估活动的表现，在业务中一般用于评估各种投资的效率。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"SAFe","question":"SAFe是什么意思？","description":"它代表Scaled Agile Framework，是一套在企业规模实施敏捷实践的组织模式。","date":"2024-11-10","categories":["SAFe","scaling","agile"],"published":true,"slug":"safe---scaled-agile-framework","content":"

🔍 定义

Scaled Agile Framework（SAFe）是一套组织模式，用于在企业规模实施敏捷实践。

🏢 目的

其目的是使公司能够在整个组织中应用敏捷框架，促进灵活性、创新，并迅速响应客户需求。

🎯 ART

SAFe的关键要素之一是敏捷发布列车（ART）。

👎 批评

SAFe是敏捷社区中最受批评的扩展框架。它主要的批评之一是没有从文化角度解决转变，只关注技术。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Scrum","question":"什么是Scrum？","description":"它是一个通过适应性解决方案生成价值的框架。","date":"2024-11-10","categories":["agile","scrum"],"published":true,"slug":"scrum","content":"

🔍 定义

Scrum是一个敏捷框架，旨在开发适应复杂问题的解决方案，强调通过迭代和增量进展、团队合作和适应变化需求来交付价值。

🤝 合作

它旨在促进团队的自我组织能力和快速决策能力，以应对复杂和不断变化的需求。

📈 增量迭代焦点

解决方案范围通过“Sprints”，即最长一个月的短期迭代（通常为2周），每次迭代产生一个可交付的产品增量。

🎯 专注于价值

Scrum优先交付客户早期和定期需要的最高价值特性，超过产品负责人排序的Backlog。

🎯 Scrum角色

Scrum确立了特定角色：Scrum Master，确保遵守Scrum实践；产品负责人，定义产品需求；以及开发者，负责实现构成产品的解决方案。

🎯 Scrum工件

Scrum的主要工件包括产品Backlog，即产品所需的全部列表；Sprint Backlog，即下一个Sprint中将开发的解决方案的承诺；以及增量，即已完成项的集合，准备交付。

🕒 Scrum事件

Scrum确定以下事件：Sprint、Sprint计划、每日Scrum、Sprint回顾和Sprint回顾会议。

💡 Scrum价值观

Scrum基于承诺、勇气、专注、开放和尊重。这些关键价值观促进了团队内的合作和共享责任环境。

📘 Scrum支柱

Scrum基于透明度、检查和适应的支柱。这些支柱支持敏捷过程，促进可见性、持续评估和灵活适应变化。

📘 Scrum指南

Scrum指南提供了敏捷框架的基本和实用理解，格式易于获取。适用于那些希望实施Scrum的人，免费下载Scrum指南。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Scrum Master","question":"什么是Scrum Master？","description":"它是负责在组织或团队中建立Scrum的角色。","date":"2024-11-10","categories":["scrum","role","framework","agile"],"published":true,"slug":"scrum-master","content":"

👨‍💼 定义

Scrum Master是Scrum框架中的三个关键角色之一，负责在团队和组织中建立Scrum，并确保团队和组织理解其理论并坚持其实践。

🔄 障碍

Scrum Master通过促进障碍的移除和为团队创造自我管理和跨功能的空间，帮助团队持续改进。

📊 度量和报告

帮助团队理解和使用度量来观察进展和识别改进领域。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Scrum of Scrums (SoS)","question":"什么是Scrum of Scrums？","description":"这是一种用于协调多个Scrum团队工作的方法。","date":"2024-11-10","categories":["Scrum","scaling","agile"],"published":true,"slug":"scrum-of-scrums","content":"

🔄 定义

Scrum of Scrums (SoS) 是一种在敏捷软件开发环境中，用于协调多个实践Scrum的团队工作的扩展技术。

📜 背景

Scrum of Scrums 由Jeff Sutherland于2001年正式提出，作为一种解决多个团队在Scrum框架内共同开发单一产品或产品族时协调和对齐需求的技术。

👥 代表

每个团队指定一名代表/大使参加一种仅限分团队代表的日常Scrum，称为Scrum of Scrums。

⏱ 时间限制

会议不应超过30分钟，重点是协调并解决团队之间的任何依赖或障碍。

🔗 可扩展性

SoS可以通过实施Scrum of Scrums的Scrum来进一步扩展，允许在组织的多个层面上进行协调。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Scrumban","question":"什么是Scrumban？","description":"它是一个结合了Scrum和Kanban原则的框架。","date":"2024-11-10","categories":["Scrum","Kanban","agile"],"published":true,"slug":"scrumban","content":"

🔄 定义

Scrumban是一个框架，结合了Scrum和Kanban的原则，提供了一种灵活的产品管理方法。

🔍 起源

“Scrumban”一词由Corey Ladas创造，该框架旨在帮助团队在Scrum和Kanban之间过渡，或以混合方式运作。

🎯 重点

该方法强调持续改进和效率，同时保持结构与灵活性之间的平衡。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Scrum@Scale","question":"Scrum@Scale是什么？","description":"它是一种框架，用于在组织范围内扩展Scrum实践。","date":"2024-11-10","categories":["agile","scaling"],"published":true,"slug":"scrumscale","content":"

🔍 定义

Scrum@Scale是一种框架，旨在帮助组织在整体上实施Scrum，促进在组织内自上而下的自然扩展。

🎯 目的

旨在使Scrum实践能够从组织独特条件中自然成长。

🔬 实证控制

该框架基于实证过程控制的支柱和Scrum价值观，专注于透明性、检查和适应。

📚 指南

官方的Scrum@Scale指南提供了对框架及其组件的全面了解。您可以通过此链接免费访问。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Senior","question":"什么是Senior？","description":"它是一名具有高水平语言和技术栈知识的开发者。","date":"2024-11-10","categories":["senior","role","team"],"published":true,"slug":"senior","content":"

👨‍💻 角色定义

高级开发者通常拥有超过5年的经验，并且具有使用的语言和技术栈的高水平知识。

🕰️ 经验

“高级”头衔不仅仅基于经验年限，还包括个人展示的天赋和软技能。

📈 领导力

在组织中，预期高级开发者将积极指导和协助初级团队成员。

🧠 解决问题

他们负责将想法转化为深思熟虑且可实施的解决方案，常常在此过程中指导他人。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Servant Leadership","question":"什么是仆人领导？","description":"它是一种哲学，在这种哲学中，领导者的主要目标是服务他人。","date":"2024-11-10","categories":["leadership","agile","management 3.0"],"published":true,"slug":"servant-leadership","content":"

👥 定义

仆人领导是一种哲学，在这种哲学中，领导者的主要目标是服务他人，专注于他们的福祉和成长。

🌱 关键原则

仆人领导者分享权力，优先考虑团队的需求，并帮助人们发展并发挥最大潜力。

🔄 对比

与传统领导不同，传统领导常常涉及权力的积累和行使，而仆人领导强调服务和赋权他人。

📚 起源

“仆人领导”这一短语最初由Robert K. Greenleaf在他1970年的论文《作为领导的仆人》中普及。Greenleaf将他对Hermann Hesse的《向东旅行》的阅读归功于这一术语的灵感来源。

🏢 应用

Greenleaf在担任AT&T执行官时，将这一概念应用于组织环境中。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","no","pl","pt","ru","sv","tr"]},{"title":"SLA","question":"SLA是什么意思？","description":"它代表服务级别协议。","date":"2024-11-10","categories":["service","kanban","metrics"],"published":true,"slug":"sla","content":"

📝 定义

服务级别协议，或SLA，是服务提供者和客户之间的合同，定义了提供者承诺提供的服务水平。它包括如上线时间、交付时间、响应时间和解决时间等指标。

🔍 重要性

SLA对双方都至关重要，因为它们建立了明确的期望，提供了衡量绩效的基础，并且概述了如果未满足要求将采取的行动。

🤝 创建

SLA通常通过谈判创建，双方就特定服务、绩效指标、责任和潜在的处罚达成一致。

👥 参与方

它通常涉及客户（内部或外部）和服务提供者，但也可以在同一组织的不同业务单位之间进行。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"SOLID","question":"SOLID原则是什么？","description":"它们是一组设计指南，用于提高软件的可维护性和可扩展性。","date":"2024-11-10","categories":["principles","software","development"],"published":true,"slug":"solid","content":"

🏛️ 起源

SOLID原则由Robert C. Martin，也被称为Uncle Bob，在2000年初关于面向对象设计的工作中引入。这些原则是五个设计概念的汇编，帮助开发者创建软件系统。

📕 定义

SOLID是一个缩写词，代表面向对象编程中的五个设计原则：单一职责、开闭原则、里氏替换、接口隔离和依赖倒置。

🔍 目的

这些原则提供了一个框架，用于设计易于维护、理解和扩展的软件，允许开发者避免常见的设计和架构陷阱。

🔨 单一职责（SRP）

一个类应该只有一个变更的理由。

🔒 开闭原则（OCP）

软件实体应该对扩展开放，但对修改关闭。

🔄 里氏替换（LSP）

超类的对象应该能够被其子类的对象替换，而不影响功能。

🔀 接口隔离（ISP）

多个针对客户的接口比一个通用接口更好。

🔄 依赖倒置（DIP）

高层模块不应依赖低层模块；两者都应依赖于抽象。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Spike","question":"什么是Spike？","description":"它是一个用于减少不确定性的研究或实验任务。","date":"2024-11-10","categories":["Extreme Programming - XP","Agile","User Story","Uncertainty"],"published":true,"slug":"spikes","content":"

🔍 Spike定义

“Spike”是极限编程（XP）中使用的一个术语，指的是一个研究或实验任务。通常用于减少不确定性或获取知识，以估算或实施一个用户故事。

🕒 时间限制

Spike是时间限制的，通常在单个冲刺的持续时间内，这意味着它们有一个预定义的最大持续时间，不旨在交付产品的功能增量。

🔧 技术Spike

用于评估技术方面的问题，如性能、可行性或项目中新技术的影响。

📐 功能Spike

用于理解用户互动，或为特定功能原型设计和测试用户界面元素。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint","question":"什么是Sprint？","description":"它是Scrum团队工作以完成一定量工作的短暂固定时期。","date":"2024-11-10","categories":["Sprint","Scrum","Agile"],"published":true,"slug":"sprint","content":"

🏃‍♂️ 定义

Sprint是Scrum团队在一段短暂固定时期内完成一定量工作的时间。

📈 增量

每个Sprint的目标是交付一个可能可交付的产品增量，为用户增加价值。

🔄 迭代

Sprint是迭代过程的一部分，一个Sprint接一个Sprint，时长相同，允许持续改进和适应变化。

🗓️ 规划和审查

一个Sprint包含其他的Scrum事件，即：Sprint规划、每日Scrum、Sprint审查和Sprint回顾。

⏱️ 典型持续时间

Sprint通常持续两周，最长不超过一个月。

📅 建议

一旦确定了Sprint的持续时间，就应该固定下来，不应更改，以保持团队随时间的一致节奏。

🌱 类比

Scrum指南将Sprint定义为：“Sprints是Scrum的心脏，将想法转化为价值的地方。”

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint Backlog","question":"什么是Sprint Backlog？","description":"它们是开发者承诺在下一迭代中完成的产品Backlog项目。","date":"2024-11-10","categories":["Scrum","PBI","Product Backlog","Sprint Backlog"],"published":true,"slug":"sprint-backlog","content":"

📝 定义

Sprint Backlog是为Sprint选择的产品Backlog（PBI）项目的集合，加上交付产品增量和实现Sprint目标的计划。

🔄 动态

它是一个活生生的计划，在Sprint期间随着对实现Sprint目标所需工作的了解而发展。

👨‍💻 所有权

开发者负责创建和维护Sprint Backlog，确保它反映了实现Sprint目标所需的工作。

🔍 透明度

Sprint Backlog是Scrum工件之一，它提供了Sprint中正在进行的工作的透明度。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint Planning","question":"什么是Sprint Planning？","description":"它是Sprint的第一个事件，在此计划迭代的范围。","date":"2024-11-10","categories":["Sprint","Scrum","event","Product Backlog","Sprint Goal","Sprint Backlog"],"published":true,"slug":"sprint-planning","content":"

📅 事件

Sprint Planning是Sprint的第一个事件，为期最长不超过八小时，针对一个月的Sprint。

🎯 目的

此事件旨在确定Sprint目标和计划交付增量所需的工作。

🔍 重点

它涉及整个Scrum团队，产品负责人和开发者协作从产品Backlog中选择可以在下一个Sprint中完成的工作。

📝 结果

结果是一个Sprint Backlog，即Sprint期间将开发的功能的预测，以及一个Sprint目标。

⏱️ 时间限制

该事件持续时间有限，以确保不会占用过多时间。

🔄 迭代

每个Sprint开始前都会进行Sprint Planning，确保规律的计划和目标设定节奏。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint Retrospective","question":"什么是Sprint Retrospective？","description":"它是每个Sprint结束时的一次会议，在会议中团队反思哪些做得好，哪些可以改进，并确定下一个Sprint的行动。","date":"2024-11-10","categories":["Kaizen","Sprint","Scrum"],"published":true,"slug":"sprint-retrospective","content":"

🔄 定义

Sprint Retrospective（回顾会），或简称Retro，是Scrum框架中每个Sprint结束时的一次会议，在会议中团队反思哪些做得好，哪些可以改进，并确定下一个Sprint的行动。

🎯 目的

主要目标是通过整合反馈并对未来的Sprint进行调整，持续改进工作方式（WoW）和团队表现。

📩 结果

会议结束后，至少要将一个改进行动纳入下一个Sprint的计划工作中。

👥 参与者

Scrum团队的所有成员，包括Scrum Master、产品负责人和开发者。

📈 迭代改进

回顾会是Scrum实证过程控制的关键元素，允许定期调整和完善团队的工作方法。

📅 时间限制

对于一个月的Sprint，回顾会时间限制为3小时，对于更短的Sprint则持续时间更短。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint Review","question":"什么是Sprint Review？","description":"它是在Sprint结束时举行的Scrum活动，此时检查产品增量。","date":"2024-11-10","categories":["Increment","Product","Product Backlog","Scrum"],"published":true,"slug":"sprint-review","content":"

🔍 定义

Sprint Review是在Sprint结束时举行的Scrum活动，此时检查产品增量并根据收到的反馈调整产品Backlog。

📈 检查

团队和利益相关者回顾Sprint期间完成的工作，并讨论可能需要的任何变更。

🎯 Sprint目标

Scrum团队表达Sprint目标并展示每个PBI如何为其贡献。

📈 指标

关于增量表现的定量数据可能会被讨论，以便于决策。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Sprint Zero","question":"什么是Sprint Zero？","description":"它是一个引入初步阶段的反模式，在使用Scrum框架开始产品开发前进行。","date":"2024-11-10","categories":["Empiricism","Sprint","Scrum","anti-pattern"],"published":true,"slug":"sprint-zero","content":"

🏃‍♂️ 定义

Sprint Zero是敏捷开发中正式冲刺过程的前奏，侧重于初步设置、规划和准备。

🚫 反模式

Sprint Zero被视为一个反模式，因为它可能导致对交付功能性软件的关注不足，并且可能被滥用作为过度计划而无具体成果的借口，违反了实证过程控制的原则。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Stakeholders","question":"什么是利益相关者？","description":"它是对企业或项目有利益关系的任何个人或团体。","date":"2024-11-10","categories":["Stakeholder","product","service","role"],"published":true,"slug":"stakeholder","content":"

👥 定义

利益相关者是对企业或项目有利益关系的任何个人或团体，他们能够影响或被项目的成果影响，从而决定项目的成败。

🎯 重要性

理解利益相关者的角色和他们的需求对于项目成功至关重要，特别是在进行项目策划和实施的过程中。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Swarming","question":"什么是Swarming？","description":"这是一个技术，整个团队集中精力解决单一任务或用户故事。","date":"2024-11-10","categories":["User Story","PBI"],"published":true,"slug":"swarming","content":"

🔄 Swarming定义

Swarming是一种技术，其中整个团队集中精力解决单一任务或用户故事，协作解决问题。

🏗️ 背景

在Scrum和其他敏捷框架中，经常使用Swarming来处理复杂问题，并确保持续的工作流和团队协作。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"System Demo","question":"什么是系统演示？","description":"它是在SAFe中的一种实践，提供了评估解决方案当前状态的手段。","date":"2024-11-10","categories":["SAFe","Scaling"],"published":true,"slug":"system-demo","content":"

🔍 系统演示

系统演示是在SAFe中的一种实践，通过展示软件的集成特性来提供评估解决方案当前状态的手段。

🔄 流程

通常在每个迭代的末尾进行系统演示，这是一次向所有利益相关者展示最新开发成果的机会。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"T-Shaped Skills","question":"什么是T形技能？","description":"它们是在一个特定领域的深入专业知识与更广泛的跨学科技能的结合。","date":"2024-11-10","categories":["skills"],"published":true,"slug":"t-shaped","content":"

🔤 定义

T形技能指的是在一个特定领域具有深入专业知识（T的垂直条）与更广泛的跨学科技能的结合，这些技能使得在不同领域间有效合作成为可能（T的水平条）。

👥 重要性

拥有T形技能的专业人员因能够在其专业领域及相关领域都作出贡献，而受到高度重视，使他们成为多才多艺且易于适应的团队成员。

🎓 起源

这一概念最初由David Guest于1991年引入，并由IDEO的CEO Tim Brown普及，作为构建跨学科团队进行创造性过程的一种方式。

🏢 麦肯锡公司

该概念也在1980年代由麦肯锡公司内部使用，被称为\"T形人\"，适用于男性和女性。

🌐 应用

T形技能在软件开发中特别受追捧，并适用于需要跨学科合作的广泛行业。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"T-Shirt Sizing","question":"什么是T-Shirt Sizing？","description":"这是一种使用T恤尺寸的估算技术。","date":"2024-11-10","categories":["planning poker","estimating","story points","fibonacci"],"published":true,"slug":"t-shirt","content":"

👕 T-Shirt Sizing

T-Shirt Sizing是一种估算技术，使用T恤尺寸（XS, S, M, L, XL）或其他相对尺度来估算任务或用户故事所需的尺寸或努力。

📊 相对估算

这种方法专注于比较任务或用户故事的相对大小，而不是尝试精确计算所需时间或努力。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"TDD","question":"什么是测试驱动开发（TDD）？","description":"测试驱动开发（TDD）是一种编程方法，强调在开发代码功能之前编写测试。","date":"2024-11-10","categories":["BDD","development","software"],"published":true,"slug":"tdd---test-driven-development","content":"

🧪 测试驱动开发（TDD）

测试驱动开发（TDD）是一种编程方法，强调在开发代码功能之前编写测试。这种方法确保代码满足预期需求并有助于防止错误。

📚 起源

测试驱动开发（TDD）是由Kent Beck在1990年代末作为极限编程的一部分开发的。

🔄 迭代过程

TDD遵循添加测试、测试执行失败、编写代码通过测试以及重构代码的周期。

🎯 焦点

TDD专注于一次测试小单位的代码，确保系统逐步建立并具有高测试覆盖率。

🔴🟢 重构周期

也被称为“红-绿-重构”周期，编写代码使失败的测试通过，然后重构以改善其结构。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Team Leader","question":"什么是团队领导？","description":"它是负责监督运营到设定目标和解决问题的角色。","date":"2024-11-10","categories":["leadership","role"],"published":true,"slug":"team-leader","content":"

👥 责任

团队领导是充当管理层与团队成员之间桥梁的角色。其角色包括监督日常运营、设定目标、衡量绩效，并确保所有团队成员与组织目标一致。此外，一个有效的团队领导还提供指导、支持和激励，以培养积极和生产力的工作环境。

📋 组织者

负责组织团队的工作，分配任务和管理资源。

🎯 策略家

制定计划和策略以实现公司和团队的目标，与组织使命保持一致。

🗣️ 沟通者

促进内外部沟通，解决冲突，推动透明对话。

💡 问题解决者

应对挑战，做出明智的决策，并引导团队走向成功。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Tech Lead","question":"什么是技术领导？","description":"一名高级开发者负责监督软件团队的技术方面。","date":"2024-11-10","categories":["leadership","development","software"],"published":true,"slug":"tech-lead","content":"

👨‍💻 领导

技术领导（TL），或技术领导者，是由一名高级开发者承担的角色，负责监督软件团队的技术方面，进行架构和设计决策，并在技术问题上指导团队成员。

🏗️ 方向

他们负责设定项目的规格和技术方向，创建技术标准框架，并监督软件和系统修改的质量。

🤝 团队指导

技术领导者在指导团队、解决技术问题以及分析现有操作以识别风险和多余部分方面发挥着关键作用。

📈 职业发展

该角色不仅涉及技术专长，还涉及领导和指导，为组织内的职业晋升提供了发射台。

📐 架构

技术领导者参与高层架构讨论，并负责系统架构的整体设计和定义。

🛠️ 指导

技术领导者指导团队成员应对技术挑战，并帮助分析和解决操作风险。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Testing","question":"什么是测试？","description":"它是验证软件产品的质量、功能和性能的过程。","date":"2024-11-10","categories":["testing","quality","qa","development","software"],"published":true,"slug":"test","content":"

🖥️ 定义

测试是进行的一种程序，用以验证和确认软件产品的功能、性能、安全性和可用性。这个过程对于识别和纠正错误、不一致性或发布到市场或交付给客户之前的任何其他问题至关重要。

🔄 进化

随着应用程序变得更加复杂，测试活动也随之采用了新的技术和方法。

🎯 验收测试

用户验收测试（UAT）验证整个系统是否按预期工作。

🔍 代码审查

确认新的和修改过的软件遵循编码标准和最佳实践。

🤝 集成测试

集成测试确保软件组件或功能能够一起工作。

🧪 单元测试

单元测试检查每个软件单元是否按预期工作。

📝 功能测试

功能测试通过模拟基于特定要求的用户交互场景来验证系统的功能。

⚙️ 性能测试

性能测试评估软件在不同工作负载下的性能。

🔁 回归测试

回归测试检查新功能是否破坏或降低功能。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"A/B Testing","question":"A/B测试是什么？","description":"它们是用于比较网页或应用程序的两个版本的方法。","date":"2024-11-10","categories":["marketing","product","ux"],"published":true,"slug":"test-a-b","content":"

🔬 定义

A/B测试，也称为A/B拆分测试，是一种用于比较网页或应用程序的两个版本以确定哪一个表现更好的方法。

📊 目的

它用于优化用户体验（UX）和通过识别哪种设计或内容变化更有效来提高转化率。

🖥️ 流程

A/B测试涉及同时向不同的网站访问者群体展示两个或更多版本（A和B），然后分析结果以确定表现更好的版本。

🧪 实施

这个过程通常是更广泛的转化率优化（CRO）策略的一部分，广泛用于数字营销和网页设计。

📈 变体

A和B是被测试的变体，A通常是当前设计（控制组），B是修改后的版本（变体）。

🔀 随机

访问者被随机分配到A或B，确保两个变体之间进行公平比较。

📊 分析

收集和分析有关用户行为和转化的数据，以确定哪个变体更有效。

🖥️ 数字元素

A/B测试可以涉及测试各种数字元素，如网页设计、内容、表单和行动呼吁。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Tester","question":"什么是测试人员？","description":"负责确保软件产品无误并符合质量标准。","date":"2024-11-10","categories":["testing","quality","development","software"],"published":true,"slug":"tester","content":"

🧪 角色

测试人员，也称为测试工程师或质量保证（QA），主要负责确保软件产品正确运行、无错误且满足规定的质量标准。

📝 责任

测试人员分析规格，开发测试案例，执行测试，报告缺陷，并向开发人员提供反馈。

🔍 技能

他们需要熟悉编程，理解系统要求，并具备强大的分析和解决问题的能力。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Three Amigos","question":"什么是三位一体？","description":"指的是商业、开发和测试的三个主要视角。","date":"2024-11-10","categories":["agile","product","development","business","software development"],"published":true,"slug":"three-amigos","content":"

👥 定义

“三位一体”是敏捷软件开发中一个术语，用于描述商业、开发和测试三个关键角色之间的合作和对话。这种合作侧重于从这三个视角定义和同意产品功能的验收标准。

🎯 目标

目标是确保对需求有共享和完整的理解，从而生产出符合商业需求并提供优秀用户体验的高质量产品。

📊 商业视角

关注正在解决的问题和用户的需求。

🛠️ 开发视角

关注如何为识别的问题创建解决方案。

🧪 测试视角

考虑可能的结果并确保解决方案符合要求标准。

🤝 构建共享理解

三位一体的合作导致对产品增量有共享的理解。

🔍 早期问题识别

帮助在开发过程中早期识别误解和混淆。

🚀 加速交付

三位一体会议的明确性可以导致产品更快交付。

📈 质量保证

确保产品满足功能性和非功能性要求。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","no","pl","pt","ru","sv","tr"]},{"title":"Throughput","question":"什么是吞吐量？","description":"它是在特定时间框架内完成的工作项数量。","date":"2024-11-10","categories":["kanban","metric","delivery","agile"],"published":true,"slug":"throughput","content":"

🔄 定义

在看板方法中，'吞吐量'用于描述团队在指定期间内完成的任务或工作项的总数。这一指标是衡量团队生产力和效率的量度，并用于评估和改善随时间的表现。

📊 指标

吞吐量是一个关键绩效指标，帮助团队理解他们的交付能力和效率。

🔍 测量

吞吐量通过计算在一段时间内已完成并交付的任务或用户故事的数量来测量，通常按迭代或每周计。

📈 跟踪

团队可以使用吞吐量数据更好地跟踪他们的交付过程中的改进并识别潜在的瓶颈。

🔢 类型

吞吐量是一个定量度量，衡量在看板系统中随时间完成的工作量。

🏭 类比

它可以与工厂的产出相比，指示工作被处理和交付的速率。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Timeboxing","question":"什么是时间框定？","description":"它是用来限制会议或任务上花费时间的技术。","date":"2024-11-10","categories":["time","agile","meeting"],"published":true,"slug":"timebox","content":"

⏳ 定义

时间框是一种时间管理概念，为活动、会议或任务分配一个特定且预定义的时间段。

🎯 目的

目的是通过防止在单一任务上花费过多时间并鼓励集中注意力和专注，来提高效率和生产力。

🏉 Scrum

在Scrum中，所有事件都有推荐的固定时间框。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Top-Down","question":"顶层向下在转型中意味着什么？","description":"它是一个由高层管理层领导转型倡议的方法。","date":"2024-11-10","categories":["transformation","leadership","agile"],"published":true,"slug":"top-down","content":"

🔝 定义

在敏捷转型的背景下，'顶层向下'方法指的是由组织的高层领导这一变革倡议的过程。在这种方法中，领导者或高级管理层做出战略决策，确定转型的愿景和方向，然后这些决策在整个组织中实施。

📈 优势和需求

这种方法可以确保一致的愿景和方向，为组织的转型提供良好的授权和采用速度，但它也要求领导者理解和实践敏捷原则和实践，以有效指导转型。

🎯 愿景

顶层向下的方法涉及传达清晰的愿景并将其与组织目标对齐，这可以带来快速的决策和明确的方向。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"Trello","question":"Trello是什么？","description":"它是一个促进任务组织的视觉工具。","date":"2024-11-10","categories":["tool","kanban","productivity","board"],"published":true,"slug":"trello","content":"

🔍 定义

Trello是一个视觉项目管理工具，允许团队使用看板、列表和卡片组织任务和项目。

🛠️ 特性

它提供了诸如任务分配、截止日期、附加文件、清单以及与其他工具的集成等功能。

🆓 界面

Trello界面基于看板，看板代表项目，在其中，列表和卡片用于组织任务和信息。

🔄 看板

Trello的设计受到看板方法的影响，强调任务和工作流程的视觉管理。

👁️ 可见性

Trello提供清晰的可见性，显示谁在处理什么任务以及哪些任务待处理，有助于团队协调和项目跟踪。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"UAT","question":"UAT代表什么？","description":"它代表用户验收测试。","date":"2024-11-10","categories":["testing","test","qa","ux"],"published":true,"slug":"uat","content":"

🎯 验收测试

验收测试是一个质量保证过程，评估软件应用是否获得最终用户的批准和符合业务需求。

🔍 意义

它是软件测试过程的最后阶段，进行以确保系统准备好投入实际使用。

📈 重点

验收测试关注业务目标和用户需求，确定软件是否符合验收标准。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"UI","question":"UI代表什么？","description":"它代表用户界面。","date":"2024-11-10","categories":["UI","UX","Design"],"published":true,"slug":"ui---user-interface","content":"

🖥️ 定义

UI（用户界面）指的是用户直接与之交互的应用程序或网站的视觉设计。

🎨 设计

它包括设计元素如颜色、排版、图标、表单、动画、按钮及其他交互组件。

👩‍💻 角色

UI设计师负责创造数字产品界面的视觉部分，专注于美观及可用性。

🔍 UI与UX

UI经常与UX（用户体验）对比，UI是可见部分，而UX是包括UI的整体用户体验。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","tr"]},{"title":"User Story Map","question":"用户故事地图是什么？","description":"它是一种技术，将产品待办列表组织成两个维度以可视化产品功能并计划发布。","date":"2024-11-10","categories":["agile","user story","jeff patton","development","products","prioritization"],"published":true,"slug":"user-story-map","content":"

📜 定义

用户故事地图（USM），或用户故事绘制，是一种技术，将产品待办列表组织成两个维度以全面可视化产品功能并计划其发布。

👤 创造者

Jeff Patton因其在2005年出版的同名书籍中引入用户故事地图技术而受到赞誉。

🎯 目的

其目的是为开发团队和利益相关者提供对产品的共同理解，促进产品发现和建设优先级的排序。

🏗️ 结构

该技术通常从识别产品的主干开始，随后发展叙述流程，详细描述不同产品部分如何连接并贡献于最终用户体验。在确立这些元素后，用户故事按照在主干中识别的活动或任务分组，并根据其重要性和为用户带来的价值进行排序，以决定潜在的发布或最小可行产品（MVP）。

🦴 主干

主干，或用户故事地图的脊柱，指的是组织和分类用户故事的主要结构，以逻辑和层次顺序描述用户流程或产品的关键活动。这个结构作为指导，帮助理解不同部分如何协同工作，为最终用户提供价值。

📚 叙述流程

在用户故事绘制的背景中，叙述流程描述沿主干的用户故事之间的进展和关系。它专注于如何将个别故事连接成一个关于用户与产品互动体验的连贯完整叙述。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"UX","question":"UX代表什么？","description":"它代表用户体验。","date":"2024-11-10","categories":["UX","design"],"published":true,"slug":"ux---user-experience","content":"

📜 定义

UX，或用户体验，是一种旨在为数字和实体产品及服务的用户提供最佳体验的策略。

🖥️ 数字重点

在数字环境中，专门从事UX的团队成员确保网站、移动应用、软件和其他数字解决方案的交互流畅且无障碍。

🏢 实体应用

UX学科也适用于实体产品，旨在改善用户的整体体验。

🎯 重要性

UX对客户满意度和留存至关重要，能显著影响公司的成功。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Value Stream Map","question":"什么是价值流图（VSM）？","description":"它是一个用于描述和分析过程流的视觉工具。","date":"2024-11-10","categories":["Lean","processes","waste"],"published":true,"slug":"value-stream-map","content":"

📜 定义

价值流图，或VSM，是在Lean中使用的一个视觉工具，用于描述和分析物料和信息通过生产过程的流动。

🎯 目的

VSM的主要目的是识别改进领域，并为战略审查和优化可视化整个生产过程。

🔄 步骤

VSM包括创建当前状态的地图，识别和消除浪费，创建未来状态的地图，以及实施改进的过程。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Waste","question":"浪费是什么意思？","description":"它指的是消耗资源但不增加客户价值的任何活动。","date":"2024-11-10","categories":["lean","kanban","waste","muda","kaizen"],"published":true,"slug":"waste","content":"

📜 定义

在Lean管理中，浪费指的是消耗资源但不为客户增加价值的任何活动。识别和消除浪费对于提高流程的效率和效果至关重要。

🔄 看板

看板是Lean管理中的一种方法，旨在通过可视化工作、限制进行中的工作，并优化工作流程来最小化浪费。

🏭 起源

Lean管理，包括浪费减少概念，起源于丰田生产系统（TPS），该系统将浪费定义为无用、无效和过度，并积极寻找持续改进（改善）的杠杆以消除它。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Waterfall","question":"什么是瀑布方法？","description":"它是一种线性和顺序的项目管理方法。","date":"2024-11-10","categories":["methodology","pmp","pmi","pmbok"],"published":true,"slug":"waterfall","content":"

🔄 定义

瀑布方法是一种线性和顺序的项目管理方法，其特点是按阶段进行结构化，每个阶段完成后才能进入下一阶段。

🏗️ 结构

项目被划分为不同的阶段，这些阶段之间没有重叠，类似于瀑布的流动。

📊 甘特图

瀑布方法常使用甘特图来可视化，常用于建筑等行业。

🚫 灵活性有限

与敏捷框架不同，一旦某个阶段完成，瀑布方法不容易适应变化，将任何变化视为对既定计划的潜在风险。

🌊 阶段

瀑布方法通常包括以下阶段：需求收集、设计、开发、测试、部署和维护。

📑 需求收集

初始阶段涉及详细收集和记录所有项目需求。

🖥️ 设计

这一阶段包括高层和详细的设计工作，规定系统架构和接口。

🛠️ 实施

根据前一阶段的设计规格开始实际的开发工作。

✔️ 测试

测试每个组件以确保它符合规定的需求并按预期功能。

🚀 部署

完成的项目向最终用户或客户部署或发布。

🔧 维护

执行维护和持续支持活动，确保项目继续正确运行。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"WET","question":"WET是什么意思？","description":"它代表'Write Everything Twice'或'We Enjoy Typing'。","date":"2024-11-10","categories":["antipattern","development","software"],"published":true,"slug":"wet","content":"

💧 WET原则

WET原则，译为'一切都写两遍'或'我们喜欢打字'，代表一种与DRY（不要重复自己）原则相对的方法，讽刺地允许甚至鼓励代码重复。

✏️ 写一切两遍

WET是一个幽默的首字母缩略词，建议不必要地写或重复代码，通常被视为强调简单性或避免抽象复杂性的一种方式。

🧩 缺乏抽象

WET代码可能缺乏适当的抽象，由于过度重复类似结构或逻辑，导致代码冗余且更难维护。

🔀 不可预测的变化

WET代码中的变化可能不可预测且不统一，因为相关元素可能不会以统一的方式变化，增加了错误和不一致的风险。

🔍 测试挑战

WET代码可能给测试带来挑战，由于重复可能涵盖更多代码路径，增加了确保软件质量的努力和复杂性。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","nl","no","pl","pt","ru","sv","tr"]},{"title":"WIP","question":"WIP是什么意思？","description":"它代表进行中的工作。","date":"2024-11-10","categories":["WIP Limit","Kanban"],"published":true,"slug":"wip---work-in-progress","content":"

🔨 定义

进行中的工作（WIP）指的是正在完成但尚未完成的任务或产品。

📊 相关性

WIP是生产和软件开发中的一个关键指标，表明在任何给定时刻正在积极进行的工作量。

🏭 制造业

在制造业中，WIP代表仍在生产过程中的部分完成产品的库存。

📈 开发

在软件开发中，使用WIP限制来优化工作流程并确保团队不承担超出其有效管理能力的工作量。

🔄 看板

WIP是看板方法中的一个关键概念，用于可视化和限制进行中的工作量，以提高效率并识别瓶颈。

⏳ 生产效率

监控WIP对于评估生产过程的效率和识别改进领域至关重要。

🔍 精益制造

WIP是精益制造中的一个关注领域，其中平衡WIP水平是简化操作和减少浪费的关键目标。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fi","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"WIP Limits","question":"WIP限制是什么？","description":"它是工作流每个阶段可以存在的最大工作量。","date":"2024-11-10","categories":["WIP","Kanban"],"published":true,"slug":"wip-limit---work-in-progress-limit","content":"

🔒 定义

WIP代表“进行中的工作”，WIP限制或进行中工作的限制是Kanban等方法中工作流每个阶段可以存在的最大工作量。

🔎 说明

限制进行中的工作不是为了减少总工作量，而是为了限制同时处理的任务数量（多任务处理）。其目的是提高专注度并推广“停止开始，开始完成”的哲学。

🔄 重要性

WIP限制帮助团队识别效率低下，揭示瓶颈，并专注于完成任务，最终提高工作流程性能。

📈 应用

团队为工作流程的每个阶段设置WIP限制，通常基于历史数据，并随时间调整以优化性能。

🎯 性能提升

WIP限制使团队专注于完成任务，这可以提高性能，增加吞吐量，并缩短交付时间。

🔍 瓶颈

WIP限制揭示了工作流中的瓶颈和效率低下，使团队能够更有效地解决这些问题。

🔄 持续评估

团队定期评估和调整WIP限制，以反映工作流性能的变化。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]},{"title":"Wireframes","question":"什么是线框图？","description":"它是界面的基本视觉表现形式。","date":"2024-11-10","categories":["wireframe","UX","UI","Mockup","Figma"],"published":true,"slug":"wireframe","content":"

🖼️ 定义

线框图是一种通常以灰阶显示的视觉表现形式，用于在添加视觉设计和内容之前勾勒出网页或移动应用的结构和功能。

🎯 目的

线框图用于建立基本布局和用户体验，重点是可用性和导航。

🔍 设计中的使用

线框图在设计的早期阶段使用，以确保项目按照约定的目标发展，并促进使用便利性和未来内容的增长。

🧰 工具

创建线框图最常用的工具之一是Figma。

\n","language":"zh","alternativeLangs":["cs","da","de","en","es","fr","it","ja","ko","nl","no","pl","pt","ru","sv","tr"]}]