Owners who run EOS often ask whether they should “do Agile” too. Teams that run Scrum often wonder why the owner keeps talking about Rocks. Both groups are asking the right question: how do these fit together?
The short answer: they do different jobs.
Two different jobs
EOS — the Entrepreneurial Operating System created by Gino Wickman — is a whole-company operating system. It answers company-level questions: where are we going, who owns which seat, what are the company’s priorities this quarter, how are we doing this week, and how do we solve issues? See what is EOS.
Agile — Scrum, kanban and related methods — is a team delivery approach. It answers team-level questions: what are we building next, how do we break work into small pieces, how do we coordinate daily, and how do we improve our process? See agile for business.
| EOS (or another business OS) | Agile (Scrum, kanban) | |
|---|---|---|
| Level | Leadership team, whole company | Delivery teams |
| Planning cycle | Annual and quarterly | Sprints of weeks, or continuous flow |
| Core meeting | Weekly leadership meeting | Daily stand-up, sprint planning, review, retro |
| Priorities | Company and leader quarterly priorities | Backlog ordered by value |
| Measures | Weekly company scorecard | Sprint goals, velocity or flow metrics |
| Problem-solving | Issues list solved weekly | Impediments removed; retrospectives |
Where they overlap
Both believe in:
- Short planning horizons. Ninety days for EOS, a few weeks for sprints.
- Regular inspection. Weekly scorecards; sprint reviews.
- Solving problems openly. The issues list; retrospectives and impediment removal.
- Clear ownership. One owner per Rock; one Product Owner per backlog.
That shared DNA is why they work well together when layered correctly.
How to run both
Here’s the pattern I recommend for small and mid-sized companies:
- The company operating system sets direction and priorities. Quarterly planning produces company and leader priorities.
- Each department leader turns their priorities into backlog items for their team.
- Teams deliver through sprints or kanban. Their ceremonies stay inside the team.
- Progress rolls up. The department leader reports priority status and key numbers in the weekly leadership meeting.
- Cross-team issues go to the leadership issues list. Team-level process problems stay in the team’s retrospective.
Mapping the vocabulary
Teams waste energy translating terms. Agree on a simple map:
- Company or leader quarterly priority → one or more epics or large backlog items.
- Weekly scorecard measure → may include team flow or delivery numbers.
- Leadership issues list → for cross-team or company issues.
- Team retrospective → for how the team works.
Write the map down and share it.
When Agile alone isn’t enough
Some fast-growing teams try to run the whole company on Agile ceremonies. They often end up with great delivery and no clear company direction, unclear seats and no leadership scorecard. Agile assumes someone is setting the priorities — a business operating system is how a company does that well.
When EOS alone isn’t enough
Some EOS companies have delivery teams struggling with complex project work: missed deadlines, half-finished work, endless rework. A Rock with one owner doesn’t tell a team how to deliver a large, uncertain project. Scrum or kanban fills that gap.
The same logic applies to other systems
Replace EOS with Scaling Up or my BOSS framework and the pattern holds: the company operating system sets direction and quarterly goals; Agile teams deliver; progress rolls up to the weekly leadership meeting. In BOSS, Quarterly Goals break into projects on a board, which is a kanban habit by another name. See business operating system and kanban for small business.
Signs the two are colliding
- People don’t know which list of priorities is real.
- Team members attend too many meetings.
- Leaders override sprint commitments mid-sprint with new priorities.
- Leadership scorecards and team metrics tell different stories.
Each of those is an issue for the leadership team to solve — usually by clarifying who owns priorities at each level.
A note on trademarks and affiliation
EOS and its related terms are trademarks of EOS Worldwide. I’m not an EOS Implementer or affiliated with EOS Worldwide; I explain how EOS and Agile fit together so teams can make good choices.
A simple test after one quarter
After running both for a quarter, ask three questions. Did company priorities get finished? Did teams feel they had the focus to deliver? Did anyone attend a meeting they didn’t need? If the first two answers are yes and the third is no, your layering is working. If not, revisit who owns priorities at each level and trim the meetings that overlap.
Next steps
If you’re running EOS and your delivery teams are struggling, pilot Scrum or kanban with one team. If you’re running Agile teams with no company-level rhythm, start with a weekly leadership meeting. If you’d like help designing how the layers connect, request a strategy call.
Questions people ask
Is EOS agile?
EOS shares some Agile ideas — short planning cycles, regular reviews, a focus on solving issues — but it’s a whole-company operating system, not a team delivery framework like Scrum or kanban.
Can a company use EOS and Scrum together?
Yes. A common pattern is EOS (or another operating system) at the leadership level setting quarterly priorities and running the weekly leadership meeting, with Scrum or kanban used inside delivery teams to execute the work.