scrum_Scrum-困难的部分

scrum

The hard parts of Scrum and how to work around them. Further inspiration can be found here: ScrumBut.

Scrum的困难部分以及如何解决它们。 进一步的启发可以在这里找到： ScrumBut 。

只有开发商估计 (Only the developers estimate)

According to the Scrum Guide, only members of the development team  are allowed to estimate development effort. Neither Scrum Master, nor  Product Owner.

根据《 Scrum指南》，仅允许开发团队的成员估计开发工作量。 既不是Scrum Master，也不是产品所有者。

As a Product Owner, you should therefore subtly influence  the estimates in your favor by asking questions like: "You can do that  in two weeks, right?" Or: "I can't imagine that this is a lot of effort.  Does anyone else see that?"

因此，作为产品负责人，您应该通过询问以下问题来微妙地影响估算值：“您可以在两周内完成，对吧？” 或者：“我无法想象这会花费很多精力。还有其他人看到吗？”

That way, you stay in control even when the going gets tough!

这样，即使事情变得艰难，您也可以保持控制！

完成了 (Done)

Scrum calls for a potentially shippable product increment at  the end of a Sprint: executable, tested and integrated software.  Because this is one of the hardest parts of Scrum, there are several  workarounds to make life a little easier.

Scrum要求在Sprint的末尾增加可能交付的产品 ：可执行，经过测试和集成的软件。 因为这是Scrum最困难的部分之一，所以有几种解决方法可以使生活更轻松。

First, learn to appreciate other artifacts as Sprint results as well.  How about a completed analysis or architectural document? For this to  work, you only need to adjust the Definition of Done.

首先，学会欣赏其他工件以及Sprint结果。 完整的分析或建筑文档如何？ 为此，您只需要调整“完成”的定义即可。

Second, most importantly: do not forget the phases before Scrum and after Scrum.

其次，最重要的是：不要忘记Scrum之前和之后的阶段。

Before Scrum, a planning phase of several months should take place, in which the project is approved and its scope is fixed.

在Scrum之前，应该进行几个月的计划阶段，在该阶段中，该项目将被批准并且其范围是固定的。

After Scrum, you should have a test phase of at least several weeks  until the product can finally be delivered. This workaround is  particularly useful if you do not use any form of automated testing,  integration or deployment.

在Scrum之后，您应该至少有几个星期的测试阶段，直到最终可以交付产品为止。 如果您不使用任何形式的自动化测试，集成或部署，则此解决方法特别有用。

产品负责人确定优先级 (The product owner sets priorities)

According to the Scrum Guide, the Product Owner has the final say when prioritizing the Product Backlog.

根据《 Scrum指南》，在确定产品待办事项的优先级时，产品所有者拥有最终决定权。

This is uncomfortable. It would give the lower level management folks  huge decision-making power. Real managers keep away from developers, in  order to be able to make unpleasant decisions and enforce them.

这很不舒服。 这将赋予较低级别的管理人员巨大的决策权。 真正的经理人远离开发人员，以便能够做出不愉快的决定并执行这些决定。

Fortunately, there are now established roles such as the "Proxy  Product Owner". Rightly applied, that role has no decision-making  authority. PPOs merely pass on the announcements from the top to the  developers and "take the responsibility" if something goes wrong.

幸运的是，现在已经建立了角色，例如“代理产品所有者”。 正确使用该角色没有决策权。 PPO只是将公告从高层传递给开发人员，并在出现问题时“承担责任”。

So - these are my "recommendations" for you today.What are your favorite Scrum hacks?

所以-这些是我今天给您的“建议”。您最喜欢的Scrum骇客是什么？

To get the basics of agile software development right, visit my online course. If you want to keep up with what I'm doing, follow me on dev.to, LinkedIn or twitter. Or visit my GitHub project.

要正确掌握敏捷软件开发的基础知识 ，请访问我的在线课程。 如果您想跟上我的工作，请在dev.to ， LinkedIn或twitter上关注我。 或访问我的GitHub项目 。

翻译自: https://www.freecodecamp.org/news/scrum-the-hard-parts/

scrum