yak-shave

Plan a replacement before Parallel Change. Sniff out a bad system or a feature the current architecture cannot hold, inventory what that system does, decide which capabilities to retain, retire, or introduce, and design the interface for that set. Then enter expand-and-contract. Use when the user says yak shave or yak shaving, when a new feature does not fit the architecture, when scenario-design finds a scenario the architecture cannot hold, or when fix-loop stops because the architecture is unsound. Do not use to harden a sound architecture that already fits the goal (fix-loop), or to build, migrate, and delete once the interface is confirmed (expand-and-contract).