scrum流程 规划 冲刺_Scrum –困难的部分2：更快地冲刺

scrum流程 规划 冲刺

In the first part, I presented my favorite list of Scrum's hard parts and how to work around them. In the second part, I offer you a colorful bouquet of workarounds as well. Have fun!

在第一部分中 ，我介绍了我最喜欢的Scrum困难部分列表以及如何解决它们。 在第二部分中，我也为您提供了多种解决方法。 玩得开心！

产品积压 (The Product Backlog)

According to the Scrum Guide, the Product Backlog is never complete. Initially, it contains only the best-understood requirements.

根据《 Scrum指南》 ，产品积压工作从未完成。 最初，它仅包含最容易理解的要求。

In innovative projects, neither requirements nor technology are known in advance. This can lead to great uncertainty. How do we know that we are in time, budget and scope so that our supervisor will receive the bonus in his target agreement?

在创新项目中，要求和技术都不是事先知道的。 这会导致很大的不确定性。 我们如何知道我们的时间，预算和范围，以便我们的主管将在他的目标协议中获得奖金？

The workaround is very simple. Make sure the project initialization phase is long enough, at least several months! If you encounter resistance from agile fundamentalists, use the term "Sprint 0". A marathon of enjoyable meetings with stakeholders is about to take place. Until the final requirements are documented in detail.

解决方法非常简单。 确保项目初始化阶段足够长，至少要几个月！ 如果您遇到敏捷原教旨主义者的抵制，请使用术语“ Sprint 0”。 与利益相关者的愉快会议的马拉松即将举行。 直到最终要求被详细记录。

Another clever idea on top of that. Write requirements with the user story template. This gives the Product Backlog an agile touch.

除此之外，另一个聪明的主意。 使用用户案例模板编写需求。 这使产品待办事项列表具有敏捷性。

And remember: as long as nothing is implemented, all wishes of stakeholders can be taken into account!

请记住：只要不执行任何措施，就可以考虑到利益相关者的所有愿望！

Scrum Master作为服务主管 (The Scrum Master as Servant Leader)

According to the Scrum Guide, the Scrum Master is a Servant Leader of the Scrum Team.

根据《 Scrum指南》，Scrum Master是Scrum团队的仆人领导 。

If you work in a company that introduces Scrum, take advantage of these new servants. After all, your company has to pay them. Here are a few examples of what Scrum Masters are used for in practice:

如果您在介绍Scrum的公司中工作，请利用这些新的仆人。 毕竟，您的公司必须付钱给他们。 以下是Scrum Master在实践中使用的一些示例：

• Scrum Master as a messenger. Instead of telling unpleasant messages directly, use the Scrum Master as a messenger. You do not  believe how many conflicts can be avoided!

  Scrum Master作为使者。 与其直接告诉令人讨厌的消息，不如将Scrum Master用作Messenger。 您不相信可以避免多少冲突！

• Scrum Master as a reporter. The Agile Manifesto says that software is the most important measure of progress. But not  everyone wants to inspect software when you can analyze numbers and graphs instead! It takes a reporter at the team level. No one can do that better than the Scrum Master.

  Scrum Master作为记者。 敏捷宣言说，软件是衡量进步的最重要指标。 但是，当您可以分析数字和图形时，并非所有人都希望检查软件！ 这需要团队一级的记者。 没有人能比Scrum Master做得更好。

• Scrum Master as a project manager. Scrum Masters who used to work as project managers are often more than willing to contribute their experience. To control Scrum projects effectively and efficiently, convert the Daily Standup into a status meeting. Combine that with assigning tasks to developers. This is how the transition from classic project management to Scrum runs smoothly.

  Scrum Master作为项目经理。 曾经担任项目经理的Scrum Master通常更愿意贡献自己的经验。 要有效地控制Scrum项目，请将“每日站立”转换为状态会议。 结合将任务分配给开发人员。 这就是从经典项目管理到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-2-sprint-harder/

scrum流程 规划 冲刺