Strictly, there’s nothing to compare: the Agile Manifesto isn’t a method. It’s four values and twelve principles, written in 2001 — and in its true form it’s close to perfect. You don’t choose between Scaleflow and the Manifesto. Scaleflow is one attempt to live it, at a time when “agile” has too often come to mean process for its own sake.

The four values, mapped

While there is value in the items on the right, we value the items on the left more.

• Individuals and interactions over processes and tools. Scaleflow is process-heavy — but the process exists to force interaction: the cross-functional Daily Check-inDaily Check-inA 15-minute daily ritual where the team surfaces reality and unknowns rather than reporting status., the Product BoardProduct BoardTwo or more stakeholders who see the team's weekly demo and coach it — the human in the loop, with no single lead., a team that shares context daily. The rhythm is in service of the people, not the other way round.
• Working software over comprehensive documentation. Progress is a weekly demo of working software, never points or a status report. The documents that exist — the Initiative DocumentInitiative DocumentThe PR/FAQ-shaped document where an initiative's context lives — customer, solution, plan, business case, and success metrics., the Check-in — are lightweight, living context that replaces meetings, not comprehensive specs that pile up beside the work.
• Customer collaboration over contract negotiation. Scaleflow works backwards from the customer and keeps a customer voice on the Product Board; validation is continuous, not a sign-off.
• Responding to change over following a plan. The ApproachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success. is re-cut every week, uncertainties are scheduled into it, and the plan is a way to communicate — never a contract to defend.

The honest tension

The first value is the one to face squarely: how can a method this full of meetings claim “individuals and interactions over processes and tools”? Because the Manifesto never said no process — it said value interactions more. Scaleflow’s wager is that the right process produces more genuine interaction than its absence does: a daily cross-discipline conversation, and a weekly room where the team and its board look at something real together. Process that smothers interaction is the failure mode; process that forces it is the point.

The principles read like the rhythm

Scaleflow didn’t set out to tick off the twelve principles, but the weekly rhythm ends up describing most of them:

• Deliver working software frequently — the weekly demo.
• Business people and developers work together daily — the cross-functional Check-in.
• Working software is the primary measure of progress — live-or-concluded only, never a chart.
• Promote sustainable development, a constant pace — the 75% capacity rule.
• The best work emerges from self-organising teams — roles, not titles; a board that coaches rather than commands.
• Reflect at regular intervals and adjust — Lessons Learned, every Check-in; retrospectives on the rhythm.

We take that as a good sign, not a coincidence — and as the reason we’re comfortable calling Scaleflow a true agile method rather than just an agile-flavoured one.