Renamed the Teams, Kept the Silos: What Scaling Agile Actually Has to Change

In Digital.ai's 2025 State of Agile survey, only 13% of respondents say agile is deeply embedded across business, technology, and supporting functions, with work aligned to the strategic outcomes of the organization.

If you lead an agile transformation, you may be telling your leadership team that you scaled the framework. Of course, if something doesn't work with one team, it's not going to work with 50. But you scaled it. The teams have new names. The events run on the same schedule for every department, a common cadence if you will.

So what actually moved underneath all of those new names? A lot of people I work with recognize that's a hard question to answer.

By the end of this article, you'll have a short test that separates what changed in the events from what changed in the structure of your organization. Then you'll know where to start on the structure: who funds the work, and who decides.

The core idea
A scaled framework and a scaled organization look identical from the conference room. The difference sits underneath the new team names, in who funds the work, who owns the outcome end to end, and who can change direction without asking another silo for permission.

Twelve Squads, Same Budget Lines

Picture a transformation that renamed every project team. The most common name I see these days is a squad. Say there are 12 of them. Each one got its own squad name, a backlog, and a sprint.

The weekly status meeting became the standup. Sprint reviews went on the calendar on a common cadence. There was a launch event, and the kickoff presentation looked great. It gives leaders a really good feeling that the organization is getting organized around iterative, incremental delivery.

Oh, and almost every annual budget line stayed exactly where it was. Leadership's happy about that, too. It all looks close enough to scaled.

Now say those 12 squads were funded from three different department budgets, each set once a year, the same way they were when the work was organized as projects. A squad working on payments still answers to the payments budget. Its plan still needs sign-off from that department's head.

In its third sprint, one squad learns that a feature nobody will use should be dropped. The team raises the flag: we don't think this needs to be built anymore. But the squad can't drop it. The feature is written into the department's annual plan, and the department head owns that plan. The change needs two department heads to agree, and getting them together takes three weeks.

In the meantime, the squad keeps building the feature. Every standup starts on time. The sprint reviews happen. All of the mechanics of iterative and incremental delivery are firing on all cylinders.

Nothing in that story is a failure of the events, and that's what I want to talk about. The standups ran, the retrospectives ran, and everyone used the new words. What didn't change is who funds the work and who decides what the work is for. The remnants of the old change board are still there, along with all the overhead it takes to coordinate one. New names, same budget lines, and the people who fund the work are still nowhere near it.

What the State of Agile Survey Says

If you've been counting scaled teams as scaled agility, the survey's answers sit on both sides of a line I want to draw.

The source this week is one we've talked about a lot: Digital.ai's State of Agile Report, the 2025 edition and the 18th one overall. I hope the next one comes out soon. Keep in mind that Digital.ai sells agile planning software. 349 agile practitioners answered the survey, mostly coaches and consultants at large enterprises, and they're describing their own organizations.

How Deep Agile Runs

Start with how deep agile runs. 13% say it's deeply embedded across business, technology, and supporting functions, with work aligned to strategic outcomes.

That's a high bar. Deep across business, technology, and support, and tied to strategic outcomes, all in one answer. That is really hard to do, no doubt. So I think part of why the number is low is the wording, and I still think it's a valuable way to look at it.

Look at the other answers to the same question. 25% say agile is practiced across some departments, but usage is inconsistent. 22% say it's scaled across IT, with business involvement still small. And 20% say it's limited to team-level execution, which is also common.

Where the Investment Went

The same survey asked about investment. 41% said their organization's investment in scaling agile increased over the past 12 to 24 months. Not everyone went that way: 24% said it decreased, and 27% said it stayed about the same.

I want to be careful here. The 41% and the 13% come from two separate questions. We can't tell whether the respondents who reported more investment are the same ones who said agile is deeply embedded. The report doesn't say, and it's hard to deduce.

Side by side, though, the two numbers still frame this whole discussion. On one question, 41% of respondents said investment in scaling agile went up. On a different question, 13% said agile is deeply embedded across business, technology, and supporting functions. Hold on to both.

Mechanics vs. Structure

