The Method Board is an independent, tool-neutral desk comparing software delivery methods. It exists because most teams adopt a method by copying its rituals and never ask what the method was designed to fix.
Every method on the wall is filed the same six ways: the ceremonies it runs, the roles it names, the artifacts it produces, its cadence, how work flows from ready to done, and where it breaks down. That shared card lets you set an iteration-based framework, a flow-based one, and a hybrid against each other on the same terms.
Our editors stick to widely taught ideas — Agile values, Scrum as an empirical process, and Kanban as a pull system with explicit limits — and frame everything as general education. We do not name or rank specific software products or commercial vendors, and we make no promises about how any method will perform for a given team.