I often use the following traffic situations when I talk about agile processes and portfolios. I thought it would be a good idea to share them here. They may also inspire you to find your own “local” examples.

The first is a typical rush hour traffic jam, caused by a lack of space and number of vehicles.  Surprisingly, the situation looks crowded but there are actually not that many cars and trucks on the road. The problem is created by strict traffic rules, for example lanes, traffic lights, intersections and of course interfering pedestrians.  Not obeying these rules may turn into harsh penalties. But even if the lights switch green, the traffic hardly flows.

.

.

.

In contrast, the other example is a picture of Grand Central Terminal, one of the larger traffic hubs in the city.

No lanes, no traffic lights or control. Actually the opposite is the case, the tracks are assigned just minutes before departure. Grand Central is simply a large hall with an information booth in the center. The train schedules and track information is on boards across the walls and screens. The responsibility of finding the gate and train information is delegated to every individual. Yes, sometimes a few folks bump into each other and not everyone will walk the most optimal path. But minor corrections and reactions based on others movements are necessary to prevent collisions. The system works faster and is extremely reliable even during peak hours.
Agile processes and PMO’s are the information booth and product roadmaps represent the train and track information. Self-organized agile teams will define what is needed to get to their goal and make the necessary adjustments.