Does each Team have to have its own Work Stream? - Scrum for Team System
Welcome to Scrum for Team System Sign in | Join

Scrum for Team System - V3 RC Discussions

Started by Bebo at 04-29-2010 2:31 . Topic has 4 replies.

Print Search
Sort Posts:    
   04-29-2010, 2:31
Bebo is not online. Last active: 11/05/2010 07:53:23 Bebo

Top 25 Posts
Joined on 10-26-2007
Posts 41
Does each Team have to have its own Work Stream?
Does each Team have to have its own Work Stream or can you reuse a Work Stream for different Teams? In the Workbench Advance Setup it says to put Team Name as the work stream title. That confused me.
   Report 
   04-30-2010, 12:48
gabriel.lozano-moran is not online. Last active: 29/04/2010 17:42:43 gabriel.lozano-moran

Top 25 Posts
Joined on 02-28-2007
Koersel (Belgium)
Posts 56
Betreft: Does each Team have to have its own Work Stream?

There is no Workstream WIT in the template so I am not sure with what you mean by reusing the workstream. As far as I know you can name the workstreams whatever you want. You define in on the Team Project settings in the Iteration Path and it is stored in the field System.IterationPath.

Eg.

Project X / 1.0 Alpha 1 / WS Team Brasil / Sprint 0 / Team Brasil
Project X / 1.0 Alpha 1 / WS Team Brasil / Sprint 1 / Team Brasil
Project X / 1.0 Alpha 1 / WS Team Brasil / Sprint 2 / Team Brasil
Project X / 1.0 Alpha 1 / WS Team Brasil / Sprint 3 / Team Brasil
Project X / 1.0 Alpha 1 / WS Team Spain / Sprint 0 / Team Spain
Project X / 1.0 Alpha 1 / WS Team Spain / Sprint 1 / Team Spain

In the above example there are two teams, one team in Brasil and a team in Spain, Brasil works with 1-week iterations and Spain with 2-week iterations. For the 1.0 Alpha 1 release the planned duration is 4 weeks.


   Report 
   04-30-2010, 3:28
Bebo is not online. Last active: 11/05/2010 07:53:23 Bebo

Top 25 Posts
Joined on 10-26-2007
Posts 41
Re: Betreft: Does each Team have to have its own Work Stream?
Sorry for the confusion. I meant something like this:

Release1.0 / 4 Week Stream / Sprint 01 / Team 01
Release1.0 / 4 Week Stream / Sprint 01 / Team 02
Release1.0 / 4 Week Stream / Sprint 02 / Team 01
Release1.0 / 4 Week Stream / Sprint 02 / Team 02

In your example the teams are on a different cadence from each other. That scenario makes sense.
In my case both teams work in 4 week increments, I was thinking I could just use one work stream. I was just wondering if that would throw off any of the reports or have some other adverse affect.

To me (as I understand it) it makes more sense to name a Work Stream by how big the cadence is (e.g. 4 week stream, 2 week stream) instead of by the team name which the workbench label suggests.

What do you think?
   Report 
   04-30-2010, 4:33
Bebo is not online. Last active: 11/05/2010 07:53:23 Bebo

Top 25 Posts
Joined on 10-26-2007
Posts 41
Re: Betreft: Does each Team have to have its own Work Stream?
I think I answered my own question. From this blog post:

http://consultingblogs.emc.com/colinbird/archive/2009/09/11/getting-started-with-scrum-for-team-system-v3-beta-1.aspx

There is this statement:

The “Workstream” part of the model enables a project to contain Sprints of different cadence (e.g. 1 team on a 2 week Sprint and another using a 4 week Sprint) and is implemented only in the Iteration Path without a matching work item. Even if you use a single cadence (recommended in most situations) it is important that a workstream node is retained, even if you change its name, to ensure that reports run correctly.

The important part for me is "even if you use a single cadence (recommended in most situations)." To me that implies that it is ok to use one stream for multiple teams.
   Report 
   04-30-2010, 4:58
gabriel.lozano-moran is not online. Last active: 29/04/2010 17:42:43 gabriel.lozano-moran

Top 25 Posts
Joined on 02-28-2007
Koersel (Belgium)
Posts 56
Betreft: Re: Betreft: Does each Team have to have its own Work Stream?

What is being said here is that even if you have a single team working with a single cadence that you must retain the structure for the Iteration Path otherwise the reports will not work. This is something I can confirm as we had to find out the hard way :-)

Here is a full example of what we have for v1.0 of a project called Pythagoras and the name of the team is K3:

Pythagoras \ 1.0 Alpha 1 \ Workstream \ Sprint 0 \ K3
Pythagoras \ 1.0 Alpha 1 \ Workstream \ Sprint 1 \ K3
Pythagoras \ 1.0 Alpha 1 \ Workstream \ Sprint 2 \ K3
Pythagoras \ 1.0 Alpha 1 \ Workstream \ Sprint 3 \ K3
Pythagoras \ 1.0 Alpha 2 \ Workstream \ Sprint 4 \ K3
Pythagoras \ 1.0 Alpha 2 \ Workstream \ Sprint 5 \ K3
Pythagoras \ 1.0 Alpha 2 \ Workstream \ Sprint 6 \ K3
Pythagoras \ 1.0 Alpha 2 \ Workstream \ Sprint 7 \ K3
Pythagoras \ 1.0 Beta 1 \ Workstream \ Sprint 8 \ K3
Pythagoras \ 1.0 Beta 1 \ Workstream \ Sprint 9 \ K3
Pythagoras \ 1.0 Beta 2 \ Workstream \ Sprint 10 \ K3
Pythagoras \ 1.0 Beta 2 \ Workstream \ Sprint 11 \ K3
Pythagoras \ 1.0 RC 1 \ Workstream \ Sprint 12 \ K3
Pythagoras \ 1.0 RTM \ Workstream \ Sprint 13 \ K3

...


   Report 
Scrum for Team ... » Version 3.x - T... » Scrum for Team ... » Does each Team have to have its own Work Stream?

Powered by Community Server, by Telligent Systems