Agile Manifesto Signatories

Independent Signatories of
The Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Signatures Received: 07 Feb to 19 Feb 2002
Marco Dorantes: (*Own experience*) Methods and techniques that really help in the trenches, where the software actually is created
Stefan Schmiedl: (Approximity GmbH)
Afik Gal.
Alexander Kjerulf: (Enterprise Systems)
Dan Johnsson: (Frobozz AB) Interhuman collaboration between developer and user in focus; not administration and formalities.
Martin Lippert: (Workplace Solutions GmbH)
Thomas Hetzer: (develop group) That is the way how software should be developed. I fully support the manifesto.
Stephan Wiesebach: (Siemens AG) After long and heavy fights between the process gurus representing the light-, heavy- or middleweight processes we now have a metaphor to support "common-sense-behaviour" in software projects. IMHO the "agile"-metaphor complements the thoughts about improving processes with process patterns nicely.
Jutta Eckstein: (Objects in Action) I support the agile alliance manifesto, because it supports finally bringing back the processes to the people.
Luc Duranleau: (ICI Design) For many years I was psychologically harassed for my unorthodox ways of driving software engineering projects. I never used any prescribed method or very elaborate documentation schemes, especially if it meant cutting down trees to produce 6 inch binders that quickly got lost on some shelf. Essentially, my approach to software design has always been based on verbal communication with all knowledge levels; anyone who could enrich the comprehensive perspective of the goals to attain and the long term vision to respect. Always striving to attain that momentum and motivation that nourrishes the instinct for initiative and willpower that inevitably determines the success of the software endeavor. I encourage any interaction that will enlighten those lonely isolated software developers in their small yet infinite kingdoms. Software design is a crystal-like reflection of the cohesiveness of this diversity of minds. I am very happy to hear I am no longer alone in this quest for simplicity of design for simplicity of life. Luc
Gilbert Semmer.
Sabine Noack: (43 - Sabine Noack) One of the most important aspects of my work as a trainer and consultant is to remind people that developing software is not simply an act of industrial production. The Agile Alliance Manifesto tells us why software development is different and what we should consider to make it successfull as well as enjoyable.
Andreas Stankewitz: (Naradana) Agile software development - because software development is working with people, not working with resources.
Patrick Morrison: (Virtual Pragmatics) 19 years experience programming professionally convince me that the values expressed in the agile manifesto produce the best software and the best releationships between business and techs. The successes I've seen in my career link to the values expressed, and the failures often tie to valuing something else.
Sriram: (Icode )
michele mondora: (mindview) One manifesto to agile them all! (Lord of Rings) Ulrich Winter: I hope that an agile process is able to remove the overhead and dissatisfaction which I currently feel in my projects.
Matthieu Colas-Bara: (KHIPLEA) The rules of the Agile Manifesto formalize what happens naturally when people of good will do their best to collaborate and succeed in software developpement. Object developpers know it from the beginning, it's now time to educate managers.
Alex Rush: (ExperShare) I come from somewhat of a more traditionalist "heavyweight" development method background, and am on a constant mission to pare down to only the essential artifacts and activities necessary to deliver quality code. I support the basic aims of the Manifesto, and look forward to its evolution.
Martin Gottschalk: (OmnesWeb) People must work together to have fun and success. I like it.
Berthold Schreiber: (OmnesWeb)
Peter Gassmann.
Kirill Maximov: (maxkir.com)
Chad Kopca: (5/3 Bancorp) Now all I have to do is inject the truth.
amouda: (Pondicherry University) I am interested to become a member of Agile software Development Manifesto.
Chris Pilsworth: (Gedas United Kingdom Ltd.)
Ozgur Aksakal: (http://www.ozgur-aksakal.com) To build better software that meets requirements, and behaves as expected.
Everett A. Warren: The values may seem simple and commonsense, but since when was commonsense very common? Agreeing with these values and actually putting them into practice are two different things, and I'm very glad to be in a position where I can push for the latter and come up with some better software.
Klaus Marquardt: It is no secret: in a healthy project, the process follows the people and their needs, not vice versa. Every stakeholder in a software project can learn from this.
Barry Fazackerley: (DSDM) As chairman of the DSDM Consortium I am proud that DSDM is associated with Agile. DSDM is built upon nine principles. The Agile values of Individuals and interactions, Working software, Customer collaboration and Responding to change align themselves very closely to the DSDM Principles.
Richard Couch: Preaching and teaching the Agile way.
Pete Clark: (pclark.net Consulting, LLC) The ideas expressed by XP and agile methods encompass ideas that have felt right since I started managing software projects. It's great to see more attention being paid to understanding how to make software development go in the real world - where requirements aren't fixed, where change is a fact of life, and where the development team needs all the help it can get.
Eric Thoman: (Manchester JUG) Focus on quality and quantity will take care of itself...
Daniel Read: (developer.*) I agree wholeheartedly.
Robb Gilmore: (Descartes Systems Group) Over the years, I have arrived at many of the very same conclusions that are so succinctly stated by the Agile Alliance. It is refreshing (and much more efficient) to point colleagues to the Agile Manifesto rather than repeating the same old stump speeches time and time again! I support the manifesto. Grigori Melnik: (Southern Alberta Institute of Technology (SAIT)) Eureka!
Roger Marlow: (m.a.partners) As a software developer and more recently a development manager, my most successful projects have used aspects of Agile Methods, although I didn't have a name for it at the time. Even so, for a long time the prevailing methods were frustrating bureaucratic failures. It seemed that the common sense and essentially agile approach espoused by Fred Brooks all those years ago would fade into history while modern methodologists espoused 'fat book' processes. Agile Methods are therefore a refreshing return to common sense basics. They bring together the best of the experiences we have all been through in software development and that we have informally known about for years. At last we have a self consistent framework for all our anecdotal evidence from successful projects. I believe that the advent of Agile Methods signal a revolution in the software development industry and promise exciting times for us all.
peter gabris: (bsp) as good as it gets
Robert S. Teich - President: (Software Teknovations, Inc.)
Daryl Winters: (Component Architects)
balachandar: (CGI) I am very much interested
Peter Lindberg: (Oops AB, Sweden) Yes!
Edward Atwell.
R.Bruinsma: (Bugando) I fully agree to your statements. I'm inclined to write here many pages of thoughts on this subject, but I save that for my thesis on the subject. Anyone who is willing to collaborate in writing a thesis is invited to send me an mail about the subject.
Marcelo Schenone: (FIUBA)
Ralph W. Boaz: (Pillar Consulting) I have filled a lot of roles in my career including software engineering, ministry, and senior management. Agile development is a breakthrough in understanding the keys to success and failure. It is the first to really address the people element which has been ignored for so long. Thank you to the Agile founders.
Scott Bechtel: (Conquest Solutions Group) After being in projects that always drag in over due it has been fun learning about this new approach!
Mario Wittler.
Shawn Lyndon: (ePredix) I feel like one of those people on a talk show when I talk about Agile Development to people new to the concepts and ideals. In all honesty, I don't know how I managed the software development process before these very practical and customer focused ideals where brought together under one banner. We are I am certain seeing a very big change in how people approach software development and design. Putting the businnes need or problem above the implementation detail is a key goal in our efforts in our company. Or as we like to generalize ... Find the 'Why?' and the 'What?' ... The 'How?' is not so important.
Erik Groeneveld: (CQ2) As consultant working in the Netherlands, I'm using the AAM principles as a starting point for organizing my projects. Amazing to see how many organizations just skip team and customer collaboration and put all their faith on heavy processes. In 2000, Willem van den Ende and I installed the Dutch XP group: www.xp-nl.org.

<< Previous Index Next >>

Signatures Received: 07 Feb to 19 Feb 2002
Marco Dorantes: (Own experience) Methods and techniques that really help in the trenches, where the software actually is created Stefan Schmiedl: (Approximity GmbH) Afik Gal. Alexander Kjerulf: (Enterprise Systems) Dan Johnsson: (Frobozz AB) Interhuman collaboration between developer and user in focus; not administration and formalities. Martin Lippert: (Workplace Solutions GmbH) Thomas Hetzer: (develop group) That is the way how software should be developed. I fully support the manifesto. Stephan Wiesebach: (Siemens AG) After long and heavy fights between the process gurus representing the light-, heavy- or middleweight processes we now have a metaphor to support "common-sense-behaviour" in software projects. IMHO the "agile"-metaphor complements the thoughts about improving processes with process patterns nicely. Jutta Eckstein: (Objects in Action) I support the agile alliance manifesto, because it supports finally bringing back the processes to the people. Luc Duranleau: (ICI Design) For many years I was psychologically harassed for my unorthodox ways of driving software engineering projects. I never used any prescribed method or very elaborate documentation schemes, especially if it meant cutting down trees to produce 6 inch binders that quickly got lost on some shelf. Essentially, my approach to software design has always been based on verbal communication with all knowledge levels; anyone who could enrich the comprehensive perspective of the goals to attain and the long term vision to respect. Always striving to attain that momentum and motivation that nourrishes the instinct for initiative and willpower that inevitably determines the success of the software endeavor. I encourage any interaction that will enlighten those lonely isolated software developers in their small yet infinite kingdoms. Software design is a crystal-like reflection of the cohesiveness of this diversity of minds. I am very happy to hear I am no longer alone in this quest for simplicity of design for simplicity of life. Luc Gilbert Semmer. Sabine Noack: (43 - Sabine Noack) One of the most important aspects of my work as a trainer and consultant is to remind people that developing software is not simply an act of industrial production. The Agile Alliance Manifesto tells us why software development is different and what we should consider to make it successfull as well as enjoyable. Andreas Stankewitz: (Naradana) Agile software development - because software development is working with people, not working with resources. Patrick Morrison: (Virtual Pragmatics) 19 years experience programming professionally convince me that the values expressed in the agile manifesto produce the best software and the best releationships between business and techs. The successes I've seen in my career link to the values expressed, and the failures often tie to valuing something else. Sriram: (Icode ) michele mondora: (mindview) One manifesto to agile them all! (Lord of Rings)	Ulrich Winter: I hope that an agile process is able to remove the overhead and dissatisfaction which I currently feel in my projects. Matthieu Colas-Bara: (KHIPLEA) The rules of the Agile Manifesto formalize what happens naturally when people of good will do their best to collaborate and succeed in software developpement. Object developpers know it from the beginning, it's now time to educate managers. Alex Rush: (ExperShare) I come from somewhat of a more traditionalist "heavyweight" development method background, and am on a constant mission to pare down to only the essential artifacts and activities necessary to deliver quality code. I support the basic aims of the Manifesto, and look forward to its evolution. Martin Gottschalk: (OmnesWeb) People must work together to have fun and success. I like it. Berthold Schreiber: (OmnesWeb) Peter Gassmann. Kirill Maximov: (maxkir.com) Chad Kopca: (5/3 Bancorp) Now all I have to do is inject the truth. amouda: (Pondicherry University) I am interested to become a member of Agile software Development Manifesto. Chris Pilsworth: (Gedas United Kingdom Ltd.) Ozgur Aksakal: (http://www.ozgur-aksakal.com) To build better software that meets requirements, and behaves as expected. Everett A. Warren: The values may seem simple and commonsense, but since when was commonsense very common? Agreeing with these values and actually putting them into practice are two different things, and I'm very glad to be in a position where I can push for the latter and come up with some better software. Klaus Marquardt: It is no secret: in a healthy project, the process follows the people and their needs, not vice versa. Every stakeholder in a software project can learn from this. Barry Fazackerley: (DSDM) As chairman of the DSDM Consortium I am proud that DSDM is associated with Agile. DSDM is built upon nine principles. The Agile values of Individuals and interactions, Working software, Customer collaboration and Responding to change align themselves very closely to the DSDM Principles. Richard Couch: Preaching and teaching the Agile way. Pete Clark: (pclark.net Consulting, LLC) The ideas expressed by XP and agile methods encompass ideas that have felt right since I started managing software projects. It's great to see more attention being paid to understanding how to make software development go in the real world - where requirements aren't fixed, where change is a fact of life, and where the development team needs all the help it can get. Eric Thoman: (Manchester JUG) Focus on quality and quantity will take care of itself... Daniel Read: (developer.) I agree wholeheartedly. Robb Gilmore*: (Descartes Systems Group) Over the years, I have arrived at many of the very same conclusions that are so succinctly stated by the Agile Alliance. It is refreshing (and much more efficient) to point colleagues to the Agile Manifesto rather than repeating the same old stump speeches time and time again! I support the manifesto.	Grigori Melnik: (Southern Alberta Institute of Technology (SAIT)) Eureka! Roger Marlow: (m.a.partners) As a software developer and more recently a development manager, my most successful projects have used aspects of Agile Methods, although I didn't have a name for it at the time. Even so, for a long time the prevailing methods were frustrating bureaucratic failures. It seemed that the common sense and essentially agile approach espoused by Fred Brooks all those years ago would fade into history while modern methodologists espoused 'fat book' processes. Agile Methods are therefore a refreshing return to common sense basics. They bring together the best of the experiences we have all been through in software development and that we have informally known about for years. At last we have a self consistent framework for all our anecdotal evidence from successful projects. I believe that the advent of Agile Methods signal a revolution in the software development industry and promise exciting times for us all. peter gabris: (bsp) as good as it gets Robert S. Teich - President: (Software Teknovations, Inc.) Daryl Winters: (Component Architects) balachandar: (CGI) I am very much interested Peter Lindberg: (Oops AB, Sweden) Yes! Edward Atwell. R.Bruinsma: (Bugando) I fully agree to your statements. I'm inclined to write here many pages of thoughts on this subject, but I save that for my thesis on the subject. Anyone who is willing to collaborate in writing a thesis is invited to send me an mail about the subject. Marcelo Schenone: (FIUBA) Ralph W. Boaz: (Pillar Consulting) I have filled a lot of roles in my career including software engineering, ministry, and senior management. Agile development is a breakthrough in understanding the keys to success and failure. It is the first to really address the people element which has been ignored for so long. Thank you to the Agile founders. Scott Bechtel: (Conquest Solutions Group) After being in projects that always drag in over due it has been fun learning about this new approach! Mario Wittler. Shawn Lyndon: (ePredix) I feel like one of those people on a talk show when I talk about Agile Development to people new to the concepts and ideals. In all honesty, I don't know how I managed the software development process before these very practical and customer focused ideals where brought together under one banner. We are I am certain seeing a very big change in how people approach software development and design. Putting the businnes need or problem above the implementation detail is a key goal in our efforts in our company. Or as we like to generalize ... Find the 'Why?' and the 'What?' ... The 'How?' is not so important. Erik Groeneveld: (CQ2) As consultant working in the Netherlands, I'm using the AAM principles as a starting point for organizing my projects. Amazing to see how many organizations just skip team and customer collaboration and put all their faith on heavy processes. In 2000, Willem van den Ende and I installed the Dutch XP group: www.xp-nl.org.