Agile Adoption and Scaling Patterns

Team Based Agile is what we mostly talk about when we talk about agile. We have Product Owners and Customers… we have ScrumMasters and Teams. We are 6-8 people… maybe all in the same room.. maybe not. We focus on solid engineering practices… collaboration… teamwork.

Horizontal Scaling is the next step. As the name implies… horizontal scaling is taking the team based model and replicating it in different parts of the organization. We see this quite a bit… pockets of agility across the enterprise… but no one is really working together in a coordinated way. Pretty much the same as team based… just more of it.

First Order Agile Scaling is basically Agile Project Management. It is the first time we start talking about how to get multiple teams working together to deliver an integrated product or project deliverable. This is where we first start thinking about the various Scrum of Scrum patterns we talked about a few posts ago.

Second Order Agile Scaling takes a collection of teams from the single project space into agile portfolio management. How are we going to break up projects and throttle them through the teams? This is where we really start to focus on lean and TOC and have to focus on enterprise priorities and investment decisions.

Third Order Agile Scaling is an area we haven’t talked much about yet. This is where we take agile outside the product delivery organization. Getting projects out the door isn’t our problem anymore… it’s not our constraint. We need to start focusing on the integrating the value stream across the entire enterprise.