The Roman Legion's lasting power didn't come from luck or individual bravery. It came from a well-designed system of collaboration that always put collective effectiveness first. Their battles weren't chaotic brawls. They were disciplined displays of teamwork, a true blueprint for any group aiming for consistent, superior results.

The success of a Roman army relied not only on the quality of its troops but also on their ability to coordinate effectively, ensuring precise execution of formations in battle.

A. The Legion's Formations: More Than Just Lines

When we think of Roman armies, we often imagine a rigid block of soldiers. But the reality was far more sophisticated. Take the Triplex Acies (triple battle line), their most common and effective formation, was a masterclass in controlled flexibility. Legionaries didn't just line up shoulder-to-shoulder. They arranged themselves in a staggered, checkerboard pattern. This created crucial gaps between units in the front line.

These gaps weren't weaknesses. They were vital for adaptability and resilience. They allowed lighter skirmishers to dart forward to harass the enemy and then retreat safely. More important, they provided room for the legion to breathe. Tired or injured units from the front line could pull back and be replaced by fresh troops from the rear without breaking the formation. This dynamic structure meant the Roman Legion was a living, moving entity, not a static wall.

The Triplex Acies (or "Triple Battle Line") was a highly effective and dynamic formation. Its power came from three core principles, each of which has a direct equivalent in successful Agile collaboration.

Here is a breakdown of the principles and their Agile equivalents:

1. The principle of staggered lines and fluidity

Triplex Acies: The formation consisted of three lines of soldiers (hastati, principes and triarii), arranged in a checkerboard pattern. The gaps in the front line were not a weakness but a deliberate feature that allowed tired units to retreat and be replaced by fresh troops from the rear. This made the formation incredibly resilient and capable of sustained effort.

Agile equivalent: The agile principle of cross-functional teams and knowledge sharing. Just as the Roman legion could rotate a tired soldier and maintain a solid front line, an agile team should not be reliant on a single "hero" or expert. If one team member is on vacation, gets sick, or hits a roadblock, another team member (from the second or third "line" of skills) can step in. This prevents bottlenecks and ensures the team maintains its pace and quality, even when a core member is temporarily unavailable.

2. The principle of focused Specialisation with a unified goal

Triplex Acies: The three lines had different roles:

• Hastati (the first line) were younger, less experienced soldiers, acting as the initial shock troops.
• Principes (the second line) were the most seasoned and capable soldiers, who would engage when the first line began to tire or fall back.
• Triarii (the third line) were the veteran soldiers, forming a final, unyielding reserve line to be used only in the most desperate situations.

While each group had a specific role and level of experience, they all operated with the unified goal of advancing the legion and winning the battle. Their individual specialisation served the collective purpose.

Agile equivalent: This mirrors the agile principles of specialisation within the team with a collective "sprint goal." Your team might have a front-end expert, a back-end expert and a QA specialist. Each person has a unique skill set (like the hastati vs. triarii), but everyone's work is aligned with the single, unified sprint goal. No one says, "That's not my job" if the front-end specialist is overloaded; the back-end developer or a QA member may step in and help. The diverse specialisations are a strength that the team uses to achieve its collective objective.

3. The principle of disciplined adaptability and reserves

Triplex Acies: The presence of the principes and especially the triarii as a reserve was crucial. The Roman army knew that a battle was rarely won with the initial push. The reserve lines provided a powerful force for a second, decisive push, or an impenetrable defense when needed. This disciplined use of reserves meant they were never overcommitted and could always adapt to a changing battlefield.

Agile equivalent: This reflects the agile practice of managing work in progress (WIP) and having a clear backlog. Overcommitting to a sprint (throwing all your soldiers at the problem at once) is a recipe for failure. A healthy backlog acts as your "reserve line." When a new, urgent task comes in that threatens the current sprint, the team has the discipline to stop, assess the new "threat," and decide if they need to pull from their backlog to address it, or if they have the capacity to handle it without breaking their current sprint goal. The team doesn't exhaust itself in one frantic push; it maintains a healthy, sustainable pace, knowing it can adapt when necessary.

