InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Interview: James Shore on “The Art of Agile Development”

Posted by Abel Avram on May 19, 2008

Sections
Process & Practices
Topics
Agile ,
Agile Techniques ,
Adopting Agile
Tags
Agile2007 ,
Introducing Agile ,
Book

In this interview taken by InfoQ's Deborah Hartmann during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book “The Art of Agile Development” that he and Shane Warden wrote. The book was not yet published at the time when the interview was made, and James offers a valuable introduction to the book touching various aspects of Agile development.

James considers the book as helpful for developers and teams which have heard of Agile, got interested about it and want to start learning and practicing it. He talks how he and Shane compiled a long list of about 200 Agile techniques, values and ideas, and aggregated them into 17 principles grouped into 5 categories: Improve the Project, Rely on People, Eliminate Waste, Deliver Value and Seek Technical Excellence. He gives some details on how to Eliminate Waste and Seek Technical Excellence.

James also says the book is not offering mainly an Agile methodology, but rather advice on creating successful software. According to James, we need to be successful in the following areas: technical, organizational and personal. We need technical success in order to create high quality software which lasts the test of time. We need organizational success because otherwise we cannot sell software no matter how good it is. We also need personal success because we are humans and we need to have a sense of accomplishment beside that obtained by writing a good piece of software.

The entire interview is 30 minutes long.

resource not found by Michal Fijas Posted
Re: resource not found by Michal Fijas Posted
Dirty word in the book title by Jim Leonardo Posted
O'Reilly link expired by James Shore Posted
  1. Back to top

    resource not found

    by Michal Fijas

    Hello,

    it seems that the links are broken.

  2. Back to top

    Re: resource not found

    by Michal Fijas

    now it's ok :-)

  3. Back to top

    Dirty word in the book title

    by Jim Leonardo

    "Art"... nothing in software development is an "art". It's all completely predictable, based on well known problem domains, and anyone can be taught to do it with 2 weeks of power point based training with some trivial 'lab' work.

    We now return you to a sarcasm free zone.

  4. Back to top

    O'Reilly link expired

    by James Shore

    I should add that the O'Reilly discount mentioned at the end of the interview has expired and the link no longer works. Amazon has the book for 14% off here: www.amazon.com/Art-Agile-Development-James-Shor...

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.