P/Mary-Poppendieck

cf: Tuesday of Model_ Design Sprint (src: Video_ The Future of Software Engineering - Mary Poppendieck)

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)

(https://www.youtube.com/watch?v=6K4ljFZWgW8) Book_ Antifragile - Nicolas Taleb Paper_ Resilience Engineering_ Learning to Embrace Failure - Acm Queue Book_ The DevOps Handbook - Gene Kim, Jez Humble, Patrick Debois, John Willis Book_ Continuous Delivery - Jez Humble, David Farley Paper_ Online Experimentation at Microsoft - Kohavi, Crook, Longbotham Paper: Standis Group Study Reported at XP2002 by Jim Johnson, Chairman Book_ Sprint - Jake Knapp, John Zeratsky, Brad Kowitz Video_ The Design Sprint - Google I_O 2014 scale out more servers CAP theorem less communication autonomous teams...