Beyond the standard, Romans drilled for specialized tactics like the impenetrable testudo (tortoise) for sieges, the focused cuneum (wedge) to break enemy lines, or the defensive orb (circle) when surrounded. Each was an example of drilled adaptability. This shows that effective collaboration means knowing your role in a dynamic system, not just sticking to one fixed shape.

The Testudo (or Tortoise) formation was a unique Roman tactic that demonstrated a powerful principle of collaboration: shared protection and collective risk.

Here’s a breakdown of its principles and their Agile collaboration equivalents:

1. The principle of collective protection and shared shielding

Testudo: This formation was used primarily during sieges. Legionaries would lock their shields together, not just in front, but also on top, creating a near-impenetrable "shell." This protected the entire unit from missiles and projectiles raining down from above and around them. No individual soldier's shield was enough on its own; their survival depended entirely on the synchronized, coordinated effort of everyone locking their shields together.

Agile equivalent: The agile principle of a shared definition of "done" and quality standards. Just as the testudo protected the legion from external attacks, a robust and shared definition of "done" protects an agile team from external pressures and the risks of technical debt. When a team collectively agrees on what "done" means (e.g., code is reviewed, tested, deployed and documented), they create a collective "shield." No single team member can cut corners without compromising the integrity of the whole. This shared standard protects the team from quality issues, bugs and rework, which are the "missiles" of the modern development world.

2. The principle of focused forward motion

Testudo: The formation was slow, but it allowed the legionaries to advance deliberately and safely towards a fortified objective, such as a city gate or a wall. The entire unit moved as a single, protected mass, relentlessly pushing forward despite the bombardment. The focus was not on speed, but on methodical, protected progress toward a defined goal.

Agile equivalent: This is a perfect parallel to deliberate, steady and sustainable progress in a sprint. A well-functioning agile team, focused on its sprint goal, moves forward methodically. It's not about frantically rushing to a finish line, which can lead to mistakes and burnout. Instead, it's about making consistent, protected progress every day. The team collectively manages its workload, identifies and removes blockers and ensures that everyone is moving together towards the goal, just as the testudo moved as a single entity towards the fortress.

3. The principle of shared responsibility and trust

Testudo: Every single soldier had a critical role. If even one person failed to hold their shield steady or in the correct position, they could create a weak point that would compromise the safety of the entire formation. The soldier on the outside of the formation was no less important than the one in the center; they all had to trust their comrades implicitly to hold their position and provide full coverage.

Agile equivalent: This directly relates to the agile principle of collective ownership and accountability. In an effective agile team, everyone is equally responsible for the success or failure of the sprint goal. There's no room for "not my problem" thinking. If one team member's work is blocking another, the team is collectively accountable for resolving it. This requires a high degree of trust—that your teammates are doing their best, will speak up when they need help and will do their part to protect the team's progress and quality.

The Cuneum (or Wedge) formation was a Roman tactic designed for a single, aggressive purpose: breaking through an enemy's line.

Here’s a breakdown of its principles and their Agile collaboration equivalents:

1. The principle of focused power and concentration

Cuneum: The formation was shaped like a spearhead, with a small number of elite, well-shielded soldiers at the very front. The ranks behind them progressively widened, with the entire formation pushing behind the point. This concentrated the collective force of the entire unit onto a single, narrow point in the enemy's line, making it difficult for the opposing force to withstand the pressure.

Agile equivalent: This is a strong parallel to the agile principle of focused effort and specialisation to solve a key problem. In a team, this means having the right person (the "point of the wedge," with the specialized knowledge) lead a task while the rest of the team supports them. For example, a senior developer might take the lead on a complex, high-risk technical challenge, while the rest of the team focuses on supporting tasks, testing and clearing dependencies. This concentrates the team's intellectual and technical power on a single point to break through a significant obstacle or deliver a high-priority feature.

2. The principle of mutual support and momentum

Cuneum: The soldiers in the wedge formation weren't just following. They were actively pushing, with each rank providing the momentum and pressure for the rank in front of them. The forward momentum of the entire unit was what made the point of the wedge so effective. Without the sustained push from behind, the front would falter and be overwhelmed.

