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: 11 Jan to 18 Feb 2003
Vera Peeters: (Tryx) You may be proposing a nice xp-ish process you've seen working before, but if it doesn't click for this team, you have to change the process -because the individuals are more important- even though your contract with the customer stated 'introduce xp for us'. This is the true meaning of responding to change... :-)
Dorai Thodla: (iMorph, Inc.)
Sanjay Raghavan: (Masters Student) It's exciting. A focus on people is a catalyst for new ideas.
Jane Hao.
Dieter Eickstaedt: (deiCon Softwareservice GmbH) As an Open Source Evangelist, I strongly support the manifest as the basis for good and professional Free Software Projects.
Stefan Schuerger: (AMDOCS Germany) This is a "back to business" approach, very much agreeable. I've seen too many cases of over-regulation, where one couldn't see the woods for all the trees... With reduced procedure overhead, we can provide more value for our customers.
Jane Hao: I am a Chinese software engineer and my concerntration area was CMM in my graduate study. I am quite interest in Agile and support the Agile Manifesto!
Edgar Sánchez: (Objeq) We develop software in Ecuador, Southamerica. In cash-constrained environments like Latin American countries it becomes even more important to deliver as early as possible working software. Not to talk about the constant turmoil in the region, change down here more than a constant is almost a disease. Thus, I deeply feel that for countries like mine the principles of the Agile Manifesto more than a good option are question of survival.
Ann Godfrey: (Suncorp) I am a relative newcomer to Agile, developing and implementing the process into a banking environment whose general community are totally indoctrinated in 'heavy' process, methodologies and documentation. It's been an interesting year, but I am convinced that this is a valuable and practicable model for them - particularly in light of the trends toward Web developing for banking/finance.
Manoj Khanna: (Eversun Software Corporation) We have been practicing agile methodologies for a couple of years now. And we have been able to produce best results, were able to deliver on time and cut our costs and resources too. We believe that agile methods are the way to success, and they fulfill the stringent requirements of a large to mid-scale level software projects. Without it a manager would be handicap as they have been for many years now. Its time for a change, its time to be agile.
Volker Brandt: (develop group) I really appreciate the publication of the agile manifest. It should be learned by heart and followed by all developers and project managers out there.
Martin Leclerc: I have tried it. Never seen such happy customers :-)
Robert McMichael: Done right, with true commitment to these ideals, the results are a beautiful thing to behold. Done in half measures, a tragedy of what might have been.
George V. Woodrow III.
Jaroslaw Borelowski: (NEUROSOFT) Ali Kousari: (Algotech SA) I am supporting Agile. Tired of being inneficient and listening to the managerial bullshit (excuse the language but this is not a technical paper). Plz standby
Bruce Woods: (NOLA Computer Services) We have been using Agile methods, specifically XP, since January 2000. The way software evolves in an agile development is natural. Our customers benefit from seeing, touching and using the software earlier in the development process than a typical waterfall development. Also, our customers appreciate receiving a new release of software much more than a document indicating what software they may or may not receive in the future.
Jerry Smetzer: (State of Alaska - Department of Fish and Game) I'm very interested in your user-oriented approach to building apps, and am trying to apply the major features of it to our new projects.
Mike Kenworthy: Please convey this to the Software Engineering Institute at Carnegie Mellon University. They are operating in the dark, very dark ages, and their client, the US Government, is suffering because of this.
Antony Grinyer: Being a software developer in the industry I am at constant exposure to the many problems associated with the development lifecycle. In my opinion the agile manifesto is the most exciting and 'realistic' way forward for software development...I'm looking forward to adopting this methodology in my practises.
Mac Felsing: (ProcessExchange)
Paul Reynolds.
Ranjiva Prasad: Superb development methodology. Getting a lot of deserved recognition in my organisation.
John A. Kunecke: (self) I have utilized the principals of the Agile Manifesto in my work for years (~15), only a few of my peers and fewer of my mangement have appreciated it. Please note the award from my supervisor (http://www.fortunecity.com/skyscraper/portal/135/SubPages/RecogBoeIDEF.htm) regarding the results of a process I developed.
fred stewart: (BAE Systems/Enterprise Systems Inc.) I strongly concur with the principle focus on persons and collaboration (i.e, individuals and interaction) vs. processes and tools, with the follwing caveats: 1) coherent processes subordinated to facilitating collective productivity are indispensable to effective collaboration; 2)tools subordinated to facilitating collaboration-friendly processes are almost indispensable to effective collaboration. I also see this principle as having a broader application than software development - e.g., agile approaches to process improvement (which of course should mean improved facilitation of collaboration!).
Karl-Heinz Werner: (Beta Systems Software AG)
Patricia Henao: (Enabling Resources)
Edward Stanford: (Microcosm, Inc.)
raghava: Productive,effectual and prompt conduct.
John Alvaro Ariza Escamilla: (YanHaas S.A.)
Siva Kumar.
Cagil Seker: (Core Computer Security Group)
John McEntire: (McEntire and Associates) Bo Carlsson: (Posten Sverige AB) Throughout my years as software developer I've found that individual motivation and responsibility among all project members are the main factors behind a successful project. With close customer collaboration we become a team focusing all energy on fighting risks instead of each other.
Paal Kristian Levang: (Common Technology, Telenor mobil) Agile Development is a must if your wants to do alteration work on an internet system.
Martijn Elzinga: (believe IT consulting) We believe that IT works... Signing The Agile Manifesto is a statement not only for ourself but also towards the industry that "we" have a responsibility towards our clients ... to do things the agile way..
Ionel Munoz: "Responding to change over following a plan". I love that part of The Manifesto. It doesn't exclude having a well-defined strategy. "Responding to change" is about tactics, and still a strategy in itself.
Patrick M. Bailey: (Grand Valley Statue University) After 20 years, getting the job done boils down to this: motivated people who are trained.
David Butt: (Project Manager) I have worked with and studied agile systems development for 4 years. My experience has taught me that this approach is clearly the best when it comes to delivering systems and business change. Through the British Computer Society, I hope to establish a UK centre of competence forum, open to all interested parties; to exchange ideas and raise the awareness/ understanding of ASD across the UK.
Tort Ren: I think the good design is also important and valued. Here, "good" design means fewer effort cost than the "bad" one while the change happen.
Alejandro Cuéllar Gaxiola: (http://www.alexcuellargaxiola.net) I'm complety agree with the manifesto. I have 24 years of software development, that is why I know when I tell all of you, that you are focusing on the right issues of software development!!!
David Harris: (EDS) Having worked as a poject manager for many years I have come to see the short comings of project effort necessarily falling into lockstep with rigid methodologies that are normally enforced by host organisations. I totally support standards, especially easily measured standards but am too often frustrated in my effort to satisfy client needs by needing to adhere to orthodoxy to the detriment of client satisfaction.
Holger Stenzhorn: (XtraMind Technologies)
Carlos Henrique.
William Nortman: (Setting Star Studio) Agile manifesto is the way to better software. It delivers what the customers really want, when they want it.
Terri Emerson: (WorkforceROI Corp)
Reza Rad: (EMC)
Arjuna Chala: (GE)
Innes Ferguson: (B2B Machines)
Franco Martinig: (Methods & Tools) As a software developper and knowledge transmitter for software development professionnals, I support all efforts to provide alternative processes for specific project needs and to consider people as the main factor of influence in software development project successes (and failures... :-])

