What Agile Organizations Can Learn from Greece
I visit Greece every now and then. Beyond its beauty and hospitality, Greece also offers a surprising mirror to anyone working in agile delivery. From small family hotels to national governance, I saw the same forces that either empower or paralyze agile projects: learning, ownership, feedback, and adaptation. I’m building the story from the individual to the institutional.
1. People: The Limits of Static Roles
This time I stayed at a small family-run apartment hotel, that I had visited over the years. Their business was good, despite the post-covid tourism dump that still exists.
At the hotel, I met the same cleaning ladies I had seen there fifteen years ago. They were still doing identical tasks, still unable to speak any English, probably on the same pay level. Career development is not a concept there.
Learning: Static roles limit growth, even if the daily work gets done. In agile projects, continuous learning and skill mobility are essential. Encourage development paths, role rotation, and self-improvement. Stagnation is the enemy of agility.
2. Grit: Doing Hard Things Without Knowing How
The hotel’s late founder had literally built it himself in the 1980s. He was not an engineer or architect, but he saw tourism rising and decided to act. He even dug the hotel’s own 16-meter-deep water well by hand. He built first, learned as he went, and iterated over decades.
Learning: Courage and ownership often outweigh initial expertise. Agile delivery thrives on teams that commit in the face of uncertainty. Grit, or the willingness to persist and learn, beats perfect planning.
3. Requirements: Learning While Building
The hotel showed odd combinations — outdated facilities next to ingenious usability details and small safety innovations clearly added over time. You could see the learning curve in concrete form. The builder had adapted the design as he learned from real guests, long before “agile” became a word in software.
Learning: Requirements emerge through use. Don’t lock down scope too early. True value appears only when the product meets real users and evolves through their feedback. Good agile managers protect emergence.
4. Governance: Centralization Kills Local Ownership
At the macro level, Greece tells a darker story. After the 2008 global financial crisis, EU-pressure was high, and admin structures were centralized to resemble Germany’s federal model. Islands that once managed their own affairs were grouped under larger regional authorities.
In the Dodecanese, for example, Rhodes became the governing hub for all nearby islands. Local municipalities lost control over land and beaches. When multinational hotel chains want to build, they negotiate with the authority in Rhodes, not with the local island. Profits flow abroad to the multinational hotel chain’s HQ. The local communities are left with little income and capacity even to clean roadsides. The result is disillusionment and loss of trust. Locals no longer believe their voice matters.
Learning: In scaled agile environments, governance must empower, not centralize. Solution- or release trains must ensure team level influence in planning. When decisions are made too far from the work, local ownership dies, and the system’s energy drains away. True agility distributes decision-making to where information lives.
Summary
Greece reminds us that social systems decay when learning, courage, and local decision-making disappear. Agility is not a process to install, but a cultural shift that needs to be maintained. AI alone cannot do it. We need leadership at every level, from management, to agile coaches, to fluent leadership within the teams.
Just like that old hotel, built by hand and improved year after year, every agile team-system must keep learning how to build itself better.
