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.

Click here to add your name to the list of signatories.

Signatures Received: 10 Dec to 10 Jan 2003
Steve Banks: (Object Partners, Inc.) Common sense should apply to software development, too.
Hussein Badakhchani: (Xensia)
Daniel Bishop: (Haestad Methods, Inc.) If only there were a better way to create software. Oh, Wait! There is! Skeptic? Watch, I'll show you.
Tom Lang: (Encyclopaedia Britannica) We've been incorporating the values of the Manifesto (and using agile methodolgies) for over a year now. They continue to work beautifully.
Matthew T. Adams: ( I appreciate the agile methodologies' concomitant acknowledgement of reality in the software development process. It is very reassuring to hear such well respected industry figures confirm values that I have held, knowingly or not, throughout my career.
Duke Gard: (Booz Allen Hamilton)
Konstantin Ignatyev: ( Agile methods really work!
Elli Georgiadou: (Middlesex University) Interested to see how the development of Agile Methods will impact (a) on the quality of systems produced and (b) on a possible re-classification of methods. I am teaching Methodologies and Tools for the Engineering of Information Systems to approximately 300 per annum. In the last two years I included in the re-designed syllabi Agile Methods and more specifically XP.
thuyen nguyen: To do anything extreme, one needs to be thin and agile. T.N.
Juan de Dios Garcia Diaz: (Organizacion Becerra)
James McGovern.
Miroslav Pavlovic: (KEPLER Technology S.A.) 100% agree. We apply and include agile in our development process ITDA-KT.
Ricardo Llamosa: (ITI Colombia)
Matthias Bohlen: ( It was time for agile practices! Takes quite a bit of courage to let go of old habits but frees a lot of energy to build software that users will happily accept. I highly recommend agile software development to my consulting customers and I am sure they'll enjoy to watch their teams succeed!
Howard Jiang: (SandS Software Studio)
T SnowWolf Wagner: (Wabunoh, LLC)
Ben K Steele: ( XP can and does work with formalisms such as CMM. Been there. Done that. Agile wraps them up.
Warwick Sands: (Sands Consulting P/L) Nice to see that the approach that I have been actively promoting and using for over 20 years now is becoming more acceptable to both the programming and managerial community.
Roustem Karimov: (Software Trenches) I support the Agile Manifesto!
Bob Bramski: (Ordinal Logistics) Getting it Done!
Scott Stirling: The Agile Manifesto is a much needed, much appreciated, experienced response to, and acceptance of, software project and development reality. I'm all for it.
Anders Clausen: I support the Agile Manifesto. I support Common Sense.
Bob Beecher: (ProQuest Business Solutions)
Chandra: (HealthPartners) Just starting to develop a methodology for software development, using Agile as a guide. Very excited in others experiences!
Ivan Vecerina: (
David Vydra: (
Gyanesh M Khanolkar: (ThoughtCircle)
Mark Interrante: (
rajkin: (NeST) There isnt a better method to track a moving and changing target as software product. I have a feeling that much of the fundamental concepts of 'agile' can however be traced back to Federick Brooks concepts in Man-Mythical-Month. Especially the chapter on Silver Bullet and after.
David E. Smyth: (Oak Grove Consulting, Inc.) So succinct as stated, so obvious once illuminated, so effective when applied.
Hassan M. Sharif: (ExtendEnt, Inc.) This is such a great movement. At the Senior Director/CTO level for Global 500 enterprises, for years I have been practicing the principles expressed in your manifesto. It is nice to know that we finally have a movement that makes sense not only from a common-sense point of view, but also from an economic, practical application. In a world where we basically blow $18 billion in failed software projects annually, the Agile principles are significant markers along the way to not only save money, but to apply the most common sense principles of life to our working life! I do wholeheartedly support your efforts and will continually strive to apply them in all aspects of my professional life! Hassan M. Sharif Chief Architect/Information Officer ExtendEnt, Inc. San Francisco, CA
Kovács Kristóf: (KKovacs) We programmers make the technology that enable people to provide better values to their customers by caring about individual needs, collaboration, and responding to change. Engineers do it with CAD software. Salesmen do it with their on-demand calculation software. Why would we deny access to these values ourselves?
Gary "Sponge-Bob" Gauthier: An eye-opener that has reminded me why I chose IT as a career in the first place!
Leonardo Ruoso: (Oktiva) : The only way to exist as a medium sized software house
Maureen Jensen: (Infinitie Possibilities)
Pankaj Kamthan: (Concordia University)
Ranoj Saha: I strongly feels the same. Need more articles about it.
Cori Dollette Peele: (Appsability)
Klaus Lieser: I agree with R. Buckminster Fuller: "Form always follows Function".
Bogdan Craciun.
Andrea Rodriguez: (NEO)
William G. Struve: (aaiPharma) Right on!
David Markle: (Optical Innovations, Inc.) Using this methodology we delivered an eProcurement solution in 6 weeks with 3 developers. The end-clients were ecstatic, the board of directors gave us a pat on the back, and we moved on the next project knowing we had accomplished something special. Agile. The failed project that proceeded this one lasted over three years, wasted millions of dollars, and alienated clients. Traditional. Enough said.
Fabio Pettinati: (Voreas, Inc.) I have been practicing the principles of agile programming for quite a while with increased success compared to status quo practices. In our company, we implemented a similar methodology, called "Wind Rose", that encompasses the main principles of agile programming, as well as in-depth client involvement and collaborative specification and reviews. In these times of economic uncertainty, agile programming can be a signficant factor in increasing a project's ROI, not to mention its chance of suceeding.
Johnny Howland: (DoDDS Pacific) I'm behind you 100%
Steven Deller: (Smooth Sailing LLC) A long while back, I had the idea of developing software using a defect tracking tool from the very start of the project. The idea was to start with a single defect, to wit "The system does not work.". Then using defect factoring, repeatedly refine the defect descriptions until they were specific capabilities, such as "The system does not synchronize with the satelite signal.". Once a defect was sufficiently factored, a test could be written for that defect. Then the defect would be worked on (and effort tracked by defect) until there was software that passed the defect-exposing test. That process seemed "obviously elegant" to me. After all, when there is no software, there is one huge defect :-). But this in the mid-70s and it was too radical for anyone to consider it. Imagine my delight on finding Martin Fowler's discussions on XP and then tracking the Web to this site. The "agile software" ideas all resonate with me. (Whether I write a defect and then write a test, or write a test and thus have a defect because the test fails is a moot distinction.) In my 30 years of programming, I have frequently used Agile programming principles and techniques. (I don't pretend that I codified the ideas as well as the Agile Alliance, but do believe I've been on the same track.) I've got some war stories where the Agile programming techniques used only partly and without the clear descriptions at this site, nonetheless resulted in extraordinary successes. I am curious though, how design and code inspections might fit with XP and Agile techniques. Inspections (Fagen-like) have been a mainstay in my successful software endeavors from the start. The interactions in a properly run inspection rapidly meld a group of programmers into a team with common goals. Perhaps "Test Inspections" might be appropriate for XP :-). Regards, Steve
John Zoetebier: (Transparent Systems) How true the Agile Manifesto is can only be appreciated after having worked in many projects for many organisations. A saying in one of the companies was "For a good programmers the specs fit on the size of a cigarette box". I do not promote smoking, but agree with the spirit of the statement. I have seen project managers produce nothing but paperwork without any concrete result. I have seen managers driving companies insane by enforcing Service Level Agreements between departments of the same company. After many years I discovered one single factor for the succes of any project: the talent of a few people in a project. This more than anything else counted for the succes of the project and the organization. There seems to be an almost religious believe in many companies that procedures, manuals and contracts lead to good systems. Nothing could be further away from the truth. I have witnessed over and over again: the Agile Manifesto is what makes a project tick.
Jay Bitsack: (ACORE) Most everyone knows what God's first equation is. Now, we have an inkling of what His second is likely to be... Agility = Speed + Flexibility. That is, this type of collaborative thinking and associated team effort is capable of moving the world toward a new era in terms of elevating man's ability to translate information into action (aka leverage knowledge). In conjunction with the on-going evolution of Web Services, the potential here appears to be enormous. Consequently, I look forward to following and supporting the development of this revolutionary capability.
Olav Maassen: (Itis J-solutions) Software should do what it is intended for: it should make work easier. Agile is a step to keep developers honest about this goal.

<< Previous  Index  Next >>