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

<< previous speaker next speaker >>

Prag-Dave Thomas, Pragmatic Programmer turned Publisher

Prag-Dave Thomas

Biography: Prag-Dave Thomas

Dave Thomas (@pragdave) is a cornerstone of the Ruby community, and is personally responsible for many of its innovative directions and initiatives. Dave is a programmer, and now he is an accidental publisher. He wrote The Pragmatic Programmer with Andy Hunt at the end of the '90s, and that experience opened a new world for them. They discovered a love of writing that complemented their love of learning new things. Dave is one of the authors of the Agile Manifesto, and he is probably responsible for bringing Ruby to attention of Western developers with the book Programming Ruby. He was one of the first adopters of Rails, and helped spread the word with the book Agile Web Development with Rails. He enjoys speaking at conferences, running public and private training. But most of all, he loves coding.

Presentation: A retake on the Agile Manifesto Part I

Track: People & Process - Day 2 / Time: Friday 14:40 - 15:30 / Location: Grandball

The Agile Manifesto was the spark that brought about a shift in how software was being developed and as a result a wave of new Agile Methodologies such as SCRUM, XP, and Continuous Delivery have been introduced as  “better ways of developing software”.  Many development organizations have adopted these agile methodologies to improve their communication, increase customer involvement, and create happier and more efficient software teams.  

Fast forward to today, 13 years later, a discussion has emerged on what has happened since the Agile Manifesto was first published.  Prag Dave Thomas, one of the original 17 authors,  has written a blog post which has been heavily discussed online and on twitter titled "Agile is Dead (Long Live Agility) where he points out that the term "Agile" has become a marketing buzzword for companies and consultants to use as a way to commercialize the ideas behind Agile Software Development.  He also goes on to suggest that developers should program with “agility” rather then hoping solutions that are simply "coined" as  "Agile" will be able to solve some of the difficult problems that they encounter when developing software.

At GOTO, we think it is time to take a closer look at what has happened in the last 13 years since the Agile Manifesto was published and evaluate where the development community is going in the future.

Presentation: A retake on the Agile Manifesto Part II

Track: People & Process - Day 2 / Time: Friday 15:50 - 16:40 / Location: Grandball

The Agile Manifesto was the spark that brought about a shift in how software was being developed and as a result a wave of new Agile Methodologies such as SCRUM, XP, and Continuous Delivery have been introduced as  “better ways of developing software”.  Many development organizations have adopted these agile methodologies to improve their communication, increase customer involvement, and create happier and more efficient software teams.  

Fast forward to today, 13 years later, a discussion has emerged on what has happened since the Agile Manifesto was first published.  Prag Dave Thomas, one of the original 17 authors,  has written a blog post which has been heavily discussed online and on twitter titled "Agile is Dead (Long Live Agility) where he points out that the term "Agile" has become a marketing buzzword for companies and consultants to use as a way to commercialize the ideas behind Agile Software Development.  He also goes on to suggest that developers should program with “agility” rather then hoping solutions that are simply "coined" as  "Agile" will be able to solve some of the difficult problems that they encounter when developing software.

At GOTO, we think it is time to take a closer look at what has happened in the last 13 years since the Agile Manifesto was published and evaluate where the development community is going in the future.