How to combine Agile and Critical Chain

When it comes to managing complex projects, finding the right balance between day-to-day task flexibility and long-term milestone planning is often challenging.

Too often, teams get bogged down in micro-level details while losing sight of key milestones—or vice versa, where high-level plans fail because the day-to-day execution doesn’t align.

In Jira or Azur Devops it is common to see a mix of cards, features, epics with messy names. It is difficult to understand the big picture.

Another approach is possible

A hybrid approach combining Agile Kanban boards for detailed task management and Critical Chain Project Management (CCPM) for milestone-focused scheduling.

This method provides both the adaptability to manage change and the focus to hit critical deadlines.

What Is Two-Tier Scheduling?

Two-tier scheduling involves splitting project planning into two interconnected layers:

1. High-level schedule (Tier 1): Focused on major milestones, work packages, and their dependencies, typically managed using CCPM principles.
2. Detailed task management (Tier 2): Tasks within each work package are managed through Kanban boards or Agile sprints, providing flexibility and visibility for the team.

This approach ensures that local tasks (Tier 2) align with global project priorities (Tier 1) without creating bottlenecks or unnecessary multitasking.

Step 1: Define Work Packages to Group Related Tasks

The first step in this hybrid approach is to group detailed tasks into work packages.

A work package is a collection of related tasks or deliverables that contribute to achieving a specific project milestone.

What makes a good work package?

• Clear deliverables: Each work package should have a defined outcome or product, such as a completed design, code module, or prototype.
• Dependencies identified: The work package should specify dependencies on other work packages or external factors.
• Focused ownership: Assign a team or individual responsible for delivering the work package.
• Reasonable size: The package should be large enough to represent meaningful progress but small enough to be completed in a manageable timeframe.

Think of work packages as the bridge between strategic milestones and operational tasks.

They provide the context teams need to prioritise tasks while keeping their focus on broader project objectives.

Quote from NuNet (who combine Agile and CCPM):

Each work package is assigned a collaboration group of developers who work together for closing issues associated with the package. Each work package contains a scope buffer, which allows to account of uncertainty of work package delivery time, in case new issues are identified and added during work.

Step 2: Build the Critical Chain Schedule (Tier 1)

Once work packages are defined, use CCPM to map out the project’s critical chain. The critical chain is the longest sequence of dependent work packages that determines the overall project duration.

Here’s what CCPM brings to the table:

• Buffer management: Instead of adding padding to each task, CCPM adds buffers at key milestones or the project’s end to absorb variability.
• Resource prioritisation: Tasks and work packages are scheduled based on actual resource availability, avoiding multitasking and resource contention.
• Dependencies accounted for: The critical chain maps out which work packages depend on each other, ensuring that delays are detected early.

This high-level view ensures that teams aren’t just busy—they’re working on the right tasks to meet deadlines.

For those that don't know how Critical Chain Project Management works, here is a 3-minute video explanation:

Step 3: Manage Detailed Tasks Using Kanban Boards (Tier 2)

While the CCPM schedule focuses on milestone-level planning, day-to-day execution happens at the task level through Kanban boards.

Each work package is broken down into tasks that are:

• Placed on a Kanban board: Tasks move across columns like “To Do,” “In Progress,” and “Done,” providing real-time visibility of progress.
• Managed with flow efficiency: Teams work in pull mode, pulling tasks only when they have capacity, which minimizes work-in-progress (WIP) and prevents overloading.
• Aligned with priorities: Because tasks are tied to specific work packages, Kanban boards naturally reflect the priorities set by the CCPM schedule.

For example, if a work package on the critical chain is delayed, teams can quickly identify and prioritise its associated tasks on the Kanban board to resolve the issue.

Step 4: Maintain Alignment Between the Two Tiers

The key to making two-tier scheduling work is maintaining continuous alignment between Tier 1 (CCPM) and Tier 2 (Kanban). Here’s how to do it:

1. Frequent updates: Regularly update the CCPM schedule based on progress at the task level. Name a work package owner.
2. Fever chart monitoring: Use CCPM’s fever charts to track the consumption of project buffers relative to progress. If the project moves into the “yellow” or “red” zone, prioritise tasks on the Kanban board accordingly.
3. Daily or weekly stand-ups: During daily meetings, review not just task progress but also how it impacts the overall schedule. This ensures that teams stay focused on tasks that protect critical milestones.

Why Two-Tier Scheduling Works: The Benefits

1. Structured Flexibility: Teams can adjust tasks within a work package without jeopardizing the overall project timeline, providing flexibility without chaos.
2. Reduced Multitasking: By linking detailed tasks to work packages and prioritizing critical chain activities, teams avoid the common trap of jumping between unrelated tasks.
3. Early Problem Detection: Dependencies between work packages are mapped out in advance, making it easier to identify and address delays before they escalate.
4. Improved Delivery Reliability: Buffers in the CCPM schedule absorb uncertainties, reducing the risk of missed milestones.

Real-World Application:

NuNet’s Combination of Agile Speed with CCPM Focus

Watch this testimonial from Nunet: Testimonial of combining Agile and Critical Chain

Final Thought: Deliver Faster Without Losing Control

Mixing CCPM and Agile is more than just a blend of methodologies—it’s a powerful way to synchronise big-picture planning with day-to-day execution. By grouping tasks into work packages and linking them through a critical chain, you get the best of both worlds: the adaptability of Agile and the precision of CCPM.

It is also useful for multi-project:

Next step?

Are you ready to implement this approach and revolutionize your project management?

Let’s discuss how this approach could work for your next big project.

Contact MARRIS Consulting if you want to do the same.

If you want more content like this you can subscribe to our newsletter: Marris Consulting's Newsletter

This article is based on an original article by Etienne Lecerf .

Marris Consulting offers:

• Consulting services
• Training courses (online or on-site)
• Short 2-day diagnostics