tfs冲刺_这个名为``零冲刺''的概念到底有什么问题？

tfs冲刺

What’s wrong with Sprint Zero? Let us explore this question and try finding an answer in this blog post

Sprint Zero有什么问题？ 让我们探讨这个问题，并尝试在此博客文章中找到答案

Often we end up hearing some of those inconsistent and unsure vocabulary around Scrum and one such term is ‘Sprint Zero’.

通常，我们最终会听到一些围绕Scrum的不一致和不确定的词汇，其中一个术语是“ Sprint Zero”。

Let us explore what is this term called ‘Sprint Zero’ and how it has nothing to do with Agile even before tagging it with Scrum as a thoughtful practice.

让我们探讨一下所谓的“零冲刺”这个术语，以及它在与Scrum一起标记为深思熟虑的实践之前，与敏捷没有任何关系。

Sprint Zero — Definition:

零冲刺-定义：

Its a label applied to the indeterminate period of time used to gather product requirements, analyze them and come up with big design upfront (BDUF) before the Scrum Team can start building the product.

它的标签适用于不确定的时间段，该时间段用于收集产品需求，分析需求并在Scrum团队可以开始构建产品之前提出较大的设计前期(BDUF)。

Even though it looks more appropriate to associate ‘Sprint Zero’ with Scrum, neither its part of Scrum or put it more specific — it has nothing to do with Scrum nor is a complimentary practice that enables more Agile thinking within the team.

尽管将“ Sprint Zero”与Scrum关联起来似乎更合适，但它既不是Scrum的一部分，也不是更具体-与Scrum无关，也不是使团队内部进行更多敏捷思考的免费实践。

Even though it looks more appropriate to associate ‘Sprint Zero’ with Scrum, neither its part of Scrum or put it more specific — it has nothing to do with Scrum nor is a complimentary practice that enables more Agile thinking within the team. Sprint Zero actually undermines Scrum and Agility.

尽管将“ Sprint Zero”与Scrum关联起来看起来更合适，但它既不是Scrum的一部分，也不是更具体-与Scrum无关，也不是使团队内部进行更多敏捷思考的有益实践。 零冲刺实际上破坏了Scrum和敏捷性。

According to Scrum Guide,

根据Scrum指南，

“The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.”

“ Scrum的核心是Sprint，即一个月或更短的时间范围，在此期间，将创建“完成”，可用且可能发布的产品增量。”

Sprint Zero rarely has a time-box and it doesnt come up building any potentially releasable product increment. Sprint zero actually inverts the Agile Values.

Sprint Zero很少有一个时间框，它不会构建任何可能发布的产品增量。 Sprint零实际上会反转敏捷值。

冲刺零使敏捷值反转。 这是什么意思？ (Sprint Zero inverts the Agile Values. What does it mean?)

It actually means that Sprint Zero promotes opportunity to create more ‘Comprehensive documentation over ‘Working Software’ , ‘Following a plan’ more over ‘Responding to change’ and find time and tactics for ‘Contract negotiation’ over ‘Customer collaboration’

实际上，这意味着Sprint Zero促进了创建更多“基于工作软件”的“综合文档”，“遵循计划”而不是“响应变更”的机会，并为“客户合作”寻找了“合同谈判”的时间和策略。

Since the purpose of Sprint Zero is to come up comprehensive documentation following a plan to do things upfront, it shows some of the practices with false beliefs, viz;

由于“零冲刺”的目的是按照事先做事的计划提供全面的文档，因此它显示了一些带有错误信念的做法，即：

• Trying to measure progress with comprehensive documentation and plan which delay measuring progress with working software (Remember the Agile Manifesto: Working Software over Comprehensive Documentation)
  尝试使用综合文档来衡量进度，并计划延迟使用工作软件来衡量进度(记住敏捷宣言：工作软件胜于综合文档)
• Instead of ‘welcoming change’, now take futile measures towards exhaustive analysis, documentation and design upfront part of the plan for Sprint Zero. Requirements emerge as we start progressing to build working software and no approach of gathering upfront expectations can help predict the future (Remember the Agile Manifesto : Responding to change over Following a plan)
  现在，不要“欢迎更改”，而应采取无用的措施来进行详尽的分析，记录和设计“零冲刺”计划的前期部分。 随着我们开始着手构建工作软件的过程中出现了需求，没有任何方法可以收集预先的期望来帮助预测未来(记住敏捷宣言：响应遵循计划的变更)
• Gather requirements upfront and hold an illusion of arresting the uncertainty / complexity that unfolds with the future. Further this mindset gives us a false hope of negotiating with the customer on a certain plan (around scope, time and effort — all identified and finalized) for the future. This diminishes the value behind collaboration seen with Just-in-Time (JIT) and Just Enough (JE) practices otherwise (Remember the Agile Manifesto: Customer Collaboration over Contract Negotiation)
  预先收集需求并抱有幻想，以制止未来出现的不确定性/复杂性。 此外，这种思维方式使我们错误地希望与客户就未来的某个计划(围绕范围，时间和精力-均已确定并最终确定)进行协商。 这削弱了即时(JIT)和恰好(JE)实践所具有的协作背后的价值(请记住敏捷宣言：合同谈判中的客户协作)

It not just stops here with the Agile Values but also undermines the actual sense around many Agile Principles.

它不仅以敏捷价值观止于此，而且破坏了围绕许多敏捷原则的实际意义。

For example, it delays the beginning of product development which violates the principles of ‘early and often delivery of working software’ and ‘welcoming change’. It also prevents ’emergence of requirements, design and architecture’.

例如，它延迟了产品开发的开始，这违反了“及早交付工作软件”和“欢迎更改”的原则。 它还可以防止“需求，设计和体系结构的出现”。

Sprint Zero is nothing more than the earlier stages of Waterfall Software Development covered by an Agile sounding term.

“零冲刺”只不过是一个敏捷的术语所涵盖的瀑布软件开发的早期阶段。

Sprint Zero is nothing more than the earlier stages of Waterfall Software Development covered by an Agile sounding term.

“零冲刺”只不过是一个敏捷的术语所涵盖的瀑布软件开发的早期阶段。

The best way to handle the uncertainty is not through ‘big upfront requirements collection, analysis and design’ but to articulate a clear product vision along with a road map and start building towards it.

解决不确定性的最佳方法不是通过“大量的前期需求收集，分析和设计”，而是要阐明清晰的产品愿景以及路线图，并开始着手制定路线图。

Are you aware of all these implications and what this term ‘Sprint Zero’ undermines / inverts?

您是否了解所有这些含义，以及“零冲刺”这个术语会破坏/颠倒什么？

在评论部分分享您的观点和反馈。 (Share your views and feedback in the comments section.)

翻译自: https://medium.com/the-innovation/what-is-so-wrong-about-this-concept-called-sprint-zero-f721def66b1a

tfs冲刺