Method selection map

Method selection mapMethod selection map: how much is known against how interrupt-driven demand is, with a default method in each quadrantHow much is known: ordered (left) to complex (right)Demand: planned (top) to interrupt-driven (bottom)Plan-driven, iterative insideKnown target state, fixed externaldate and scope. Gates at the contractlevel, small tested incrementswithin.Scrum or Shape Up + discoveryValue risk high. Sprint Goals orappetite-bounded bets, a discoverytrack, reviews with customers.Kanban with WIP limits and anSLEMany small, known items arrivingunplanned. Classes of service, aquotable service level.Kanban + a discovery trackUnplanned demand and unknowns. Flowfor delivery, a fixed weekly slot forlearning and review.Across all quadrants: five or more teams on one product? Remove dependenciesfirst, then scale.

A starting point for choosing a method per team. Two questions (how much is known, and how much demand arrives unplanned) place most teams. Fixed external dates, team count and the strength of test and eval automation then adjust the default.