Home > Software Quality Tips > Software Quality Book Excerpts > Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
Software Quality Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

SOFTWARE QUALITY BOOK EXCERPTS

Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams


Alistair Cockburn
02.12.2008
Rating: --- (out of 5)


Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 3 of Agile Software Development: The Cooperative Game, 2nd Edition written by Alistair Cockburn and published by Addison Wesley Professional. "Communicating, Cooperating Teams" addresses issues that need to be considered when adapting an agile methodology to an organization. Cockburn emphasizes the flow of information in a project and how it is affected by seating arrangements and methods of communication. Each project has "information radiators" in the forms of team members, whiteboards, sticky notes and more. The chapter is punctuated by useful anecdotes from industry veterans.



[IMAGE]

Book description:

The agile model of software development has taken the world by storm. Now, in Agile Software Development, Second Edition, one of agile's leading pioneers updates his Jolt Productivity award-winning book to reflect all that's been learned about agile development since its original introduction.

Alistair Cockburn begins by updating his powerful model of software development as a "cooperative game of invention and communication." Among the new ideas he introduces: harnessing competition without damaging collaboration; learning lessons from lean manufacturing; and balancing strategies for communication. Cockburn also explains how the cooperative game is played in business and on engineering projects, not just software development.

Next, he systematically illuminates the agile model, shows how it has evolved, and answers the questions developers and project managers ask most often, including:


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Software Quality Book Excerpts
Perfect Software, Ch. 8: What Makes a Good Test
Seven Steps to Mastering Business Analysis, Ch. 1
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
Inherent Quality Simplicity, Section V: The Evolution
Managing the Test People, Chapter 6: Keeping Your Beast Effective
Mastering the Requirements Process, 2nd Edition: Chapter 2, The Requirements Process

Agile software development
Agile development growing, but problems remain
Agile, IBM tools boost Merge Healthcare's software quality
Agile development reshaping requirements
Agile software development tutorial: How to transition to agile
Agile software development tutorial: Pros and cons of agile
Agile software development tutorial: Agile requirements gathering
Agile software development tutorial: Agile project management, tools
Agile software development tutorial: Agile testing
Reporter's Notebook: Jack Vaughan on agile methodology
Best practices for moving testers from waterfall to agile development

Extreme Programming (XP)
Reporter's Notebook: Jack Vaughan on agile methodology
The challenges of test-driven development (TDD)
How teams transition to agile development methodologies
Adopting continuous integration brings agility, other benefits
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
Software development groups take many routes to Agile
Better software through debugging and unit testing -- Unit testing, Extreme Programming and TDD
Better software through debugging and unit testing -- Other useful resources
Better software through debugging and unit testing
Addressing software quality issues with development models, methods

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
acceptance test  (SearchSoftwareQuality.com)
iteration  (SearchSoftwareQuality.com)
planning board  (SearchSoftwareQuality.com)
planning game  (SearchSoftwareQuality.com)
release  (SearchSoftwareQuality.com)
release plan  (SearchSoftwareQuality.com)
spike  (SearchSoftwareQuality.com)
stand-up  (SearchSoftwareQuality.com)
story  (SearchSoftwareQuality.com)
timebox  (SearchSoftwareQuality.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary




  • Where does agile development fit in our organization?
  • How do we blend agile ideas with other ideas?
  • How do we extend agile ideas more broadly?


  • Cockburn takes on crucial misconceptions that cause agile projects to fail. For example, you'll learn why encoding project management strategies into fixed processes can lead to ineffective strategy decisions and costly mistakes. You'll also find a thoughtful discussion of the controversial relationship between agile methods and user experience design.

    Cockburn turns to the practical challenges of constructing agile methodologies for your own teams. You'll learn how to tune and continuously reinvent your methodologies, and how to manage incomplete communication. This edition contains important new contributions on these and other topics:

  • Agile and CMMI
  • Introducing agile from the top down
  • Revisiting "custom contracts"
  • Creating change with "stickers"


  • In addition, Cockburn updates his discussion of the Crystal methodologies, which utilize his "cooperative game" as their central metaphor.

    If you're new to agile development, this book will help you succeed the first time out. If you've used agile methods before, Cockburn's techniques will make you even more effective.

    >> Read Chapter 3: Communicating, Cooperating Teams.

    >> Buy the book




    This chapter is excerpted from the book, Agile Software Development: The Cooperative Game, 2nd Edition, authored by Alistair Cockburn, published by Addison-Wesley Professional, October, 2006, Copyright Pearson Education, Inc. ISBN 0321482751. For more information please visit: www.awprofessional.com

    Rate this Tip
    To rate tips, you must be a member of SearchSoftwareQuality.com.
    Register now to start rating these tips. Log in if you are already a member.




    DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



    Software Design & Testing - Project Management
    About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
    SEARCH 
    TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

    TechTarget Corporate Web Site  |  Media Kits  |  Site Map




    All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
      TechTarget - The IT Media ROI Experts