How Do Tasks Flow in Albatross, Compared to Scrum and Kanban

Most comparisons of Scrum, Kanban, and Albatross are about philosophy. This one is about cells.

Five people. Sixty days. The same work, done three ways. One cell is one person, one day. The cells show where work happened, where it waited, and where it was squeezed.

Scrum

Scrum Fixed calendar intervals. Tasks crowded toward the boundary. Some overflow the lane. M1 M2 M3 M4 M5 Sprint 1 end Sprint 2 end D1 D10 D20 D30 D40 D50 D60 push push push crowd push push push push push push push push push push push Work Crowded — pushed toward boundary Overflowing the lane Dependency wait Sprint boundary

Tasks are dense at the start of each interval and crowded at the end. The sprint boundary forces the work to fit a calendar, so the last days are compressed — and some tasks push out of the lane entirely. The lane is the person. It can only hold so much.

Meanwhile, a few cells sit empty mid-sprint. A dependency wasn’t ready, and no one could proceed.

Scrum pays in overloaded people and in waits it can’t see coming.

Kanban

Kanban No boundaries. Work flows where it can. Waits appear where a dependency was missed. M1 M2 M3 M4 M5 D1 D10 D20 D30 D40 D50 D60 Work Unoccupied — dependency missed

No boundaries. Tasks flow wherever they can, at whatever size they arrive.

The waits are the story. Cells sit empty at irregular points across the timeline — wherever a dependency was missed. They don’t line up across lanes, because nothing coordinates them. Each person waits on their own dependency, at their own time.

Nothing is crowded. There’s no boundary to squeeze against. So Kanban doesn’t overload people.

It wastes time instead.

Albatross

Albatross No boundaries. Dependencies designed first, so the schedule holds. No unoccupied cells. M1 M2 M3 M4 M5 D1 D10 D20 D30 D40 D50 D60 Work No boundaries. No unoccupied cells.

No boundaries, no crowding, no empty cells.

Every lane runs continuously. Every cell is occupied. The waits that appear in the other two diagrams — the mid-sprint stalls, the scattered dependency misses — don’t happen.

Not because the work is smaller or the team is faster. Because the dependencies were designed before construction began, and the schedule was plotted from that structure. Readiness is known before work starts. Nothing waits, because nothing was started before its dependencies were satisfied.

The Comparison

BoundariesEmpty cellsCrowding
ScrumYesSomeYes — at boundaries
KanbanNoThroughoutNo
AlbatrossNoNoNo

Scrum pays in overloaded people. Kanban pays in lost time. Albatross pays in neither.

That’s the difference three diagrams can show. The reason is in the structure — and that’s the longer argument.


Related:

Leave a Reply

Your email address will not be published. Required fields are marked *