当您有多个项目时，Scrum如何工作？ [英] How does Scrum work when you have multiple projects?

问题描述

我对Scrum的好处和过程非常了解。我在待办事项列表，燃尽图，迭代，使用用户故事以及Scrum框架的其他各种概念中得到了想法。

I'm fairly well read in the benefits and processes of Scrum. I get the ideas on the backlog, burndown charts, iterations, using user stories, and other various concepts of the Scrum "framework".

话虽如此……我为一家网络开发公司工作，该公司一次管理多个项目，由六个团队成员组成生产团队。

With that said... I work for a web development firm that manages multiple projects at one time, with six team members that make up the "production team".

Scrum如何处理多个项目？您是否仍然只是在一定时间内安排单个项目的迭代，并且整个团队都在工作，然后在迭代完成后继续进行下一个新迭代的项目？还是有一种敏捷的方式可以同时仅由一个团队使用自己的迭代来管理多个项目？

How does Scrum work with having multiple projects? Do you still just schedule an iteration for a single project in a certain amount of time and the entire team works on it, and then you move on to the next project with a new iteration when that iteration is completed? Or is there an "agile" way in managing multiple projects with their own iterations with only one team at the same time?

推荐答案

Scrum确实并不要求您必须开发一种独立的产品。它只是说明需要完成很多工作（产品积压），在下一次迭代中有一定的开发时间（从项目速度中得出），并且客户选择了一些项目/ business在此问题/任务池中具有最高优先级，将在下一次迭代中完成（冲刺积压）。

Scrum really doesn't dictate that you have to be working on the one self-contained product. It simply states that there is a bunch of stuff that needs to be done (the product backlog), there is a certain amount of development time available in the next iteration (worked out from the project velocity) and there are items selected by the client/business as having most priority from this pool of issues/tasks that will be done in the next iteration (the sprint backlog).

没有理由产品积压和sprint积压必须来自一个项目-即使在单个项目中，也会有一些分散的工作单元，就像单独的项目一样项目-UI，业务层，数据库架构等。尤其是企业软件开发就是这样，您在其中拥有许多必须不断进步的代码库。 Scrum流程-会议，问题，烧毁图表等-无论是一个项目还是多个项目，都可以正常工作。

There is no reason that the product backlog and sprint backlog have to be from the one project - even in a single project there will be discrete units of work that are like separate projects - the UI, the business layer, the database schema, etc. Enterprise software development in particular is like this, where you have a number of code bases that all have to be progressing. The Scrum process - meetings, questions, burn down chart, etc - all work whether it is one project or multiple.

在实践中，这样做通常对每次迭代都有一个主要主题-执行报告模块或与XYZ系统API的接口-因此，很多问题都来自一个项目或领域，在迭代结束时，您可以指向一个大型机构工作并在上面打勾。

Having said that, in practice it is often good for each iteration to have a major theme - "do the reporting module" or "interface with XYZ system's API" - so that a lot of the issues come from one project or area and at the end of the iteration you can point to a large body of work and place a tick against it.

这篇关于当您有多个项目时，Scrum如何工作？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！