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: 20 Mar to 27 Mar 2002
Nanduri, V Rao: (Mascot Systems ltd) I am keen on knowing every aspect of this new movement. I am also keen to contribute to this effort. Please do let me know how I can be a part of this.
Marcus Ahnve: (Lecando AB)
Padraic Mahon: ( )
Karl Scotland: (BBC Interactive) Thank you!
Fan Li: (Merck & Co., Inc) I have been following the movements of lightweight methodologies for a while. And I think they can improve development process for many software projects.
Ricardo Bánffy: (http://www.dieblinkenlights.com) We all felt it deep in our hearts there ought to be a better way. Yet, we could not see it, blinded as we were by our firm belief building software was like building bridges. Thank you, folks. We feel much lighter now.
Lars Gendner: (Sony NetServices) because it trusts in the competence and autonomy of the individuals participating in a project.
John Ng.
ben wong.
Markus Voelter: (MATHEMA AG)
Steve Berczuk: (http://www.berczuk.com)
James Ruddock: (The Quetico Group)
Joe Parks: (EDS)
Nicholas Crown: Software developement is a discipline whose foundation is grounded on the innovation and imagination of the individual engineer.
Dwight Wilson: (Independent Consultant)
Mayank Tandon: (Webmasters India) I am still in the process of completely imbibing the ideology of Agile manifesto but it seems this is an interesting development that acknowledges the shortcomings of traditional software development models in light of their failure to take into consideration human factors while enabling a highly critical development cycle with common sense. Would be interested in contributing whatever we can to promote the idea....
Fred Ballard.
Craig Dewalt: I support the Agile Manifesto because I have a sincere desire to build quality, practical software on time and within budget.
Martin Andrews: (Object Oriented Pty. Ltd.) The manifesto describes a set of values that we should all strive to encompass in our daily work. As new ideas and techniques become popular in the changing world of software development, these values can still hold as strong underlying principles. We should ensure that we never lose that focus.
Samir Rajguru: This is by far the best way to develop software.
Patrick Krook: (Silicon Corn) Agile Methods hold a promise to bring the focus back to what makes development an enjoyable and entelechial pursuit, free from the spectors of "Death by Planning" and other negative solutions.
Rodrigo Furlan: (Elucid Partners SA) Joerg Seebohn: (http://www.s.netic.de/jseebohn) To find a way of harmony between a set of rules and creative chaos in a satisfactory way for the customers and the developers - this is a divine talent.
Celio Vasconcellos: Great !!!! Full support to this alliance is very important in the software industry. After years reading books and experincing x-thousand methodologies in projects, it is time to handle directly with all problems, those known since decades.
Mikael Börjesson: (Callista Knowledgebase AB)
Matson Lopes da Silva.
Paul Firgens.
Hudson Bonomo: Salve! I agree.
Ioakeim Tzanetis.
Rick Wilkes: (Healthnotes, Inc.) Great success comes from teams who love being responsive and are given an appropriate, liberating context within which to create.
Rob Schripsema: (Integra Software and Services) As critical as proper engineering, design and documentation are to the end result, they often place a stranglehold on the more creative, elegant aspects of software development. I've struggled for years with how to balance the two sides. I fully support what the Agile Alliance is doing to help us keep the proper balance!
Chris Jordan: (cjaxx)
Rogier Hofboer: I have been using this method without knowing its name. It is the only method I have actually seen working.
Sanford Redlich: (CNET)
Chris Ringrow: (i2i) I strongly agree that the key to successful software development is the team rather than the process. However in order for that to work the team members needs to communicate effectively not only with each other but with customers, managers and investors. At the end of the day it is good communications at all levels that makes a successful project possible.
David Intersimone "David I": (Borland Software Corporation) Borland has always been a part of changing the way software is developed. We believe in small teams of developers collaborating together. We also encourage freedom of choice in platforms, open standards, languages, tools, methodologies, and more.
David Hicks: (RADTAC Ltd.) Here at RADTAC we help our clients employ the very best IT practices and the very best IT solutions, to deliver real capability improvements and return on investment. Agile methods are vital to this. We wholeheartedly support the Agile Alliance.
Marc Elbirt: (Softmarc Canada) It is a better way
Ole Erecius: (ChangeGroup) Freedom of mind, flexibility, collaboration, minimal overhead and the strive for results. I love it - just as I love the "dogme" films: www.tvropa.com/ tvropa1.2/ film/ dogme95
Samanth Athrey. Jordi Gonzalez : (Avanade) I agree with the Agile manifest, during my experience as developers I tried to apply with more or less successful the principals of you manifest.
Dave Thomas: (Bedarra Corp) Software is built by people supported by tools and a process. The AgileAlliance promotes the Joy of Building Software Together, and promotes best practices. Dave
Robert W. Howell: (Independant) I have been using this methodology intuitively for years. It is good to see someone finally put it down in writing. Now I can actually put a name on it when someone asks me what mthodology I favor. I usually work alone or with small teams (less that 5 people) and I have always followed what I called "the Patented (not really) Bob Howell system of software development." ;-) I even used this back in the early eighties when I was programming on Data General Mini's in COBOL. When you think about it, it is really an allegory of the old "The customer is always right." rule of successful business practice. The point is I hate micro-engineering, where you try to completely spec out a project before writing one line of code. I've seen these projects go for two years with zero to show except reams of documents that no one can remember what they are for. My philosophy is, get the basic business process down, then prototype and iterate. Give the customer something to work with other than reams of specs they have to approve. One other thing, It IS important to have a flexible software framework to build on. I have a framework that I have used on several jobs. It evolves some from job to job but it makes development much faster. The framework handles things like user authentication, form and window management, etc. Spend the time up front to engineer a framework you are comfortable with or you may end up with a code base that is unmanageable. As a development manager that should be where you spend your time.
Gerry Simblett: (UK Freelance Developer) I am really excited by agile software development. Agile methodologies provide a win-win solution for everyone involved (except for perhaps the pointy-haired bosses of this world!). I thoroughly endorse and try to apply these principles whenever I can.
Gab Scali: (Space SpA)
Alexandre Junqueira: (INMETRICS)
Roland Caron: (Rogue Bear Software) Customer satisfaction thru quality software, a novel concept -lets hope it catches on.
ian walker: (spherion)
Pete Hanson: As an IT professional of 32 years standing, I have seen processes, tools, and documentation come and go, and there seems to be no end in sight. I am, and have been without realizing it, a long-standing advocate of the Agile Software Development Manifesto, and am very pleased to see rationality and reality being brought back to our profession.
Rolando Gabarron: (INTesa)

<< Previous Index Next >>

Signatures Received: 20 Mar to 27 Mar 2002
Nanduri, V Rao: (Mascot Systems ltd) I am keen on knowing every aspect of this new movement. I am also keen to contribute to this effort. Please do let me know how I can be a part of this. Marcus Ahnve: (Lecando AB) Padraic Mahon: ( ) Karl Scotland: (BBC Interactive) Thank you! Fan Li: (Merck & Co., Inc) I have been following the movements of lightweight methodologies for a while. And I think they can improve development process for many software projects. Ricardo Bánffy: (http://www.dieblinkenlights.com) We all felt it deep in our hearts there ought to be a better way. Yet, we could not see it, blinded as we were by our firm belief building software was like building bridges. Thank you, folks. We feel much lighter now. Lars Gendner: (Sony NetServices) because it trusts in the competence and autonomy of the individuals participating in a project. John Ng. ben wong. Markus Voelter: (MATHEMA AG) Steve Berczuk: (http://www.berczuk.com) James Ruddock: (The Quetico Group) Joe Parks: (EDS) Nicholas Crown: Software developement is a discipline whose foundation is grounded on the innovation and imagination of the individual engineer. Dwight Wilson: (Independent Consultant) Mayank Tandon: (Webmasters India) I am still in the process of completely imbibing the ideology of Agile manifesto but it seems this is an interesting development that acknowledges the shortcomings of traditional software development models in light of their failure to take into consideration human factors while enabling a highly critical development cycle with common sense. Would be interested in contributing whatever we can to promote the idea.... Fred Ballard. Craig Dewalt: I support the Agile Manifesto because I have a sincere desire to build quality, practical software on time and within budget. Martin Andrews: (Object Oriented Pty. Ltd.) The manifesto describes a set of values that we should all strive to encompass in our daily work. As new ideas and techniques become popular in the changing world of software development, these values can still hold as strong underlying principles. We should ensure that we never lose that focus. Samir Rajguru: This is by far the best way to develop software. Patrick Krook: (Silicon Corn) Agile Methods hold a promise to bring the focus back to what makes development an enjoyable and entelechial pursuit, free from the spectors of "Death by Planning" and other negative solutions. Rodrigo Furlan: (Elucid Partners SA)	Joerg Seebohn: (http://www.s.netic.de/jseebohn) To find a way of harmony between a set of rules and creative chaos in a satisfactory way for the customers and the developers - this is a divine talent. Celio Vasconcellos: Great !!!! Full support to this alliance is very important in the software industry. After years reading books and experincing x-thousand methodologies in projects, it is time to handle directly with all problems, those known since decades. Mikael Börjesson: (Callista Knowledgebase AB) Matson Lopes da Silva. Paul Firgens. Hudson Bonomo: Salve! I agree. Ioakeim Tzanetis. Rick Wilkes: (Healthnotes, Inc.) Great success comes from teams who love being responsive and are given an appropriate, liberating context within which to create. Rob Schripsema: (Integra Software and Services) As critical as proper engineering, design and documentation are to the end result, they often place a stranglehold on the more creative, elegant aspects of software development. I've struggled for years with how to balance the two sides. I fully support what the Agile Alliance is doing to help us keep the proper balance! Chris Jordan: (cjaxx) Rogier Hofboer: I have been using this method without knowing its name. It is the only method I have actually seen working. Sanford Redlich: (CNET) Chris Ringrow: (i2i) I strongly agree that the key to successful software development is the team rather than the process. However in order for that to work the team members needs to communicate effectively not only with each other but with customers, managers and investors. At the end of the day it is good communications at all levels that makes a successful project possible. David Intersimone "David I": (Borland Software Corporation) Borland has always been a part of changing the way software is developed. We believe in small teams of developers collaborating together. We also encourage freedom of choice in platforms, open standards, languages, tools, methodologies, and more. David Hicks: (RADTAC Ltd.) Here at RADTAC we help our clients employ the very best IT practices and the very best IT solutions, to deliver real capability improvements and return on investment. Agile methods are vital to this. We wholeheartedly support the Agile Alliance. Marc Elbirt: (Softmarc Canada) It is a better way Ole Erecius: (ChangeGroup) Freedom of mind, flexibility, collaboration, minimal overhead and the strive for results. I love it - just as I love the "dogme" films: www.tvropa.com/ tvropa1.2/ film/ dogme95 Samanth Athrey.	Jordi Gonzalez : (Avanade) I agree with the Agile manifest, during my experience as developers I tried to apply with more or less successful the principals of you manifest. Dave Thomas: (Bedarra Corp) Software is built by people supported by tools and a process. The AgileAlliance promotes the Joy of Building Software Together, and promotes best practices. Dave Robert W. Howell: (Independant) I have been using this methodology intuitively for years. It is good to see someone finally put it down in writing. Now I can actually put a name on it when someone asks me what mthodology I favor. I usually work alone or with small teams (less that 5 people) and I have always followed what I called "the Patented (not really) Bob Howell system of software development." ;-) I even used this back in the early eighties when I was programming on Data General Mini's in COBOL. When you think about it, it is really an allegory of the old "The customer is always right." rule of successful business practice. The point is I hate micro-engineering, where you try to completely spec out a project before writing one line of code. I've seen these projects go for two years with zero to show except reams of documents that no one can remember what they are for. My philosophy is, get the basic business process down, then prototype and iterate. Give the customer something to work with other than reams of specs they have to approve. One other thing, It IS important to have a flexible software framework to build on. I have a framework that I have used on several jobs. It evolves some from job to job but it makes development much faster. The framework handles things like user authentication, form and window management, etc. Spend the time up front to engineer a framework you are comfortable with or you may end up with a code base that is unmanageable. As a development manager that should be where you spend your time. Gerry Simblett: (UK Freelance Developer) I am really excited by agile software development. Agile methodologies provide a win-win solution for everyone involved (except for perhaps the pointy-haired bosses of this world!). I thoroughly endorse and try to apply these principles whenever I can. Gab Scali: (Space SpA) Alexandre Junqueira: (INMETRICS) Roland Caron: (Rogue Bear Software) Customer satisfaction thru quality software, a novel concept -lets hope it catches on. ian walker: (spherion) Pete Hanson: As an IT professional of 32 years standing, I have seen processes, tools, and documentation come and go, and there seems to be no end in sight. I am, and have been without realizing it, a long-standing advocate of the Agile Software Development Manifesto, and am very pleased to see rationality and reality being brought back to our profession. Rolando Gabarron: (INTesa)