AICoo Logo
Sign in

Next-Generation Agile

Agile control for large, complex, uncertain projects

NGA is not another agile flavour. It is a set of complementary techniques that extends agile beyond software development, with systematic uncertainty reduction from portfolio strategy down to the daily task board.

Organisation

Breakdown

Portfolio

Network

Plan

Gantt

Task

Kanban

One dataset, four zoom levels: from the whole organisation down to a single task in flight.

Why classic agile is not enough

Scrum and its relatives work because they systematically reduce uncertainty in software development. But they lean on freedoms that only software offers, and on a narrow slice of the project life cycle. Outside that comfort zone, the gaps show.

Built on software assumptions

Incremental delivery relies on code that can be reworked without scrapping materials, teams that need nothing but a laptop, and features that ship independently. Construction, manufacturing and transformation projects have none of these freedoms.

Covers execution only

Classic agile supports building, testing and deploying. Selecting the right projects, aligning them with strategy and tracking benefits after go-live remain uncovered.

Operational level only

Scrum coordinates one team through one sprint. Tactical questions such as sequencing projects, sharing resources and managing cross-project dependencies are out of its scope.

Success defined too narrowly

Compliance with user requirements is not the same as organisational benefit. Projects can pass every demo and still fail the business case.

NGA keeps the agile ceremonies where they work and adds the missing strategic and tactical layers on top.

One common denominator: uncertainty

Whether you steer by time, cost, scope, benefits or risk, the shared denominator is uncertainty. It comes in two forms: information you do not have yet, and information you have but overlook.

The uncertainty matrix makes this visible. Project success means systematically growing the known-knowns quadrant before overlooked stakeholders, requirements and dependencies turn into overruns.

Four strategies to reduce uncertainty

  1. 1Raise information awareness
  2. 2Increase information availability
  3. 3Improve the effective use of information
  4. 4Maximise information efficiency
Information awareness

Known-knowns

Available and understood

Known-unknowns

Wanted but not yet available

Unknown-knowns

Available but overlooked

Unknown-unknowns

Invisible and unexpected

Information availability

Twelve techniques, one goal

Each NGA technique addresses one key project uncertainty that classic agile leaves open. They are complementary: you keep your existing ceremonies and add what is missing.

01

One Breath Challenge

Do we understand each other?

Communication effectiveness

02

Switching Thinking Modes

Are we thinking effectively as a group?

Collective thinking

03

Strategic Step Transformation

How does the project affect the organisation?

Impact uncertainty

04

Project Methodology Framework

Are we using the optimal project method?

Method uncertainty

05

Project Elevator Pitch

Do we understand the why, what and how?

Assignment clarity

06

Project Success Paradigm

Are we achieving what we set out to do?

Success forecast

07

Project Metadata Technique

Are we overlooking existing information?

Information awareness

08

Result Breakdown Structures

What is part of the project, and what is not?

Scope obscurity

09

Power Kanban

Does the right hand know what the left hand does?

Coordination uncertainty

10

Agile Rolling Wave

How far ahead do we plan, and in what detail?

Diminishing planning returns

11

In-Flight Guidance

How robust is the plan against unwanted events?

Scenario variability

12

Project Information Blueprint

Are we wasting time processing information?

Information efficiency

aicoo NGA

One dataset, four cross sections

aicoo NGA implements the method as one connected dataset with four zoom levels, from the whole organisation down to a single task in flight. Nothing is re-entered, nothing is kept in sync by hand.

Cross section 01 · Organisation

Breakdown

What work exists across the organisation?

Portfolios, programmes, projects and epics in one structured tree. Ownership, status and progress roll up every level, so the executive view and the project view read from the same records.

Used by:
Portfolio leads, PMO, executives
Answers:
Coverage, ownership, duplication

NGA technique: Result Breakdown Structures

Northwind Group

Portfolio → Programme → Project → Epic → …

The tree keeps going below epics: stories and tasks live on the Kanban board.

Cross section 02 · Portfolio

Network

What depends on what?

Dependencies between projects are made explicit instead of living in status calls. A date change propagates along the chain, and the projects it puts at risk surface immediately.

Used by:
Programme managers, PMO
Answers:
Critical path, blast radius, sequencing

NGA technique: Power Kanban (coordination)

Dependencies

Critical chain

A two-week slip in Data warehouse moves CRM rollout and Billing rework.

Cross section 03 · Plan

Gantt

When does each phase land?

High-level phases on one timeline. Deliberately coarse: the plan stays stable while the work underneath it moves, and a phase shift is a decision, not a side effect.

Used by:
Project leads, steering committee
Answers:
Sequence, duration, phase dates

NGA technique: Agile Rolling Wave

Platform migration

5 phases

Phase
Q1
Q2
Q3
Q4
Discovery
Solution design
Build
Integration
Rollout
Today

Phase dates are what the dependency network reads.

Cross section 04 · Task

Kanban

What is being worked on right now?

Granular tasks, moved by the people doing the work. Each card belongs to a phase above it, so execution reporting is a by-product of the board rather than a weekly exercise.

Used by:
Delivery teams, scrum leads
Answers:
Flow, load, what is blocked

NGA technique: Power Kanban

Platform migration · Sprint 14

Phase: Build

Backlog12
PM-214
Schema migration script
PM-219
Legacy user import
PM-221
Audit log endpoints
In progress5
PM-198SN
Tenant routing layer
PM-201JW
SSO handshakeBlocked
Review3
PM-187PI
Rate limit config
PM-190
Error taxonomy docs
Done24
PM-172
Environment parity
PM-178
Secrets rotation

Card movement updates phase progress on the Gantt automatically.

Grounded in the NextGen Agile Handbook

NGA was developed by Paul W. M. Cuypers of Hyves Project Research, Norway, and is documented in The NextGen Agile Handbook. aicoo NGA is the tooling built side by side with the method, so the techniques are not slideware but daily practice.

Compliance and data security, built for large, complex projects

From GDPR to your customer's IT security questionnaire: your project data is stored on German servers, encrypted in transit and stays under your control at all times.

aicoo Legal
  • Data stored in Germany

  • GDPR compliant

  • 99.95% uptime

  • Encrypted data transfer

Get to know aicoo NGA in 30 minutes

Book a meeting and learn how aicoo NGA turns Next-Generation Agile into daily practice, from the portfolio breakdown to the task board.