Ways out of
the Kraken's grip
Many ways to work with your crew: hands-on workshops, a backlog with validated goals at every level, and enablement that keeps lean-agile values alive in daily work, with AI where it helps. Every engagement starts with a free, remote discovery call.
Workshops
Crew, context and AI, hands-on.
One to two days, on site or remote, grounded in agile and lean values. No slideshow marathon: the crew works on its own backlog, its own board, its own scenarios.
The Kanban Game
Two days with the getKanban board game: flow, WIP limits, bottlenecks and metrics, felt at first hand rather than explained. On day two the crew designs its own board. Works as crew building on the side.
8 to 12, two boards
Scrum Workshop
Roles, events and artefacts as a played-through mini sprint rather than slides: slice a backlog, plan, build, review, retro. The crew leaves with its first real sprint plan and its own working agreements.
up to 12
Story Mapping
Crew and stakeholders break a product or initiative into a story map: user journey, slices, first release. The result is a structured, prioritised backlog draft, and a natural start into Backlog Architecture with AI.
up to 12
Backlog Tool Workshop
The craft of a good backlog: story splitting patterns, agile estimation done properly, story points and their alternatives, definition of ready. The crew leaves with a full box of tools and a clear sense of which of them fit its own work.
up to 12
Facilitation Workshop
For Scrum Masters and coaches: how to hold a room, not just a meeting. Day one covers stance, psychological safety and session design. Day two is practice: everyone facilitates a real event from their own crew and gets feedback.
up to 12
Flow Metrics & Dashboards
Measuring what matters: cycle time, throughput, WIP and work item age, read in a cumulative flow diagram. Then forecasting without story points, with AI crunching the numbers. The crew builds its own dashboard in its own tool.
up to 12
Backlog
Architecture
with AI
Validated goals at every level, agents on the routine work.
A backlog without validated goals is just a longer list. The main risk is not AI; it is the gap between what was intended and what gets built.
- Approach
- Build a backlog hierarchy that links strategy, portfolio and crews, from initiatives and capabilities down to epics and stories, and validate goals at each level before work moves down. AI agents take on drafting, slicing, checking and forecasting inside that structure; the crew keeps final authority.
- Why
- Structure without validation only organises drift, and validation without structure has nothing to anchor it. Together they keep intent and output aligned even as AI speeds up delivery.
- Who
- Multi-crew products and platforms, backlogs that have outgrown their structure, products with many stakeholders and little shared overview.
- How
- Map the current state: levels, flows, how a requirement travels from idea to story. Design the hierarchy and the validation points. Then introduce agents step by step, with hands-on training. Tool-agnostic, in the systems already in use.
- Outcome
- A backlog everyone can read, validated goals at every level, AI agents handling the routine work inside clear rules, and a crew that maintains it on its own.
the size and complexity of the work
Lean-Agile
Enablement
with AI
Two disciplines, one course, AI on deck.
Building with AI is fast. It still needs agile teamwork and lean discipline, and structures only work if people can live them.
- Approach
- Review how the crew works: ceremonies, overhead, decision points, and how work actually flows. Then bring AI into that routine where it helps, planning, documentation, analysis, and keep the calls with people. Adapts to the existing frame, Scrum, Kanban, Flight Levels or your own, as long as it supports transparency and continuous improvement.
- Why
- The aim is a self-organised, transparent crew that owns its direction, not a framework that is followed because it was introduced. Building with AI makes this more important, not less: speed without a shared way of working turns into noise.
- Who
- Crews already practising agile and looking for the next step, crews starting out, and crews that have inherited a framework nobody chose.
- How
- Coaching for crews, product owners and leadership: workshops, facilitation and hands-on support in the daily routine, on site or remote. AI tools are introduced the same way, small changes first, reviewed together, kept only if they prove themselves.
- Outcome
- Less preparation, more delivery, AI on the mechanical parts, decisions where the knowledge is, and improvement the crew keeps up by itself.
depending on complexity
What about data safety?
NDAs are standard for every engagement. When AI tools are involved, crew and provider agree beforehand which data goes into which systems and what stays in-house.
Chart your course first
A free call to find out what fits your journey best.
Book a free discovery call