Tracking change and innovation in the enterprise software development community
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Posted by Abel Avram on May 19, 2008 06:41 AM
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.
Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Hello, it seems that the links are broken.
now it's ok :-)
"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.
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: http://www.amazon.com/Art-Agile-Development-James-Shore/dp/0596527675
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
4 comments
Reply