Pod Insights The Agile Daily Standup - AgileDad The Concept of Scrum Fluid Teams About this episode The Concept of Scrum Fluid Teams
Fluid Scrum Teams are a concept introduced by Willem-Jan Ageling, where a stable group of individuals (e.g., 20 members) self-organize into smaller, temporary teams each Sprint to address specific objectives. This approach allows for flexibility and adaptability, as team compositions change based on the current needs of the projects at hand.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 A recent student asked me to record an episode on fluid scrum teams. Now, this is a concept that honestly, I thought I knew what it was, but I wanted to do some research to make sure I wasn't too far out of the park. So, fluid scrum teams are a concept that was introduced by William Jean-Ageling, where a stable group of individuals, let's just say 20 people or so, self-organize into smaller temporary teams each sprint to address a specific objective. So, it's almost like mobbing or swarming towards achieving something, and it gives you more flexibility and more adaptability as a team. So, as the team composition changes based on the current needs of the project at hand,
0:58 Speaker 00 they become more adept at being able to complete the work. So, from a logical perspective, it makes sense. The question is, does that much disruption cause problems with predictability? And I guess that's what I'm going to question next.
1:15 Speaker 00 In the article that was recommended that I read, the author says, "I previously described how my team responsible for delivering software projects across different business units adopted this model. Instead of forming dedicated teams for each project, we maintain a unified pool of resources during sprint planning. If a BA wanted her project to be worked on in a sprint, she worked toward defining one clear sprint goal. If we agreed within the team to have multiple sprint goals, we worked on one project per team.
1:48 Speaker 00 Team members then self-organized into smaller sub-teams to tackle each of the goals, regardless of the specific project that they originated from." So, I guess that was a little confusing, but the goals could be from different projects. The teams swarmed around covering the goals. So, the object to get your item worked on was to create the best goal. Very interesting. I see...
2:12 Speaker 00 I see where it's going, I think, but I want to make sure before I predict. So I'm going to continue. A single backlog was maintained encompassing tests from all projects. Team members volunteered for backlog items based on their expertise and interests rather than being assigned to specific projects. The team adopted a model of partial fluidity, with some members working consistently on specific projects while others shifted between tasks as needed. This adoption, the adoption of this model brought benefits such as flexibility to quickly adapt to changing projects without the need to form new teams. Rather, interaction among all team members facilitated better information sharing and collaboration. Hard pause. Okay. I see a little bit of an issue. So for me,
2:57 Speaker 00 this seems to be a great idea if you're doing something like software, where everything is defined in such a way that it can be output-led or output-driven. If you're trying to achieve a specific outcome, you may need to stay more focused on one specific area to achieve the outcome as opposed to flabbergasting between many different projects and bouncing all over the place. I also think it makes it very difficult to predict when something can be completed or when an expectation could be met. I think that if we have that type of fluidity in our goals, it causes tension and frustration. And sometimes leaders get really frustrated because they can't,
3:40 Speaker 00 you know, on one sprint, maybe a lot of things worked on, and the next sprint, nothing's worked on that project. It just, it creates some confusion. But let's see what they go on to say. Essentially, fluid Scrum teams allow the team to set focal points in sprints and create low adhesive groups to create value and work on backlog items. Say you have a pool of a dozen developers, okay? They will create a specific Scrum team for a sprint based on current requirements. Then, in the next sprint, a Scrum team might be set up by a different constellation of people. We use the idea behind this approach within one team. For example, on one sprint, a specific technology might be needed for a data product. One of the developers knows a lot about this technology and would focus with others specifically on this product backlog item.
4:22 Speaker 00 In the next sprint, the expertise would no longer be needed, and a team would create other focus groups. Okay.
4:29 Speaker 00 From getting the right person on the right job or trying to deliver things quickly, I understand, but this also creates subject matter expertise and it feels like it's also going to create silos. Um, I want to be clear, I'm not against having fluid teams. I'm not against having teams that want to learn from each other and try different things. I, I think that's all positive and a good thing, but I think the way that this is set up so far, I'm, I'm not jiving with it. Let's see what they say about sprint planning because I'm curious. So the next section says how sprint planning works in a Scrum fluid team.
5:04 Speaker 00 Okay. So there's an article that was dedicated to this. Apparently I'm not going to go through that article. It says it breaks sprint planning into three steps instead of two. Okay. Step one is pre-planning, determine possible goals and a product backlog items needed to achieve each goal. Before sprint planning starts, the product owner should already have multiple suggestions for sprinkles based on a product goal. Uh, you want to have enough sprinkles to form small temporary teams. It's helpful also have an idea of skills expected to be required to achieve each of those. Let's stop. I think it's hard enough for product owners to have enough work planned for the team to do, much less to understand the goal or objective, how that's going to impact the end consumer or achieve a specific outcome.
5:46 Speaker 00 And have a clear understanding of what technical prowess is going to be needed to do those things. This definitely calls for the need of a BAFATA and maybe their idea of pre-planning is my PO BAFATA backlog add and creation workshop, which would make sense. Uh, because that is the step before you can actually go to plan, but I would argue you also need release planning beforehand, but they kind of skipped that. Let's continue. The next step is to agree on sprinkles. The entire pool of people, Scrum Master, product owner, and all those people collaborate to determine the sprinkles. Let's stop there. I think this sounds like a major, large size extended meeting. You know, I just keep picturing a company like Microsoft where you have 511 potential backlog items that you're going to cover in this pre-planning meeting.
6:30 Speaker 00 Cause you don't know which ones are going to align with which goals and how they're going to be. Yeah. And I think that if you said, oh, if you start with the goals, then you can align that backlog items to the goals. But I still think there's opportunities for cross pollination or for people to fall into expertise pools or for silos to be done. Let's see where it goes. The final step is to organize around the goals. Now that sprinkles are defined and people have a rough idea to required skills for each goal, developers can organize themselves around the goals. I suggest doing this in several rounds. Oh, now there's multiple rounds. Round one, developers free to select which goal they want to help realize. Round two, everyone verifies the distribution of people and that it makes sense. Round three developers take the learnings to optimize their distribution over the goals.
7:16 Speaker 00 At the end of step two, we should have temporary fluid teams who signed up for sprinkles. Every sprinkle has people with combined skills to achieve the goal. I just, I'm still very concerned. Now, this might answer my question right here. Let's, let's continue. There's also a concept that's been introduced about a fluid scrum crew that can cross lateral, stable scrum teams. Ah, okay. So now we're into something. Let's pause here. So a fluid scrum crew, just based on the example they give a diagram, just based on the example is what I call a services group or services team.
7:58 Speaker 00 So if there's someone who has expertise and a capability that can drop into sprints with other stable teams and help them achieve their goals, that actually makes sense, right? But they break it down in the capability crews and product crews and scrum governance crews. It just seems like we're taking something very simple and turning it into something very complicated by overscaling it and by making it virtually impossible to have predictability. That's, that's the thing that's blowing my mind. I don't one time see here where there's a leader, an owner who says, oh, yes, this is exactly what I wanted. I mean, does it help you deliver things faster? Sure. Would help you make sure everything's aligned with a goal? Absolutely.
8:38 Speaker 00 Would help you with potential backlog item stack ranking, you know, objective stack ranking? I don't think so. I think in fact it would cause more chaos. But then they introduced the concept of a BA, a business unit leader, a product owner, a product manager, a unified business analysis. Okay, this is, this is just to me what I call straight up bloating.
9:03 Speaker 00 So there are so many people who try to fix process with process that it creates this this overwhelming amount of disdain with the team with others because there's frustration because no one wants to be part of an infinite number of meetings. So my take on this is instead of trying to do fluid teams, why don't we have well-formed teams and have teams that are, you know, both cross-functional and then other teams who are experts in what they do that can drop in and do the things that are necessary. I think we achieved the same thing. I think the only thing beneficial about this approach is that it focuses on goals and that we can align the goals with outcomes instead of outputs. And if we do that, maybe it adds some value,
9:44 Speaker 00 but I don't know that I'm a huge fan of the concept of this truly fluid unit. That's going to do it for this episode. I hope you enjoyed it. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous The February Blanket - A Story of Mae Next The Scrum That Actually Worked Page updated November 6, 2026 · transcript and summary are machine-generated