Critical Chain
In a portfolio, the constraint is usually a skill that every project needs a little of. With aangine, you see which pool it is, period by period, and sequence project starts so it is not overloaded.
The planning gap
The Theory of Constraints starts with a simple discipline: identify the constraint, exploit it, subordinate everything else to it, elevate it, and keep inertia from becoming the new constraint. In a single project the constraint is often a chain of tasks. In a portfolio it is usually a scarce skill or resource: data engineers, a test environment, the few people who understand the billing system. Every project needs a little of them, and together they set the pace.
A constraint like that rarely shows up in a status report. Only the combined load, period by period, shows that one pool is planned far beyond what it can deliver. Approving a project and starting it are also different decisions. When they are treated as one, a project is approved and starts now, another is approved next week and starts too, and soon the same specialists are switching between many projects, each waiting on the others, while every finish date slides.
The portfolio also keeps changing. A new top priority lands, a team loses people, a project slips, and the constraint quietly moves somewhere else. The theory is well understood. Keeping the sequence right by hand, week after week, is the hard part, and a plan rebuilt on a spreadsheet each time is already out of date when it reaches the meeting.
How aangine works with Critical Chain
Buffer management and task-level critical chain schedules stay in your scheduling and CCPM tools; aangine does not size or manage buffers. It decides what starts when at portfolio level, against real capacity.
Capacity is planned by team, role or skill across every project, with operations and service work, calendars and temporary reductions included. The AI Portfolio Analyst reads the plan one time slice at a time and flags the pools heading for overload in Portfolio Journey, with every figure drawn from aangine’s algorithms and your own data.
Rank the work by business unit or by score, then replan. The algorithms postpone or pull forward projects to clear overloads on the constrained pool, higher priority first, while dependencies and deadlines hold. Mandatory and locked projects never move, and the plan shows which pool ran out and when.
A project is pulled in only when it fits within capacity. When it does not, the plan shows what it would displace or which pool would need to grow. Waiting demand that now fits is pulled in, and the lowest-value, non-mandatory work is flagged as a candidate to drop.
When exploiting and subordinating are not enough, each option becomes a scenario: add people to the constrained pool, bring in temporary capacity, or keep capacity and re-sequence. Compare which projects start sooner, the labor cost and how value timing changes, then take a clear, costed ask to finance.
In practice
In multi-project Critical Chain, staggering project starts is the main lever. Here it means sequencing starts within capacity limits, and keeping that sequence current as the portfolio changes.
Plan the pool that sets the pace by role or skill, with its real availability after operations work, calendars and temporary reductions.
Use business-unit ranking or scoring, so the sequence reflects agreed priorities and strategy, not whoever asked loudest in the last meeting.
Replan in one click. See which projects moved, which pool ran out and when, and which projects wait because of it.
Compare the staggered plan with the current one, then accept, lock or adjust. When the constraint moves, replan again instead of rebuilding by hand.
How aangine works
aangine is the decision layer above the tools you already use. No rip & replace: it imports your plans, replans them in one click and pushes the approved plan back.
The result: faster, clearer decisions when it matters most.
What our customers report in their case studies. Read the customer results
Keep exploring
Framework and method names are used to identify them only. aangine and Continuous Software are not affiliated with, or endorsed by, the owners of these frameworks and methods.
Book a demo
Book a demo and bring your project pipeline and the pool you suspect is the constraint. We’ll show how your portfolio sequences around it, alongside the CCPM tools you already use.
