5

A scrum team has grown over the dezired size, which makes it difficult to organize and plan work. The team works on a component that is used on multiple projects, that every now and then needs customizations that are based on the baseline product. The reason of the team growth is that there was increase of the load of work (new projects were started and thus new customization work was required) and consequently new members were added to the team. The projects are long lasting and are often run in parallel, so the team basically works on several projects at a time. The scope of the work is still the same, meaning that the teams cannot be divided by scope (e.g. UI vs service side).

What would be good approach for splitting the team into two teams?

How would backlog be maintained?

Should there be two product owners because of the size of the backlog?

If so, what would be good practices to synchronize the teams?

  • SAFe - Scaled Agile Framework link... scaledagileframework.com – Jon Raynor Dec 15 '16 at 17:03
  • 3
    What helped at my company was to have all people from both our teams on all the code reviews. We also assigned component leads from our senior developers and architects. Those leads were required moderators for all code reviews involving their components. They also could delay a release for their components if there were outstanding issues. Essentially we distributed a lot of the responsibility. It has worked out decently. – Adrian Dec 15 '16 at 19:53
5

Background: Working in a large team of 17, moving into an agile approach. We had the same dilemna, we had large standups and large backlogs.

What we did: Our work was easily split between 2 divisions as suggested by Michal. We now have a Datastore Team (mainly SQL/SSIS/SSRS) and a Utilities Team (C#.NET UI stuff). We have 2 backlogs, 2 scrum masters, but our line manager looks at the priorities of both with the scrum masters (as a Product Owner). The 2 scrum masters work out dependencies between the 2 teams.

Issues: We have a number of developers who switch between the 2 because of the workload. The same as you, we have projects come in requiring some work to be done, so sometimes one agile team "uses" members of the other. As we have all previously worked together it hasn't been too bad, but you don't want developers switching between the 2 too often imo. We do say that switches only occur between sprints. Once someone is in a sprint, they stay there until the next planning meeting.

I hope this helps you in some way.

5

First of all, beware Brooks's Law: adding manpower to a late software project makes it later. This is just a rule of thumb but does tend to be true, so if you only throw more people at a project in order to speed it up, without being able to divide the work differently, you may actually cause the opposite to happen.

Basically, if the teams are to be able to work without interference and without much coordination between them, you have to be able to somehow split the work by scope. Otherwise, despite the theoretical splitting into two teams, they would in practice still be working as a single large team with all the issues that this brings. Trying to work on a single backlog and just assigning tasks to one team or another will either introduce an amount of communication overhead that will eat up all your increased capacity, or even worse, you avoid the communication, which will cause the teams to step on each others' toes and cause lots of unnecessary work, conflicts and reduced morale.

So, I'm afraid you need to find some line of division. Maybe it will not be as clearly cut as backend vs UI. Maybe one team can concentrate more on the algorithms and the other on everything else? Maybe there are some components within the application which could be developed in a more or less independent fashion? Maybe some of the work is related to performance tuning and is localized so that it does not affect the whole application and can be done independently? Perhaps there are some high-level mechanisms which make use of more low-level components? Then one team could program against the interface of the low-level components and the other team could implement them. Once the interfaces are agreed upon, such teams could work in a largely independent manner.

Unfortunately it's hard to suggest anything more detailed without knowing the domain of your application and its structure. For example, you suggest that backend vs UI is not an option but you don't explain why.

EDIT: If the work consists of customizations which are mostly independent from each other and which do not modify the base product (which could affect the other team's work), I think you could try working as two separate teams with separate backlogs by splitting the work based on the customer.

I assume there are several customers and each of them orders many customizations over time. Since it is known in advance who ordered which customizations, it should be easy to tell into which backlog to place each item.

Caveat: it's still really just one product, so you should make sure the teams do know what the other one is doing in order to avoid duplicating work and to exchange knowledge. Attending sprint demos should probably be enough, and make sure the two teams' leaders do talk to each other more frequently.

  • I tried to add some more details to the question. Hope it helps. – Vladimir Stokic Dec 15 '16 at 14:03

protected by gnat May 16 '17 at 20:39

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.