One Product: One Backlog + Multiple Teams (Hradec Králové)

Most large scale product development organizations look like this:

• Split large product into small "pieces" (components, subsystems, features, does not really matter)
• Each "piece" has its own specialized team
• Each team has their own backlog of priorities for their "piece"
• Some dependency management process on top of that, as most of the teams hardly deliver an end-to-end feature

While efficient at first sight (each specialized team knows their "piece" deeply), it's utterly ineffective at product level:

• Everybody is waiting for everyone
• Everything takes forever
• Nothing is nobody's fault

There are better ways
There are better ways to organize large scale product development:

• One backlog for the whole product, shared by all teams
• Multi-specialty multi-learning end-to-end teams collaborating on the single shared backlog

Karel Smutný will share his rich experience with such adoptions:

• Why one backlog in the first place? Who benefits?
• Key principles for adoption
• How to start and what to avoid
• 2 case studies: from corporate and from a startup

Agenda
18:00 - 18:30 Arrival + Networking
18:30 - 19:30 Talk on Large Scale Scrum + 2 Case Studies
19:30 - 20:30 Interactive Workshop
20:30+ Beer + Networking