About Taskstreamer - Born From 25+ Years in IT Development Management

18 Years Independent

Maarten Rooseboom

Founder & Product Lead

I've spent over 25 years in Software Development & IT management, working across projects and Agile teams. I started with Prince2 and traditional project management, detailed plans, fixed baselines and Gantt charts. It worked well for predictable work, but struggled the moment requirements shifted. Then I embraced Agile. Teams became more responsive, but leadership lost the big picture. Nobody could answer "When will it be done?" or "What should we work on next?"

For the last 18 years, I've been independent, helping organization after organization find alignment. I've been asked to consult at the strategy level. I declined. Strategy decks are easy. The hard part is what happens after at the tactical and execution layer where plans meet reality. That's where I've always stayed.

And that's where you see what most consultancies and tool vendors miss. Beautiful frameworks that look great in a presentation but fall apart the moment real teams with real dependencies and real capacity constraints try to use them. I watched this pattern repeat across dozens of organizations, regardless of framework: smart people spending their weeks maintaining a picture of reality instead of actually shaping direction.

Taskstreamer is built from the execution layer up, from what actually happens when plans meet teams. Not from what looks good on a slide.

The journey to understanding

Every lesson learned across dozens of organizations shaped what Taskstreamer became.

The Early Years

Traditional project management

Waterfall, Gantt charts, Prince2 certification. We learned to plan everything upfront, create detailed work breakdown structures, and track progress against fixed baselines. It works for when the end-goal is known.

The Agile Transition

Teams got faster. Visibility got worse.

Sprints, stand-ups, retrospectives. Teams became more responsive and delivered in shorter cycles. But leadership lost the strategic view. "When will it be done?" became unanswerable. Agile solved the delivery problem for unknown targets but created an alignment problem.

25+ Years of seeing the Pattern

Every organization, same problem

Working independently across dozens of organizations, a pattern became undeniable. SAFe shops, Scrum teams, project-driven companies, hybrid setups (the framework didn't matter.). Underneath, it was always the same flow: strategy into execution through teams. And everyone was spending their time maintaining roadmaps instead of thinking about direction.

The Realization

Portfolio management had become roadmap maintenance

The real insight wasn't about Waterfall vs. Agile. It was that the entire industry had confused maintaining a picture of reality with actually shaping direction. People who should be thinking strategically, considering options, understanding trade-offs, making deliberate choice, were instead updating spreadsheets. That had to change.

This experience shaped our philosophy

After 20 years of watching the same pattern repeat: strategies dying in transit, roadmaps becoming fiction, smart people spending their weeks maintaining plans instead of making decisions, we crystallized what we believe alignment software must do differently.

These aren't abstract principles. They're hard-won lessons from decades of trying to help organizations think clearly about where they're going and why.

What we believe

Five principles that guide everything we build.

Belief 01

Every framework is an expression of the same underlying reality: strategy flowing into execution through teams.

Belief 02

Portfolio management is not keeping roadmaps up to date. It's understanding direction and why.

Belief 03

Organizations are living systems where everything influences everything.

Belief 04

Strategic decisions deserve data-informed exploration, not gut feeling or week-long analysis.

Belief 05

Strategy and execution must connect without forcing anyone out of their world.

Read the full philosophy

Why we refuse to prescribe a framework

Dave Snowden's Cynefin Framework taught us that different types of work require different approaches. The mistake isn't choosing Waterfall or Agile, it's forcing one approach on all types of work. This insight is fundamental to how we built Taskstreamer.

Complicated Work → Plan Systematically

Difficult but knowable. The end state is clear. Plan thoroughly, execute against milestones.

Complex Work → Iterate and Learn

Unpredictable outcomes. Small bets with feedback loops. Adapt continuously based on what you discover.

Most organizations do both, and everything in between. That's why Taskstreamer doesn't force you into SAFe, Scrum, or traditional project management. It supports the way you actually work, whatever blend that is. The underlying flow is always the same: strategy into execution through teams.

Learn more about Cynefin Framework

Built by people who've lived the problem