Problems with Proxies in Software

#91 - Lean Software Development Principles and Mindset - Mary & Tom Poppendieck

Topic 3 of 5

Published Jun 6, 2022 · Clip 31:00–41:18 (10:18)

Mary explains that the concept of proxies came from Jeff Bezos's shareholder letter about staying in 'day one.' She argues that teams doing work should be in direct connection with the people they do it for, citing Amazon, SpaceX, and Tesla as organizations without proxies. She contrasts software's proxy-laden structure (business analysts, product owners) with traditional engineering, where experts deal directly with problems, and calls Scrum's product owner concept its biggest mistake. Tom adds that maximizing utilization is a deceptive proxy metric. They discuss managing by outcomes rather than tasks: give teams the expected outcome and rationale, and let them decide the tasks, since proxies cannot know the technical details or convey the 'why.'