> This feels like a strawman - does anyone actually build software this way? I've seen teams perform this cursed sequence: 1. "As a user, I want my pipes to s

> This feels like a strawman - does anyone actually build software this way? I've seen teams perform this cursed sequence: 1. "As a user, I want my pipes to stop leaking" 2. Replacing the leaking joints and pipes would be very time-consuming, we should produce an MVP using duct tapes and drip-catching buckets an intern empties every day, to confirm that users really want this. If they do, we can redo it properly later. 3. New feature released - pipes stop leaking. Great job everyone. 4. Redo it properly? Our users aren't asking for that, their pipes aren't leaking any more. Interns aren't users.