Sander Hoogendoorn is an independent dad, avid traveler, and lifelong software developer. With over 40 years of hands-on coding experience under his belt, he still ships code every day — because once a developer, always a developer.
Currently the CTO at iBOOD, Sander has led technology at companies such as ANVA, Quby, and Klaverblad, and was once Capgemini’s global agile thought leader. But don’t expect corporate buzzwords — Sander’s known for cutting through the fluff with a post-agile mindset and a healthy disregard for outdated best practices.
He helps teams and organizations break rules that need breaking — replacing heavyweight processes with lightweight thinking, and agile dogma with actual flow. If something’s slowing your team down, chances are he’s already ranted about it in a keynote.
Onstage, Sander brings code, stories, and sharp insights — whether he’s talking disruption, continuous delivery, microservices, monads (yes, really), software architecture, or the lost art of elegant code. His talks are fast-paced, thought-provoking, and never just theory.
Sander believes in small steps, critical thinking, and building stuff that works. No silver bullets. Just better software, made by better teams.
At iBOOD, we already skipped pull requests. Trunk-based development with AI-assisted review is faster, less friction, and more accountable. We didn't plan for it — it just made sense to stop waiting.
Our microteams are small and autonomous. We pair, mob, and vibe continuously. As AI becomes a full participant in that collaboration, those practices aren't going away. They're evolving. The team's social contract is being renegotiated in real time. And continuously. This talk walks back from a future where AI-native development is the norm. What happens when developers become knowledge managers, who own outcomes, not keystrokes? How do specs replace tickets, and feedback loops compress from weeks to minutes?
Every major shift in this industry, think internet, mobile, Git, cloud, expanded what teams could build. AI is no different. The question was never whether to adapt. In software, we do that continuously. Change is imminent. This era is no longer about surviving AI, but rather about thriving with AI.
After over five years of building, breaking, and learning at iBOOD, we’ve discovered what makes a development team truly successful. No frameworks, no dogma—just seven practical habits that help teams ship great software, stay motivated, and keep improving.
This talk is based on real experiences, not theory, nor agile BS. We’ll dive into:
- Prioritizing Pragmatically Balancing business needs, technical debt, and innovation.
- Killing Complexity Keeping architecture, code, and processes simple, even as you scale.
- Owning the Work Why autonomy beats process, and how teams can take real ownership.
- Communicating Relentlessly Why constant, transparent communication makes everything smoother.
- Building Microteams Why smaller, focused teams move faster and collaborate better.
- Delivering Continuously Making small, frequent releases a habit (without the chaos).
- Having Fun Because happy teams build better software. An afterthought about purpose, mastery, and autonomy.
I’ll share stories from the trenches—what worked, what failed, and what we’d never do again. If you’ve ever wondered how to build a team that doesn’t just survive but thrives, this talk will give you concrete ideas to take back to your team.
This talk offers a brutally honest, experience-based look at what makes software teams successful, without buzzwords, silver bullets, or agile theater. Backed by four years of hands-on learning at iBOOD, it distills real-world lessons into seven practical habits any team can adopt.
Searching for speaker images...