Agile equivalent: This reflects the agile practice of active support and removing blockers to maintain momentum. In a sprint, the "wedge" is the most critical task or feature that the team is trying to complete. The rest of the team's work is to support that task's forward momentum. This means actively helping the person leading the task, removing any impediments and ensuring their path is clear. It's not about passive waiting; it's about a collective, proactive push to ensure the high-priority item is delivered. The daily stand-up, for instance, is the perfect opportunity to ensure the "wedge" is moving and to address anything that might slow it down.

3. The principle of a clear, shared objective

Cuneum: Every soldier in the wedge, regardless of their position, knew exactly what the formation's goal was: to punch a hole through the enemy line. This simple, clear objective meant everyone's effort was aligned in a single direction. There was no confusion or ambiguity about the purpose of the maneuver. 

Agile equivalent: This is the agile principle of a singular, well-defined sprint goal. The entire team must be aligned on what "success" looks like for the sprint. If the team's objective is to "launch the new login feature," then every single task, every decision and every discussion should be aimed at achieving that goal. Just as the Roman wedge's power came from its singular focus, an agile team's power is multiplied when everyone is pushing in the same direction toward a clear, shared objective.

Below: Video clip from "Rome" tv series showing the importance of coordination and discipline in battle. Gauls were Celts located in modern-day France, Belgium as well as parts of Switzerland and northern Italy. 

Warning: Contains violent content!

In essence, Roman formations weren't just static arrangements; they were dynamic tools for collective action and adaptability on the battlefield.

B. The power of rotation & resilience

Here lies a profound lesson for modern teams: the Roman understanding of energy management and continuous cover. Romans knew even the strongest soldier would tire. Their system didn't push individuals to collapse. It was about sustaining collective effort.

When a legionary was tired, wounded, or just needed a moment, they seamlessly rotated out of the front line. A fresh, equally trained soldier immediately stepped into their place, keeping the shield wall unbroken. This wasn't a chaotic swap; it was a practiced, disciplined maneuver. This continuous rotation allowed the Legion to absorb immense pressure. They fought for long periods, wearing down opponents who relied on individual bursts of energy. This wasn't a "one-and-done" battle where victory hinged on a single, unsustainable push. The Roman system was built for endurance, for long campaigns, for maintaining peak performance over time. This is a crucial distinction for teams aiming for continuous delivery and long-term success.

The ability to rotate effectively meant the Roman Legion could maintain intensity and effectiveness far longer than its adversaries.

C. Cohesion over individual glory: The peril of the "Superstar"

This deep coordination, discipline and adaptability demand solid team cohesion. In such a system, there is less room for "superstars." This isn't because individual talent isn't valued. It's because individual glory at the expense of the collective is a fatal flaw.

Imagine a Roman legionary, a formidable warrior, who decides to break formation and act as a "battle maniac." He seeks personal duels or individual kills. While his bravery might seem impressive, in the phalanx, this action would be disastrous. A gap opens in the shield wall, creating a vulnerability the enemy can exploit. His sudden, unplanned movement throws off his comrades' rhythm and coordination. Crucially, his colleagues can no longer depend on his shield being where it should be.

The Roman system, focused on the interlocked scutum (shield) and the efficient gladius (short sword), was for unified action, not individual heroics. Roman military discipline was strict. Breaking formation could lead to severe punishment, precisely because of the immense danger it posed to the entire unit. For the Romans, discipline prioritized the formation's integrity and the collective over any single soldier's heroics. Success was a shared achievement; failure, a shared consequence of broken cohesion.

Just as a gap in the shield wall invited disaster for the Roman Legion, a lack of true cohesion can undermine even the most talented modern team – the ancient equivalent of a ‘No d*ckheads’ policy. 

Fast forward two millennia and our modern professional world demands similar agility and collective power. This is why frameworks like Agile and Scrum are so popular. They promise adaptability, iterative delivery and quick responses to change – all vital in unpredictable markets. Scrum, with its defined roles, events and artifacts, offers a structured way to achieve these promises. It empowers teams to deliver value consistently.

A. The allure of Agile & Scrum

