InfoQ

News

Book Excerpt: Agile Software Development, 2nd ed.

Posted by Deborah Hartmann on Oct 30, 2006 02:00 AM

Community
Agile
Topics
Methodologies,
Stories & Case Studies
Tags
Agile Manifesto,
History,
Crystal
Agile Software Development: The Cooperative Game (2nd Edition), Alistair Cockburn's new update to his classic work, was published last week by Addison-Wesley.   This second edition profits from five more years of practice and research, expanding the author's ideas even further, into the domains of business and engineering projects.  Though he's added content to the book in the new "Evolutions" chapters, the basics have not changed. In the InfoQ exclusive excerpt from Chapter 1, Cockburn is once again encouraging us to think about software development as a "cooperative game of invention and communication.”

Cockburn observes that software development is difficult to talk about - it's at once disciplined and exploratory, mathematical and artistic, so he has chosen to come at it in a unique way.  In this introductory chapter, Cockburn uses analogies to examine what we do, asking “What would the experience of developing software be like if it were not software we were developing?” He uses examples from both his own art form (poetry) and from co-operative games like rock-climbing, to explore other ways of thinking and talking about software development, providing new mental models for teams that want to develop better processes.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

1 comment

Reply

sdf by Jan Fredrik Øveraasen Posted Jan 9, 2007 2:04 AM

  1. Back to top

    sdf

    Jan 9, 2007 2:04 AM by Jan Fredrik Øveraasen

    dsf

    Reply

Exclusive Content

Agile and Beyond - The Power of Aspirational Teams

Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.

Concurrency: Past and Present

Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.

ActionScript 3 for Java Programmers

Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.

Neal Ford On Programming Languages and Platforms

Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.

Future Directions for Agile

David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.

Nick Sieger on JRuby

Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.

Rustan Leino and Mike Barnett on Spec#

Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.

10 Ways to Screw Up with Scrum and XP

Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.