The Disciplined Agile tool kit, unlike most agile scaling frameworks, does not insist that sub-teams/squads within a program follow the same iteration/sprint cadence (or even that sub-teams follow an iteration-based lifecycle). What we mean by that is that the squads don’t need to necessarily all have the same sprint length. For example, one sub-team may have a one-week iteration length, five sub-teams have a two-week iteration length, and two sub-teams follow DAD’s continuous delivery life cycle which doesn’t have iterations at all. Or you may find a program where every sub-team has two-week iterations. Or a program may choose to have all teams take a continuous delivery approach. Each of these strategies make sense in certain situations, but none of them make sense in all situations. There is no single “best practice” – Context counts.
The Coordinate Activities process goal includes advice for how to coordinate within a program team, as you can see in Figure 1. Coordination across a program, a team of teams, typically requires you to implement several strategies. The cadences followed by your sub-teams will affect when it makes sense for them to coordinate.