Hi Gilad,

I think your "backlog" means "product backlog", right?

Then I against the idea of having a single product backlog per team.
First, product owner is the person who can decide the format of
product backlog. And basically I think you do not have a single
product owner for different projects. Second, the product backlog is
constructing based on priority, how you construct the product backlog
among projects? Then you mess up the backlog with project priority,
which not directly relate to customer requirement priority.

Based on the assumption you have to work on different projects in
same sprint, my suggestion is :

You should have your team's capacity estimated, then perhaps you need
to negotiate with project managers about capacity division among
projects. Then use your project specific capacity to select product
backlog items for different projects.

Best Regards,
Xu Yi-Kaveri


--- In scrumdevelopment@yahoogroups.com, "gzgruber"
<gilad.gruber@...> wrote:
>
> Mates,
>
> Our teams sometimes have multiple projects. I am wondering what is
the
> best way and what is the SCRUM way of handling this. My feeling is
that
> the best way is to have a single backlog per team (even if this
means
> that in a sprint the team is working on backlog items belonging to
> multiple projects). I think the purists will recommend splitting
the
> team and having multiple backlogs.
>
> Any thoughts on this would be greatly appreciated
>
> BR,
>
> Gilad
>