‘To further the state of agile and lean software development by providing a forum at which an international group of experts and novices from both industry and academia can meet and learn from each other’ XP2016 Mission
Day 1. Digital Friction Lab - Key Takeaways The Process Signals/Patterns Problem Statement Hypotheses Experiment Not Requirements Not Features Not Estimates Not a backlog of stories Do Multiple Experiments
Highly Successful Digital Organisations Day 1. Digital Friction Lab - Conclusions Do ● Constantly Evolving Products ● Problems ● Hypotheses ● Full Stack Teams ● Immediate Connection ● Tests at Specification ● Deployment Pipeline ● Federated Architecture Don’t Do ● Projects ● Features ● Estimates ● IT ● Outsourcing ● Testing at the End ● Periodic Releases ● Monolithic Architecture
Day 2. Keynote Takeaways Allocation: optimizing for happiness Organisation = a mesh not a hierarchy Breakfast = “genius piece of social engineering” Don’t hire into leadership roles
Day 2. Keynote - Principles - Use Conway’s Law to your advantage - Separate “What” and “How” - Work at sustainable pace - Automate relentlessly - Ensure feedback cycles are fast - Teams own their own quality - Reflect, adapt, experiment
Day 2 - Symbiotic Design Practices - Full Spectrum vs Full Stack Developer - Take advantage of Conway’s Law - dynamic reteaming - Legacy code = team lifetime != code lifetime - Feature deletion - The cost of change - Software like biology