• start with signals, not requirements

• have a problem statement, not features

• plan with hypotheses, not estimates

• experiments around a hypothesis, not backlog of stories

• analysis and conclusion, not guesses

• analysis and conclusion, not guesses

if you have good problem solving teams, what good are estimates?

within constraints

• here is my constraints

• here is my problem

(src: Video: The Future of Software Engineering - Mary Poppendieck)