MoSCoW (also known as MoSCoW prioritization or MoSCoW analysis) is a prioritization technology designed to reach a consensus with stakeholders on its importance for the delivery of each requirement. (MoSCoW方法(也称为MoSCoW优先级划分或MoSCoW分析)是一种优先级技术,旨在与利益相关方就其对每项要求的交付的重要性达成共识。)
Continue readingSprint Backlog在Scrum中是什么意义?
Sprint Backlog is a set of product backlog projects selected for the current Sprint and a plan to provide product increments for achieving Sprint goals. (Sprint Backlog是为当前Sprint选择的一组产品Backlog项目,以及为实现Sprint目标而提供产品增量的计划。)
Continue reading什么是Scrum中的产品Backlog?谁负责呢?
Product Backlog is the only source ranking list of all products you need and changes in product requirements. The owner of the product is responsible for content, usability, and prioritizes the backlog product backlog to-do list. (产品Backlog是所有你所需要的产品以及产品需求变化的唯一来源排序列表。该产品拥有者是负责内容,可用性,并要求产品Backlog产品待办事项列表的优先级。)
Continue readingSprint目标 – 如何写?
Sprint goals are a high-level summary of what the product owner wants to achieve during the sprint, usually described in detail through a specific set of product backlog items. (Sprint目标是产品所有者在sprint期间希望实现的目标的高级摘要,通常通过一组特定的产品积压项目进行详细说明。)
Continue readingScrum中Definition of Ready的定义是什么?
The product owner can work with the team to define an artifact called Definition of Ready to ensure that at the top of the backlog projects are ready to move to sprint so that the development team can confidently submit and complete them. The end of the sprint. (产品所有者可以与团队一起定义一个名为“ Definition of Ready的定义”的工件,以确保积压顶部的项目已准备好移动到sprint中,以便开发团队可以在冲刺的结束之前自信地提交并完成它们。)
Continue reading完成 vs. 接受标准的定义
Completion (DoD) is defined as a list of requirements that user stories must comply with in order for the team to complete the PBI. The difference between the two is that DoD is universal to all user stories, and acceptance criteria are applicable to specific user stories. The acceptance criteria for each user story will vary according to the requirements of the user story. (完成(DoD)的定义 是用户故事必须遵守的要求列表,以便团队完成调用。这两者之间的区别在于,DoD对于所有用户故事都是通用的,而接受标准适用于特定的用户故事。每个用户故事的接受标准将根据该用户故事的要求而有所不同。)
Continue readingScrum工件是什么?
Scrum artifacts provide key information that Scrum teams and stakeholders need to understand in order to understand the products being developed, the activities being planned, and the activities completed in the project. The following artifacts are defined in the Scrum Process Framework. (Scrum工件提供了Scrum团队和利益相关者需要了解的关键信息,以便了解正在开发的产品,正在计划的活动以及项目中完成的活动。Scrum Process Framework中定义了以下工件。)
Continue readingKen Schwaber, father of Scrum: Agile is an evolution of survival of the fittest (Turing Interview)
The rapid development of software has become the key to the viability of the company, not only in the way the company operates, but also in the software that has been embedded in their products. Enterprises that do not evolve, do not apply agile methods in software and product development, will not be able to compete effectively to survive. (软件发展之迅速,已经成为了公司是否能存活的关键,这不仅关乎公司运转的方式,也关乎已经被嵌入到他们产品中的软件。那些不进化的企业,不在软件和产品开发中应用敏捷方法的企业,就无法有效竞争并存活下来。)
Continue reading从长远来看: Scrum Master角色是否会消失?
Scrum Masters coaches, coaches, coaches and enables their teams to develop excellent products. This can be a challenging and time-consuming task for new teams in organizations that are also novices to Scrum. Over time, the team improved. Does the Scrum Master role disappear completely and continue to zero? (Scrum Masters教练,指导,指导并使他们的团队能够开发出优秀的产品。对于同时也是Scrum新手的组织中的新团队而言,这可能是一项具有挑战性且耗时的工作。随着时间的推移,团队改善了。Scrum Master 角色是否完全消失一直持续到零?)
Continue reading作为Scrum Master,您如何帮助您的产品产品拥有者?
The common goal of Scrum master and products is to create viable products through the use of Scrum best practices. The two roles overlap in some of their skill combinations. Therefore, product owners and Scrum Master should make every effort to work closely in many different areas of the project. (Scrum master和产品的所共同目标是通过使用Scrum最佳实践创建可行的产品。者两个角色在他们有一些技能组合中重叠。因此,产品负责人和Scrum Master应尽一切努力在项目的许多不同领域密切合作。)
Continue reading