Track: Effective design and Clean code

Abstract: Most software is written to solve a problem. Unfortunately we often don't pause long enough to understand the problem, or check our progress to make sure we're still solving it. This leads us to write more software than we need, and to write software that does more than the original problem required (or in too many cases, software that doen't solve the original problem at all). Business folks try to counter this by writing down everything they think we need to know in copious detail - known as requirements documents - to try to keep us on track. This doesn't usually work out so well. Technical folks try to counter this by creating software libraries designed to cope with any eventuality - we call these frameworks - so we can focus on solving the business problem. This doesn't usually work out so well either. In this talk, Dan contrasts the traditional top-down and bottom-up approaches with a proven "outside-in" approach based on real life experience - engaging with and listening to our stakeholders. He shows how this can allow us to stay firmly on track, leading to clean code and effective design that provides maximum value to our stakeholders. Not just the famous Scrum Product Owner. And still be home in time for tea.