什么是敏捷方法？

敏捷方法是在整个软件开发阶段采用频繁迭代、沟通和灵活性的框架和方法。

传统的项目管理主要特点是遵循既定的计划，而敏捷则基于关键原则，例如以稳定的方式交付价值、收集反馈和适应变化。

敏捷的基本原则之一在《敏捷宣言》中概述，其中强调了四个基本价值观：人员胜于流程和工具，可运行的软件胜于详细的文档，客户合作胜于合同谈判，以及适应变化胜于遵循计划。

虽然使用敏捷方法可以提高灵活性并可能加快软件交付速度，但重要的是要认识到它可能会在开发过程中提供反馈机会，在某些情况下，这可能会带来质量的提升。

An Agile team refers to a structured group of developers, a number of which are multifunctional, and its main role is to generate customer value with the help of iterative and incremental activities. Every member has the responsibility to ensure the success of the team by managing the product roadmap, prioritizing the backlog, and delivering quality.

• Scrum Master 维护敏捷流程，确保团队遵循 Scrum，并消除前进的障碍。
• 产品负责人是客户的代表，管理产品待办事项，并确保团队生产正确的产品。
• 开发团队成员需要在称为冲刺的短时间内，产出符合敏捷规范的可工作产品。

Product managers have the most crucial role in Agile and enterprise transformation as they enable a product vision into business value, reflecting on business strategy and understanding customer needs. Their duties involve creating plans for the future, focusing on customer needs, understanding data, and leading teams from different departments.

看板和Scrum是两种用于管理团队工作的敏捷框架，但它们的功能有所不同。

看板更侧重于持续交付，重点在于可视化工作和在制品（WIP）的方法，而Scrum则侧重于在冲刺中交付，以角色、仪式和冲刺目标为指导要素。 

看板的灵活性允许适应变化，而Scrum的框架则侧重于优化项目交付。 

看板基于在制品限制下持续频繁调整工作流程的原则，而Scrum则基于冲刺墙，意味着仅在特定的冲刺时间框架内进行计划和交付。

看板使用可视化看板来管理工作流程，并经常在工作过程中进行更改，而 Scrum 使用冲刺待办事项来定义每个冲刺的任务并为每个冲刺提供指导。

看板适用于需求高度不规则且不断变化的组织，因为它很容易适应新的变化，而 Scrum 在需求明确且更可预测的环境中效率更高。

A software development team using Kanban can easily adapt newly requested features in the middle of the project, and a Scrum team would have to add those into the next sprint.

When comparing Kanban and scrum systems, consider the type of project as well as the preference of the working team. Kanban is more suitable for rapid change, while Scrum structure is good for well-defined work.

The Scaled Agile Framework (SAFe) is an organization and venture development framework that supports businesses in scaling Agile principles and practices throughout large organizations. SAFe comprises key elements like Program Increment (PI) planning, Kanban boards, and 持续交付 Pipeline.

PI planning is an event that happens in cadence to ensure that all teams and stakeholders are rightly aligned with the respective mission and vision of the firm, and Kanban boards are used to visualize the Work-In-Progress on SAFe.