<< Previous Index Next >>

Signatures Received: 11 Jan to 18 Feb 2003
Vera Peeters: (Tryx) You may be proposing a nice xp-ish process you've seen working before, but if it doesn't click for this team, you have to change the process -because the individuals are more important- even though your contract with the customer stated 'introduce xp for us'. This is the true meaning of responding to change... :-) Dorai Thodla: (iMorph, Inc.) Sanjay Raghavan: (Masters Student) It's exciting. A focus on people is a catalyst for new ideas. Jane Hao. Dieter Eickstaedt: (deiCon Softwareservice GmbH) As an Open Source Evangelist, I strongly support the manifest as the basis for good and professional Free Software Projects. Stefan Schuerger: (AMDOCS Germany) This is a "back to business" approach, very much agreeable. I've seen too many cases of over-regulation, where one couldn't see the woods for all the trees... With reduced procedure overhead, we can provide more value for our customers. Jane Hao: I am a Chinese software engineer and my concerntration area was CMM in my graduate study. I am quite interest in Agile and support the Agile Manifesto! Edgar Sánchez: (Objeq) We develop software in Ecuador, Southamerica. In cash-constrained environments like Latin American countries it becomes even more important to deliver as early as possible working software. Not to talk about the constant turmoil in the region, change down here more than a constant is almost a disease. Thus, I deeply feel that for countries like mine the principles of the Agile Manifesto more than a good option are question of survival. Ann Godfrey: (Suncorp) I am a relative newcomer to Agile, developing and implementing the process into a banking environment whose general community are totally indoctrinated in 'heavy' process, methodologies and documentation. It's been an interesting year, but I am convinced that this is a valuable and practicable model for them - particularly in light of the trends toward Web developing for banking/finance. Manoj Khanna: (Eversun Software Corporation) We have been practicing agile methodologies for a couple of years now. And we have been able to produce best results, were able to deliver on time and cut our costs and resources too. We believe that agile methods are the way to success, and they fulfill the stringent requirements of a large to mid-scale level software projects. Without it a manager would be handicap as they have been for many years now. Its time for a change, its time to be agile. Volker Brandt: (develop group) I really appreciate the publication of the agile manifest. It should be learned by heart and followed by all developers and project managers out there. Martin Leclerc: I have tried it. Never seen such happy customers :-) Robert McMichael: Done right, with true commitment to these ideals, the results are a beautiful thing to behold. Done in half measures, a tragedy of what might have been. George V. Woodrow III. Jaroslaw Borelowski: (NEUROSOFT)	Ali Kousari: (Algotech SA) I am supporting Agile. Tired of being inneficient and listening to the managerial bullshit (excuse the language but this is not a technical paper). Plz standby Bruce Woods: (NOLA Computer Services) We have been using Agile methods, specifically XP, since January 2000. The way software evolves in an agile development is natural. Our customers benefit from seeing, touching and using the software earlier in the development process than a typical waterfall development. Also, our customers appreciate receiving a new release of software much more than a document indicating what software they may or may not receive in the future. Jerry Smetzer: (State of Alaska - Department of Fish and Game) I'm very interested in your user-oriented approach to building apps, and am trying to apply the major features of it to our new projects. Mike Kenworthy: Please convey this to the Software Engineering Institute at Carnegie Mellon University. They are operating in the dark, very dark ages, and their client, the US Government, is suffering because of this. Antony Grinyer: Being a software developer in the industry I am at constant exposure to the many problems associated with the development lifecycle. In my opinion the agile manifesto is the most exciting and 'realistic' way forward for software development...I'm looking forward to adopting this methodology in my practises. Mac Felsing: (ProcessExchange) Paul Reynolds. Ranjiva Prasad: Superb development methodology. Getting a lot of deserved recognition in my organisation. John A. Kunecke: (self) I have utilized the principals of the Agile Manifesto in my work for years (~15), only a few of my peers and fewer of my mangement have appreciated it. Please note the award from my supervisor (http://www.fortunecity.com/skyscraper/portal/135/SubPages/RecogBoeIDEF.htm) regarding the results of a process I developed. fred stewart: (BAE Systems/Enterprise Systems Inc.) I strongly concur with the principle focus on persons and collaboration (i.e, individuals and interaction) vs. processes and tools, with the follwing caveats: 1) coherent processes subordinated to facilitating collective productivity are indispensable to effective collaboration; 2)tools subordinated to facilitating collaboration-friendly processes are almost indispensable to effective collaboration. I also see this principle as having a broader application than software development - e.g., agile approaches to process improvement (which of course should mean improved facilitation of collaboration!). Karl-Heinz Werner: (Beta Systems Software AG) Patricia Henao: (Enabling Resources) Edward Stanford: (Microcosm, Inc.) raghava: Productive,effectual and prompt conduct. John Alvaro Ariza Escamilla: (YanHaas S.A.) Siva Kumar. Cagil Seker: (Core Computer Security Group) John McEntire: (McEntire and Associates)	Bo Carlsson: (Posten Sverige AB) Throughout my years as software developer I've found that individual motivation and responsibility among all project members are the main factors behind a successful project. With close customer collaboration we become a team focusing all energy on fighting risks instead of each other. Paal Kristian Levang: (Common Technology, Telenor mobil) Agile Development is a must if your wants to do alteration work on an internet system. Martijn Elzinga: (believe IT consulting) We believe that IT works... Signing The Agile Manifesto is a statement not only for ourself but also towards the industry that "we" have a responsibility towards our clients ... to do things the agile way.. Ionel Munoz: "Responding to change over following a plan". I love that part of The Manifesto. It doesn't exclude having a well-defined strategy. "Responding to change" is about tactics, and still a strategy in itself. Patrick M. Bailey: (Grand Valley Statue University) After 20 years, getting the job done boils down to this: motivated people who are trained. David Butt: (Project Manager) I have worked with and studied agile systems development for 4 years. My experience has taught me that this approach is clearly the best when it comes to delivering systems and business change. Through the British Computer Society, I hope to establish a UK centre of competence forum, open to all interested parties; to exchange ideas and raise the awareness/ understanding of ASD across the UK. Tort Ren: I think the good design is also important and valued. Here, "good" design means fewer effort cost than the "bad" one while the change happen. Alejandro Cuéllar Gaxiola: (http://www.alexcuellargaxiola.net) I'm complety agree with the manifesto. I have 24 years of software development, that is why I know when I tell all of you, that you are focusing on the right issues of software development!!! David Harris: (EDS) Having worked as a poject manager for many years I have come to see the short comings of project effort necessarily falling into lockstep with rigid methodologies that are normally enforced by host organisations. I totally support standards, especially easily measured standards but am too often frustrated in my effort to satisfy client needs by needing to adhere to orthodoxy to the detriment of client satisfaction. Holger Stenzhorn: (XtraMind Technologies) Carlos Henrique. William Nortman: (Setting Star Studio) Agile manifesto is the way to better software. It delivers what the customers really want, when they want it. Terri Emerson: (WorkforceROI Corp) Reza Rad: (EMC) Arjuna Chala: (GE) Innes Ferguson: (B2B Machines) Franco Martinig: (Methods & Tools) As a software developper and knowledge transmitter for software development professionnals, I support all efforts to provide alternative processes for specific project needs and to consider people as the main factor of influence in software development project successes (and failures... :-])