Large organizations rarely have one Kanban. Portfolio, Product Management, Architecture and delivery each need their own flow. The challenge is keeping the same work connected as it moves between them. Kanban works well when you can see work moving through a process. But enterprise planning rarely happens inside one process
PI Planning
Your next PI can take shape continuously, long before the planning event begins.
Plan in your team's language. Scaling agile only works when everyone on the train can actually engage with the plan, not just follow along with it. That's why we've rolled out the full Kendis experience in four new languages: German, French, Spanish, and Swedish.
An executive-level conversation with Justin Oke, VP of Global Sales and Partnerships, on why physical sticky-note boards failed remote-first teams, the context that vanishes between one increment and the next, and how AI that actually remembers your programme turns task tracking back into strategic business speed. The
When Agile emerged in the early 2000s, it was a much-needed answer to bloated, slow, waterfall-style project delivery. It brought something refreshing: collaboration over contracts, responding to change over following a plan, people over processes. The goal was straightforward — deliver value faster, better, and together. But somewhere along
If you’ve spent any time in a quarterly planning session, you’ve likely witnessed the "Feature Factory" in full swing. The room is filled with backlogs, Gantt charts, and a roadmap bursting with "what" we are building. The mindset is often tactical: if we ship
Inspect & Adapt is supposed to be one of the most powerful tools in Agile delivery. Its purpose is simple: look at what happened during the last Program Increment (PI), understand why things went well or poorly, and make concrete adjustments for the next cycle. When done properly, it creates
Imagine finalizing a portfolio plan for the quarter, only to discover halfway through that the world has moved on. By the time most strategic decisions are acted on, they’re already outdated. In complex portfolios, execution moves faster than interpretation, and leaders are always a quarter behind reality. This gap
PI Planning
Over the years, advancements in ALM tools have significantly changed how organizations approach PI Planning. Teams now have access to more structured backlogs, real-time updates, dependency tracking, and planning artifacts than ever before, with tools that have made it possible to plan across dozens of teams and hundreds of
Most Agile teams still measure success the same way factories measure success. “How many units did we ship?” Epics, Features, Stories, Bugs. Tickets. Velocity. Release notes that read like a supermarket receipt. And then everyone wonders why the business isn’t moving. If what you shipped doesn’t change customer
Modern Agile delivery is full of artifacts. Features, epics, stories, dependencies and more. Each artifact is useful on its own and together, they describe a plan. But no single place truly owns that plan as a coherent narrative. This is the gap that shows up most clearly after PI Planning
Dependency Management
If you are already using Kendis for program boards, solution boards, and dependency management, you already understand one core truth: dependencies are unavoidable in scaled delivery. As teams grow, ARTs expand, and delivery spans multiple tools, dependencies stop being simple handoffs and start becoming one of the biggest risks to