The appeal is clear: In a world where requirements shift rapidly and customer needs evolve daily, the ability to inspect and adapt, deliver working products frequently and embrace change offers a significant competitive edge. Scrum provides a lightweight, empirical framework. It helps complex product development teams navigate uncertainty and continuously deliver value. It lays out a clear rhythm, roles for accountability and ways to ensure transparency.

According to the 17th State of Agile Report, "improved collaboration" and "better alignment to the business" are consistently cited as top benefits from using Agile, with almost 60% of survey takers reporting improved collaboration.

B. The superficial trap: "Dailies and Roles" aren't enough

However, many organisations falter here. They fall into what we call the "Superficial Scrum Trap." They adopt the ceremonies and assign the roles – Scrum Master, Product Owner and Developers – but miss the profound collaborative mechanics underneath. They schedule the Daily Scrum, hold Sprint Reviews and conduct Retrospectives. But these often become mere status updates, passive demos, or just gripe sessions.

The dangerous misconception is that collaboration is simply holding daily stand-ups or giving someone a title. This superficial adoption misses the deeper, critical elements that make Scrum truly powerful. Without understanding the fundamental shift in how teams must interact – how they build collective responsibility and how they truly commit to each other's success – these activities become mere rituals. They lose the very collaborative energy they're meant to foster. For example, if a "Daily Scrum" is just each person reporting to the Scrum Master instead of the team planning together, it's a wasted opportunity for real collaboration. You might have all the right pieces on the board, but if they're not moving with purpose and precision, you're not playing the game effectively.

Consider a project where, despite the team's best intentions, "too much unsaid in the name of psychological safety" led to loose discipline and slower progress. Issues that should have been addressed directly lingered, causing avoidable delays. This highlights that while safety is crucial, it must be paired with active, honest communication to prevent complacency.

C. The Scrum Master: Architect of team mechanics

If the Roman General was the Product Owner (setting the strategic objective) and the legionaries were the Development Team (doing the work), then the Scrum Master is the Architect of the Team's Mechanics. They aren't a commander giving orders, nor a soldier in the fight. Instead, the Scrum Master constantly observes, refines and optimizes how the "phalanx" itself operates.

Their role is to facilitate the seamless "rotations" we saw in the Roman Legion. They ensure that if a team member is on leave, ill, or needs a break, others can seamlessly step in. This comes from cross-training and shared knowledge. They ensure the "shield lock" is efficient by removing impediments that block the team's flow, communication, or cohesion. Crucially, the Scrum Master ensures the "rules of engagement" are understood and followed – not the rules of war (the external market or product strategy), but the rules for how the team collaborates internally. This includes how they communicate, make collective decisions, manage their work, handle conflicts and continuously improve their process. They are the guardian of the how, empowering the team to move as one, a truly formidable force.

The Scrum Master guides the team to build the muscle memory for effective, results-driven collaboration, much like a drill sergeant honing a legion's movements.

This brings us to the most crucial, often unstated, dimension of effective collaboration in Scrum and beyond. The Scrum Guide provides the framework, roles and events – the container for collaboration. But it doesn't explicitly dictate the content of that collaboration, nor how it truly flourishes.

A. Beyond a moment it's a movement

Here's the fundamental truth: Collaboration isn't a "one and done" event, nor a switch you simply flip on. It's not just about attending a daily stand-up or brainstorming. Instead, it is a dynamic, evolving pattern of interactions, built through continuous practice, shared learning and collective commitment. Think of it as the muscle memory of the Roman Legion – not an instruction given once, but a fluid, responsive capability forged through countless drills and actual combat.

This consistent process allows the team to mature beyond just coordinating tasks. It's the alchemy through which the "whole" of the Scrum Team, acting as a unified, self-managing entity, consistently becomes greater than the mere sum of its individual parts. It's the difference between talented musicians playing alone and a world-class orchestra performing a symphony.

B. Pillars of deep collaboration (beyond the explicit Scrum framework)

While Scrum offers the scaffolding, the following "pillars" are the behavioral and cultural foundations for true, deep collaboration:

