Scrum Burndown模式

本文介绍了Scrum Burndown模式的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我是一个由10人组成的团队，致力于处理大型遗留代码库，而产品所有者却不太理想。我们的积压情况非常糟糕，大型史诗经常打破我们的冲刺。团队也对完成的定义感到困惑-有些成员虔诚地编写单元测试，有些则不写，有时取决于可用的时间。

I'm in a 10 person team working on a large legacy code base with a less than ideal product owner. Our backlog is in pretty bad shape and large epics have frequently been breaking our sprints. The team also struggles with its definition of done - some members write unit test religiously, others don't, sometimes depending on time available.

所以，我一直在看一些有趣的燃尽模式，我想知道其他人正在看到哪些模式以及它们的含义。

So, I've been seeing some interesting burndown patterns, and I'm wondering which patterns others are seeing and what they mean.

模式1：

# # # # # # # # # # # # # # # # # # # # # # # # # # # #

• 肯定的解释：一切都很好。
• 否定的解释：太好了，难以置信。真的发生了什么？
• Positive explanation: "All good."
• Negative explanation: "Too good to be true. What's really going on?"

模式2：

# # # # # # # # # # # # # # # # # # # # # #
• 积极的解释：这比我们想象的要容易得多，让我们介绍更多的故事。
• 否定解释：??

模式3：

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
• 正面解释：一开始不确定这项工作，然后发现比我们想象的要容易。
• 负面解释：进展不足，请停止编写单元测试以按时完成。
推荐答案

办公室就像啊，废话！我忘了。燃尽：

This is recognized around our office as the "Ah, crap! I forgot about that." burndown:

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #