GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes
Russell Miles, TweetCo-Author of Head First Software Development
Biography: Russell Miles
Russ Miles is Principal Consultant at Simplicity Itself and works with their clients to continuously and sustainably delivering valuable software.
Russ' experience covers almost every facet of software delivery having worked across many different domains including Financial Services, Publishing, Defence, Insurance and Search. With over 16 years experience and through consultancy, coaching and training, Russ uses a holistic view of the software delivery process in order to implement multi-faceted continuous improvement programmes touching on everything from developer skills and practices, creating and evolving the best architectures and designs for a given domain, through to advising the management of various companies on how to apply lean and agile thinking and practices to better tune their return on investment from their software development effort.
Russ is also an international speaker on techniques for achieving the delivery of valuable software as well as a published author, most recently of "Head First Software Development" from O'Reilly Media. He is currently working on two new books; "Programming Spring" for O'Reilly Media that launches the Simplicity Itself technique of "Test Driven Learning" for the first time publicly, and another book, working title being "Field Guide to Continuous Improvement for Software Delivery Team Members" that captures the different thinking tools and techniques that a professional software developer can apply concretely to their own continuous improvement goals.
Twitter: @russmiles
Presentation: TweetFrom 'Agile Hangover' to 'Antifragile Organisations'
This is the unfortunate age of the ‘agile hangover’.
In this talk Russ Miles, Chief Scientist at Simplicity Itself, will share his experiences overcoming the agile hangover, looking at:
• The many different facets of an ‘agile hangover’
• Where common organisational changes disrupted the routes being taken towards agility
• Typically where and why Agile ‘champions' leavde the organisation stealing the journey's momentum
• What we wanted, and what didn’t we get from a typical ‘agile journey’
• How to turn an agile hangover into something that can really get those promised benefits by going beyond ‘Agile’
Workshop: Embracing Change: Building Adaptable Software with Events Tweet
Ever experienced that moment where your heart sinks at the words "We just want you to make this one, small and trivial change…".
If you build software, change is an inevitable force in your life and your ability to react to change can be the difference between a killer product and a last-to-the-post flop.
Given that change and speed of software evolution is so critical, why is it that so much software becomes a millstone around yourself and your team's next, leading to you dreading the next inevitable change that's needed? For over 10 years, focus has been consistently applied to helping us work in a more agile and adaptable fashion, with far less focus on how to create software that thrives in an agile environment.
This hands-on, extremely practical course teaches you the latest techniques you can apply today to your architecture, design and code to build software that doesn't fear change. This course will teach you how to build software that adapts as fast as your business and requirements do.
In this deeply technical course you will learn how to:
- Understand Change: Manage evolution from a component, module and system perspective.
- Understand Complexity: Identify the causes of complexity in your architecture, design and code and the affect it has on dealing with change.
- Organise for Change: Organise your architecture, design and code for clarity and change.
- Clean Design and Architecture: Architect, design and build components that embrace change.
- Reduce Inter and Intra System Coupling: Identify and Manage accidental coupling between components, modules and systems.
- Apply Events: Apply Event-Driven Architectural patterns to increase de-coupling.
Requirements: Bring a laptop and if you have GitHub account.