|
|
|
<<< Previous speaker
|
next speaker >>>
|
Steve Freeman, Independent Consultant
Steve was a pioneer of Agile software development in the UK, he has
built applications for banks, ISPs, financial data providers, and
specialist software companies. He has given training courses in
Europe, America, and Asia.
Previously, he worked in research labs, software houses, earned a PhD, and wrote shrink-wrap software for IBM. Steve also teaches in the Computer Science department at University College London. He is a presenter and organizer at
international industry conferences, and was conference chair for the
first London XpDay.
|
Presentation: "Turning on a sixpence - technical skills for Agile development : Introduction"
Time:
Wednesday 10:30 - 10:45
Location:
Abbey Room
Abstract: Many organisations have adopted Agile development practices over the past ten years and are now discovering that there's more to it than iterations and stand-ups. One of the best features of the Agile movement was that it reset the balance between the business and technical sides of a software organisation. True Agility--the ability to respond rapidly to change--requires both good business decision- making and strong technical skills and practice.
This track is about the technical essentials you need to know to make Agile software development reliable and sustainable. It will include "refresher" topics, for those who are just starting or have been getting a bit rusty, and some of the new ideas and practices that have come out of a decade of experience in the discipline.
Presentation: "Test Driven Development: Ten Years Later"
Time:
Wednesday 14:15 - 15:15
Location:
Abbey Room
Abstract: Over the last ten years, Test-Driven Development has grown from something exotic, that only a handful of people knew about, to near- commodity. So there's nothing left to say, right? We don't think so.
In this session, we'll review some of the landmarks in the history of Test-Driven Development and what they tell us about how to develop software; the ideas, techniques, objections, and misunderstandings.
We'll talk about our experiences of discovering TDD and what we've learned about how to do it well, how to adopt it, and how to bring it into existing code.
|
 |
| |
