Good software provides value and benefit to its users. Most good software has a long life and evolves continuously, keeping pace with the needs of its users.
A project is, by definition, a temporary structure created to manage and deliver a specific goal.
This workshop will explore the conflict between software development organised around projects and software development organised around products. Do projects even make sense in a truly agile software development context?
Participants will work in small groups to exchange thoughts and ideas, build them into a coherent viewpoint and present them back to the other groups.
Dr Kevin Rutherford is a software development coach, trainer and extreme programmer. He is the creator of the vastly under-rated Reek code smell detector, and the vastly over-rated book 'Refactoring in Ruby'. If you have ever used Unix System V or transferred money between bank accounts, you’ve unwittingly used his code. He was using vi before you were born.
Andy is a pragmatic software developer who has - unfortunately - recently ended up in roles like development manager. He has worked for many companies, from a large multi-national through to a 4-person startup - but he is getting to the age where he is beginning to forget half of them.
He has been very fortunate that some thoughtful and intelligent people have spent their time helping him to learn some really useful and interesting stuff, so he tries to give some of that back when he can.
To buy tickets to see this fantastic talk, and many others like it head over to our ticket page.
Need help planning which sessions to attend? We've provided a breakdown of our various session types below.
A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of Agile and Lean practices. Case studies and experience reports include some discussion of lessons learned and an indication of how novel the work is.
Participants learn a new approach, tool or technology through using it to solve one or more practical exercises. Any software/hardware requirements are disclosed in the session description.
A session focused around some specific tool, technique or issue. Primarily led by the speaker, tutorials usually include some elements of interactivity or individual / group exercise.
An in-depth working session on a specific topic. May include paper presentations.