DeScaling with Large Scale Scrum (Part1)

In a large scrum team , how do you assign PO?. This question is asked in several communities/projects and LeSS gives us some options

Imagine this , with large teams and every team being a scrum team ( 2–8 folks), the equation

becomes complex. If every team has a PO, then there will be large number of POs for the whole setup or combination ie 7 of them. Most team will do a copy paste and thats what is never to be done.

This means that all the

-Teams have their own Product Backlog.

-Also each will have their own features

-Each team will work on their feature and also some Java/Rest Program to develop for other teams.

-An engine if to be developed will have to come or develop first.

-PMs or PM Co-ordinations needs to be added to manage this large picture.

-Some teams like UX or portals will have nothing to do as they are waiting for others.

-Thus Product Backlogs needs to be distributed among these teams to keep them busy.

All in all , if copy paste scaling is to be done for each team. If copy paste is done then its hard to manage progress, metrics, dependencies, architecture, end to end testing etc.

Key feature of Scrum is that you give the problem to the team and they will be above to solve it by themselves. This is what is key to the Scrum that we will be using. But how do you manage the POs for each team if more than 8 teams.

One of the Options is to have ‘Feature teams’, these feature teams will solve the customers problems. These feature teams are ‘Cross Functional;’, Cross components, Stable and long lived. But there is a problem, these teams then have what is called the “Product Part Owners”

Continued in the next post