That gap led me to start thinking about mechanics and structure. A scaled framework and a scaled organization can look identical from the conference rooms where we present all of this. So I separate them into two lists.

Mechanics are the parts you can install, and they're what a lot of us focus on: team names, event calendars, roles, boards, the tool everyone logs into. Teams need those things. I'm not saying they don't matter.

Structure is who funds the work, who owns the outcome end to end (an important distinction), and who can decide without asking a whole other silo of people.

Everything on the first list can change within a quarter. Those are easy things to do, and you can buy some of them off the shelf. The second list is much harder, because changing it moves power. Someone gives up a budget line. Somebody loses a sign-off and the oversight that comes with it. In the organizational hierarchy of traditional corporate America, in my experience at least, that gets complicated fast.

Where Scaling Usually Starts

I was part of an organization that was trying to scale. I say "trying" because you never arrive.

It's very common for a transformation to begin in the engineering organization, and so we tend to optimize for the engineers at the expense of everything else. That's been a great learning experience for me. Most agile transitions take shape around that structure, and I always find myself standing against that gravity to make sure we optimize for the end user. It's a lonely island out there, I promise you.

The deeper lesson is that we have to organize around common stakeholders who can roughly align on a product team's priorities, as opposed to a project team's. This is often called the product operating model, which Marty Cagan describes as organizing teams around products and value streams, with common stakeholders, end to end. Remember that phrase. I keep coming back to end to end.

This organization decided the word "scale" meant building teams around the IT departments that supported each business function. It was more important to charge the teams' hours to projects and report ROI to each business than to remove the friction of teams with lots of dependencies and handoffs and give them room to adapt to their stakeholders' needs. That's hard.

It was heading in the right direction, but it wasn't quite there, and it could end up worse if nobody catches it or plans for it. Notice where they wanted to optimize: tools, tracking, function, skill set, utilization, and finance. Those are the internal mechanics of an organization. None of them are about delivery.

Copy the Surface, End Up With Debt

A few weeks back, we talked about code that gets copied instead of restructured. This is the same type of failure, a level or two up. Copy the surface, skip the hard restructuring, and you end up with debt.

When an organization standardizes the mechanics across its silos, the silos get a common vocabulary. They don't necessarily get a common budget or a shared outcome. That takes a lot more work.

I've learned to start with funding and decisions right from the get-go, along with the stakeholder grouping that determines how we organize and optimize teams. The mechanics will be there for everyone to see later. If we don't start with the product stream or the value stream, the structural problems don't show up until much, much later.

So my advice is to go look at the structures. If they didn't move, you'll be able to find where the old organization is still holding on. Those spots are pretty easy to identify once you look from that angle.

Where the Silo Lives

The survey gets close to this in one of its questions. It asked what role business and executive leaders play in guiding agile practices.

33% of respondents said agile is treated as a delivery function rather than a strategic lever. That matches my experience. 24% said agile is driven from the bottom up with minimal executive involvement, and that's not going to go well either. Then again, sometimes executives buy into agile just because they hear "fast," and that can be dangerous too. Only 15% said business and executive leaders actively shape and sustain agile practices. We've cited that one before. It's where you want to be, and it's the lowest number on the list.

Remember who answered: agile practitioners describing their leaders. These aren't leaders describing themselves, and the numbers would probably look different if they were.

Look again at the 24%. Those are leaders who aren't in the room, as opposed to leaders directing teams. But absent from the practice isn't the same as absent from the money. Leaders can hand the practice to the teams and keep the budget and the big decisions for themselves. That's the pattern I'd look for. Otherwise, they'll run away from a job that requires them to be closely involved.

The Checkout Squad

Go back to the 12 squads and the payments work. Say one squad owns the checkout experience. Its backlog says so. Its sprint reviews show checkout work.

But the money for checkout features sits in the payments department's annual budget, over in finance. That department's head decides whether the checkout plan changes. And that person is probably watching reconciliation and reporting more than the user experience.

On paper, the squad owns checkout. In practice, a silo still owns the budget. The squad depends on that silo and probably doesn't interact with its people very often.

