如何在计划/估算游戏中形成“峰值”？-Howdo“spikes”figureintheschedule/estimationgame?

6  

I guess you are constantly underestimating

我猜你一直在低估

• what you do already know about the 3rd party component

您已经了解的第三方组件

• how long it takes you to create usable/helpful spikes for unknown areas

你需要多长时间才能为未知区域创建可用/有用的尖峰

1. Get better at estimating those two things.

1.更好地估计这两件事。

So, it's all about experience. No matter what methodology you use, they will help you to use your experience better, not replace it.

所以,这都是关于经验的。无论您使用何种方法,它们都将帮助您更好地使用您的体验,而不是替换它。

2. Try not to get lose track when working on those spikes.

2.在使用这些尖峰时,尽量不要失去踪迹。

They should be short, time boxed sessions. They are not about playing around with all the possible features listed on the marketing slides. Give them focus, two or three options to explore. Expect them to deliver one concrete result.

它们应该是简短的,有时间限制的会议。他们不是在玩营销幻灯片中列出的所有可能功能。给他们集中注意力,两个或三个选项来探索。期望他们提供一个具体的结果。

Update(Gishu): To summarize

更新(Gishu):总结一下

• Spikes need to be explicit tasks defined in the iteration planning step.

尖峰需要是迭代计划步骤中定义的显式任务。

• If spikes exceed the timebox period, stop working on it. Shelve the associated task. Complete the other tasks in the current iteration bucket. Return to the shelved task or add a more elaborate/broken down spike to the next iteration along with the associated task. Tag a more conservative estimate to the generation 1 spike the next time.

如果尖峰超过时间段,则停止工作。搁置相关任务。完成当前迭代存储桶中的其他任务。返回搁置任务或向下一次迭代添加更复杂/细分的尖峰以及相关任务。下一次将更保守的估计标记为第1代尖峰。

2  

If you run out of time in your timeboxed spike, you should still stop and complete your other committed work. You should then add another spike to your next iteration to complete the necessary work you need to complete in order to accurately estimate the task resulting from the spike.

如果你的时间盒峰值时间不足,你仍应停止并完成其他承诺的工作。然后,您应该在下一次迭代中添加另一个尖峰,以完成您需要完成的必要工作,以便准确估计由尖峰产生的任务。

If there is a concern over spiking things for too long and this becoming a problem - this is one reason I like 1 week iterations. :-)

如果长时间关注尖峰事件并且这成为一个问题 - 这就是我喜欢1周迭代的一个原因。 :-)

1  

@pointernil.. It's more of no estimation coupled with a Indy-Jones Head-First approach to tackling a story. I estimate stories by their content.. currently I don't take into account the time required to find the right incantation for the control library to play nice. That sometimes takes more time than my application logic.. So to rephrase the Original question, should spikes be separate tasks in the iteration plan, added on a JIT basis before you start working on a particular story?

@pointernil ..更多的是没有估计加上Indy-Jones Head-First方法来处理故事。我根据他们的内容估计故事..目前我没有考虑到找到正确的咒语所需的时间让控制库发挥得很好。这有时需要比我的应用程序逻辑花费更多的时间。所以,为了重新解释原始问题,spikes应该是迭代计划中的单独任务,在开始处理特定故事之前在JIT基础上添加?

My Spikes are extremely focussed.. I just can't wait to get back to the "real" problems. e.g. 'How do I show a context menu from this control?' I may be guilty of not reading the entire 150+ page manual or code samples.. but then time is scarce. The first solution that solves the problem gets the nod and I move on. But when you're unable to find that elusive event or NIH pattern of notification used by the component, spikes can be time-consuming. How do I timebox something that is unknown? e.g. My timebox has elapsed and I still have no clue for plugging-in my custom context menu. How do I proceed? Keep hacking away?

我的Spikes非常专注。我迫不及待想要回到“真正的”问题。例如'如何从此控件显示上下文菜单?'我可能会因为没有阅读整本150页以上的手册或代码样本而感到内疚。但是时间紧迫。解决问题的第一个解决方案得到了点头,我继续前进。但是当您无法找到组件使用的难以捉摸的事件或NIH通知模式时,峰值可能非常耗时。我如何计时未知的东西?例如我的时间框已经过去了,我仍然无法插入我的自定义上下文菜单。我该怎么办?继续黑客攻击?

Maybe this comes in the "Buffering Uncertainity" scheme of things.. I'll look if I find something useful in Mike Cohn's book.

也许这出现在“缓冲不确定性”方案中。如果我在Mike Cohn的书中找到有用的东西,我会看。

1  

I agree with pointernil. The only issue is that your estimates are incorrect. Which is no big drama, unless you've just blown out a 3 million dollar project of course :-)

我同意pointernil。唯一的问题是您的估算不正确。这不是什么大戏,除非你刚刚吹出一个300万美元的项目当然:-)

If it happens once, its a learning experience. If it happens again and the result is better, then you've got another learning experience under your belt. If you are constantly underestimating and your percentages are getting worse, you need to wisen up a bit. No methodology will get you out of this.

如果它发生一次,它是一种学习经验。如果再次发生并且结果更好,那么您将获得另一种学习体验。如果你经常低估你的百分比越来越差,你需要稍微提高一点。没有任何方法可以让你摆脱这种局面。

Spikes just need to be given the time that they need. The one thing I've seen happen repeatedly in my experience is that people expect to be able to nail a technology within a couple of hours, or a day. That just doesn't happen in real life. The simplest issue, even a bug caused by a typo, can have a developer pulling their hair our for huge chunks of time. Be honest about how competent yourself or your staff really are, and put it in the budget.

尖峰只需要给他们需要的时间。根据我的经验,我所看到的一件事就是人们希望能够在几个小时或一天内完成一项技术。这在现实生活中不会发生。最简单的问题,即使是由错字导致的错误,也可能让开发人员将头发拉到我们的大块时间。要诚实地说明自己或员工的实际能力,并将其纳入预算。