Agile software development : the cooperative game

“Agile Software Development is a highly stimulating and rich book. The author has a deep background and gives us a tour de force of the emerging agile methods.” –Tom Gilb The agile model of software development has taken the world by storm. Now, in Agile Software Development, Second Edition , one of...

Descripción completa

Detalles Bibliográficos
Otros Autores: Cockburn, Alistair Author (author)
Formato: Libro electrónico
Idioma:Inglés
Publicado: [Place of publication not identified] Addison Wesley 2007
Edición:2nd ed
Colección:Agile software development series
Agile Software Development
Materias:
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627186206719
Tabla de Contenidos:
  • Cover
  • CONTENTS
  • LIST OF FIGURES
  • LIST OF STORIES
  • PREFACE
  • PREFACE TO 2ND EDITION
  • 0 UNKNOWABLE AND INCOMMUNICABLE
  • The Problem with Parsing Experience
  • The Impossibility of Communication
  • Three Levels of Listening
  • So, What Do I Do Tomorrow?
  • 0.1 UNKNOWABLE AND INCOMMUNICABLE: EVOLUTION
  • Communication and Shared Experience
  • Shu-Ha-Ri
  • CHAPTER 1 A COOPERATIVE GAME OF INVENTION AND COMMUNICATION
  • Software and Poetry
  • Software and Games
  • A Second Look at the Cooperative Game
  • What Should This Mean to Me?
  • CHAPTER 1.1 A COOPERATIVE GAME OF INVENTION AND COMMUNICATION: EVOLUTION
  • The Swamp Game
  • Competition Within Cooperation
  • Other Fields as Cooperative Games
  • Software Engineering Reconstructed
  • CHAPTER 2 INDIVIDUALS
  • Them's Funky People
  • Overcoming Failure Modes
  • Working Better in Some Ways than Others
  • Drawing on Success Modes
  • What Should I Do Tomorrow?
  • CHAPTER 2.1 INDIVIDUALS: EVOLUTION
  • Strategy Balancing
  • CHAPTER 3 COMMUNICATION, COOPERATING TEAMS
  • Convection Currents of Information
  • Jumping Communication Gaps
  • Teams as Communities
  • Teams as Ecosystems
  • What Should I Do Tomorrow?
  • CHAPTER 3.1 TEAMS: EVOLUTION
  • A Sample Office Layout Revisited
  • CHAPTER 4 METHODOLOGIES
  • An Ecosystem That Ships Software
  • Methodology Concepts
  • Methodology Design Principles
  • XP under Glass
  • Why Methodology at All?
  • What Should I Do Tomorrow?
  • CHAPTER 4.1 METHODOLOGIES: EVOLUTION
  • Methodologies versus Strategies
  • Methodologies across the Organization
  • Process as Cycles
  • Describing Methodologies More Simply
  • CHAPTER 5 AGILE AND SELF-ADAPTING
  • Light but Sufficient
  • Agile
  • Becoming Self-Adapting
  • What Should I Do Tomorrow?
  • CHAPTER 5.1 AGILE AND SELF-ADAPTING: EVOLUTION
  • Misconstruing the Message
  • Evolution of the Agile Methodologies.
  • New Methodology Topics
  • Persistent Questions
  • Agile Outside Software Development
  • CHAPTER 6 THE CRYSTAL METHODOLOGIES
  • Shaping the Crystal Family
  • Crystal Clear
  • Crystal Orange
  • Crystal Orange Web
  • What Should I Do Tomorrow?
  • CHAPTER 6.1 THE CRYSTAL METHODOLOGIES: EVOLUTION
  • The Crystal Genetic Code
  • Crystal Clear
  • Stretching Crystal Clear to Yellow
  • APPENDIX A: THE AGILE SOFTWARE DEVELOPMENT MANIFESTO
  • The Agile Alliance
  • The Manifesto
  • Supporting the Values
  • APPENDIX A.1 THE AGILE SOFTWARE DEVELOPMENT MANIFESTO AND THE DECLARATION OF INTERDEPENDENCE
  • The Agile Manifesto Revisited
  • The Declaration of Interdependence
  • APPENDIX B: NAUR, EHN, MUSASHI
  • Peter Naur, Programming as Theory Building
  • Pelle Ehn, Wittgenstein's Language Games
  • Musashi
  • APPENDIX B.1 NAUR, EHN, MUSASHI: EVOLUTION
  • Naur
  • Ehn
  • Musashi
  • APPENDIX C: AFTERWORD
  • Agile Software Development
  • Business as a Cooperative Game
  • Leadership
  • Everyone
  • APPENDIX D: BOOKS AND REFERENCES
  • INDEX.