• Continuous Interaction & Shared Learning: Just as Roman legionaries constantly drilled and learned from each skirmish, effective Agile teams develop their unique "patterns of delivery" through relentless, continuous interaction. This includes pairing, mob programming, mutual teaching and constant feedback. This is where multi-disciplined individuals truly shine. Their willingness to share knowledge and learn new skills not only builds individual capability but also creates a strong safety net for the team, making "rotations" seamless. It's a shared commitment to collective mastery.
• Collective Ownership & Accountability: In a truly collaborative team, everyone owns the outcome. There's no room for "that's not my job" or blaming. Like legionaries depending on each other's shields for survival, every team member understands their interdependence. They celebrate success together; they own and learn from failures as a unit. This builds a real sense of shared responsibility and a proactive drive to support one another, ensuring no "shield" ever drops.
• Disciplined Adaptability: Romans weren't just disciplined in holding a line; they were disciplined in changing that line on command, adapting to new terrain or enemy tactics. Similarly, Agile team members aren't just multi-skilled; they are disciplined in applying those skills within the team's evolving patterns to achieve results. This means a willingness to pivot, to re-prioritize, to learn new tools and to collectively solve problems, all to deliver value. It's about responding to new "battlefield" situations while staying cohesive and focused.
• Cohesion as a Force Multiplier: Strong bonds, mutual trust and a shared purpose amplify effort. When team members truly respect and trust each other and feel safe being vulnerable or giving honest feedback, their individual efforts multiply. This isn't just about "getting along." It's about a deep sense of unity. This allows the team to weather storms, solve complex challenges and innovate together. It creates an unstoppable force that far exceeds what any sum of individual talents could achieve. For example, consider a project where technical experts openly challenged each other, being clear about what they did and didn't know. This fostered trust and led to rapid problem-solving and higher quality, proving that the synergy of skilled individuals combined with strong team cohesion truly works wonders.

The Roman Legion didn't dominate the ancient world through brute force alone, nor by relying on individual heroes. Their lasting success came from disciplined, well-drilled and highly cohesive collaboration. They understood that strength came from a system designed for collective action, sustained effort and mutual support.

This is the profound lesson for our modern, complex world. True collaboration, whether within an Agile Scrum framework or any other team structure, is far from a casual affair or a simple checklist of roles and meetings. It is a deliberate, practiced, and deeply ingrained pattern of interaction. It's the daily practice, the shared understanding, and the collective commitment that allows a group of individuals to transcend their separate parts and become a formidable, unified force. It's the resilience to rotate, the discipline to hold the line, and the unwavering trust that your comrades' shields will be there.

For too long, we've perhaps settled for "collaboration" that's "about feelings" or merely the outward performance of ceremonies. But in an environment that demands constant adaptation and consistent delivery, it's time to ask ourselves a challenging question:

Is your flavor of collaborative "Scrum" a mere sequence of ceremonies, or a powerful engine of collective will, meticulously engineered for results?

Reflect on your own team. Are you building a loose collection of individual warriors, or are you forging a truly unstoppable modern phalanx?

Action Steps: Forge your team's phalanx

Ready to transform your team's collaboration from ritual to results? Here are concrete steps you can take:

1. Cultivate cross-training: Actively avoid over-reliance on your strongest players. Identify the most frequently used skills and schedule dedicated time for knowledge sharing and cross-training. This builds resilience and ensures anyone can cover essential work.
2. Unpack bottlenecks in retrospectives: When delays or bottlenecks occur, don't just note them. Deeply discuss why they happened in your retrospectives. Focus on team process improvements, not individual blame, to ensure collective learning.
3. Champion candor with clear rules: Foster an environment where honest, transparent communication is the norm. Encourage direct feedback and challenge, but ensure there are agreed-upon "rules of engagement" for how this feedback is delivered constructively, preserving team cohesion.
4. Monitor team dynamics: Regularly check the pulse of your team's interactions. Are discussions stagnant? Is communication flowing freely, or does it feel slow and indirect? Being alert to subtle shifts in dynamics allows for early intervention by the Scrum Master or team members.
5. Define Shared Success: Go beyond individual tasks. Ensure every team member understands and commits to the collective definition of "done" and the shared outcome. This fosters a true sense of collective ownership.

What "mechanics" have you found most crucial in fostering this deeper, more results-driven collaboration? Share your insights and experiences – let's learn how to build teams that don't just work, but conquer.