That squad will look scaled on every report. It runs its events and keeps its own cadence. It just can't stop building something without going up a chain that isn't heavily involved in customer discovery. What we're really trying to do in software development is build things for end users, and organizations get very distracted from that.

"We Don't Even Run a Framework"

You might be thinking your organization doesn't run a framework anymore, so none of this applies. I hear that a lot, and it's a fair point.

The same survey shows plenty of variety in approaches. Asked which frameworks and delivery models they use, 48% chose a blended or hybrid model, 44% chose SAFe (the Scaled Agile Framework is very popular), and 26% chose a homegrown framework or operating model. Respondents could pick more than one, so the numbers don't add up to 100. We've cited the hybrid and homegrown figures before. And 7% said they don't follow a mandated scaling model at all.

So this isn't a story about one framework. I'm certainly not interested in ranking them and having framework debates ad infinitum. I'm tired of it. Hybrid models are common. So is SAFe. So is your own homegrown approach. None of it matters as long as you're achieving agility, which is something we spend a lot of time on in our classes.

A hybrid model can standardize the mechanics just as well as a named framework can, and a homegrown playbook can rename the teams too. The question is whether the model you picked actually touched funding, ownership, and decision rights, or whether it only touched the vocabulary and the mechanics.

Leadership cue
Before you report the next scaling milestone, pick one unit and answer three questions: has the way its work is funded changed, does it own an outcome end to end, and can it change what it's building without a sign-off from outside? If all three answers are "nothing changed," start the next conversation with whoever holds that budget.

The Silo Test

That question is what a tool I built this week helps answer, or at least get started on. I'm calling it the Silo Test.

You can't fix a structure you haven't separated from its mechanics, so I start by separating them. These days, when I take on an agile transformation, I usually start with organizational design, because I've been burned so badly by skipping it.

The worksheet runs on one unit. That can be one team or a group of teams; it's totally up to you.

Step 1: List Everything That Changed

List everything that changed when the unit was scaled: names, events, roles, tools, budgets, approvals. All of it goes on the list.

Step 2: Sort Each Change Into Two Columns

Sort each change into one of two columns. Was it mechanics, or was it structure? The definitions above are your cheat sheet.

Step 3: Ask Three Structural Questions

For whatever landed in the structure column, ask three questions about the unit, and answer each one "changed" or "nothing changed."

Funding: Has the way the unit's work is funded changed since you scaled?

Ownership: Has the team come to own an outcome end to end, or does it still work through a lot of handoffs and dependencies between departments?

Decision rights: Has the team gained the right to change what it's building without a sign-off from someone outside? By "the team" I don't just mean the developers. If you're scaling agile, product management, developers, and agile coaches are all working together.

Step 4: Read the Columns Side by Side

If every change sits under mechanics, the unit was renamed, not restructured. That's useful to know. It isn't a verdict on anyone. It's a starting point for making sure your transformation and organizational design efforts are on the right track.

Step 5: Pick One Structural Change

Pick the one structural answer you'd change first. You can't change everything at once. Then write down who would have to agree to it.

Run the checkout squad through it. Its mechanics column is probably full, and its structure column is likely empty. All three answers come back "nothing changed," and all three point at the payments department. That's where the conversation should start.

The full worksheet goes up here on the blog on Wednesday. Run it on a team, a group of teams, or a whole product grouping.

When you sort your own unit, which structural question comes back "nothing changed"? Is it funding, ownership, or decision rights? I'd love to hear what you find.

Renaming the Standup Doesn't Dismantle the Silo

The next time someone tells you the framework is scaled, ask what actually changed. Renaming the standup doesn't dismantle the silo that might be sitting underneath it.

This one might have hit close to home for some of you. If you've made real structural progress, celebrate it. Then get back to work, because transformation work never really ends. Prioritize the problems, roll up your sleeves, and model the behavior you want from the organization yourself.

Next week, I'm continuing this thread with product discovery and what happens when it falls behind delivery, including something I call the planning ladder.

If you're working through the structural side of a transformation and want help with organizational design, funding, and decision rights, take a look at our upcoming classes and workshops.