If we face something which is new to the whole team (or most team members), then we have performed sort of an investgation sprint, where we allow ourselves some time (timeboxed) to investigate/learn.
For smaller things, we add a timeboxed activity to the sprint backlog to allow training/investigation/experimentation.
In both cases, we simply subtract the time used so far from the estimated remaining time at the end of each day.
Our scrum master has a chart with suggested quotas for extending the estimates based on a number of such parameters (new technology, new team member and so on). Still, at the end of the day, they are still just guesses.
If you're using a brand new (to you) technology, I'd suggest that you cut your velocity by half as a reasonable attempt to estimate the velocity using the new technology. Eventually, you'll be able to actually both measure your new velocity and have it return to more normal levels as your team gets familiar with the new technology. Adjust future estimates based on feedback during the early iterations.
发布评论
评论（4）
如果我们面临对整个团队（或大多数团队成员）来说都是新的事情，那么我们就进行了某种调查冲刺，我们给自己一些时间（时间限制）来调查/学习。
对于较小的事情，我们在冲刺待办事项中添加时间盒活动以允许培训/调查/实验。
在这两种情况下，我们只需从每天结束时的估计剩余时间中减去迄今为止所用的时间。
If we face something which is new to the whole team (or most team members), then we have performed sort of an investgation sprint, where we allow ourselves some time (timeboxed) to investigate/learn.
For smaller things, we add a timeboxed activity to the sprint backlog to allow training/investigation/experimentation.
In both cases, we simply subtract the time used so far from the estimated remaining time at the end of each day.
你只是猜测。
由于您的工作迭代时间很短，因此您很快就能知道 WAG 是否偏离正常。
如果您休息了，您可以针对下周的迭代进行调整。
请记住，敏捷是一个迭代过程，每次迭代都能让您更深入地了解项目。
但在开始之前，先做一个很好的猜测。
迭代估计每周都会变得更好。
You just guess.
Since you're working in short iterations, you know pretty quickly if your WAG is way off.
If you're off, you adjust for the next week's iteration.
Remember, agile an iterative process, with each iteration giving you more insight into the project.
But to get started, just make a good guess.
The iteration estimations will get better each week.
我们的 Scrum Master 有一个图表，其中包含建议的配额，用于根据许多此类参数（新技术、新团队成员等）扩展估计。 尽管如此，归根结底，它们仍然只是猜测。
Our scrum master has a chart with suggested quotas for extending the estimates based on a number of such parameters (new technology, new team member and so on). Still, at the end of the day, they are still just guesses.
如果您使用的是（对您来说）全新的技术，我建议您将速度降低一半，作为使用新技术估计速度的合理尝试。 最终，当您的团队熟悉新技术时，您将能够实际测量新的速度并使其恢复到更正常的水平。 根据早期迭代期间的反馈调整未来的估计。
If you're using a brand new (to you) technology, I'd suggest that you cut your velocity by half as a reasonable attempt to estimate the velocity using the new technology. Eventually, you'll be able to actually both measure your new velocity and have it return to more normal levels as your team gets familiar with the new technology. Adjust future estimates based on feedback during the early iterations.