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: 28 May to 12 Jul 2002
Andy Carmichael: (Better Software Faster) To build better software we need to *measure* its quality more, and more effectively -- especially through testing. To build software faster we need to *do* less. This implies smaller sets of artifacts and more effective automation. Agile processes are therefore essential to the universal goal of building better software faster, which is why this manifesto has my full support.
Peter Messervy: (Opus Magnum Inc.) I have been pursuing most of the Agile concepts from a time before I even heard of Agile. I heartily embrace the principles and the process. I have focused on analysis (requirements) and design practices that fit very well into the Agile philosophy. Including some modeling approaches that are very agile.
Namkyu Cho: (Independent Consultant) I believe it support the compatibility with WinWin. Sure, I love the agile method.
David Kitchen: (Büro 9) I've evolved into Agile Modeling through years of frustration through the development processes and restrictive practices that I've followed within corporations. Since applying what I held to be my own 'philosophies of development' I've seen dramatic improvement in code and the use of the code... actually seeing projects go live and get used heavily, rather than shelved for not fitting requirements. Only later did I realise that my own philosophies were but a poor image of Agile Modeling, and since then the improvements made have been substantial. I would urge all who are interested in actually producing meaningful applications and the right solution to a problem to investigate further.
Peter Windsor.
David Green: I develop software for military projects. The pile of unwanted, but contracted documentation is incredible and at very high cost. It's easy to forget that we are developing a software product. Agile principles also seem more environmentally friendly.
Wolfgang Miller: (All for One Systemhaus AG)
Paulo César Alvim Ottoni: (Powerlogic) I work in Brazil with these very important principles, including Scrum and eXtremme Programming...
Masao Ito: (Nil Software Corp.)
Bryan Zarnett: (Redhook Solutions) The Agile Alliance, the Agile Manifesto and the concept of Agile methodologies, regardless of the style provides a philosophy where we can build systems and services that transform the manner in which business is done in an effective and timely manner. Several years ago I told my boss (old one) that I did not like the way things where done - the way we communicate with the customer, the way we develope. I said I wanted to change this. He said it could not be done. I guess we are proving him wrong!
Lailah Gouvêa.
Daniel Schweizer: (Daedalos Consulting, Switzerland) “The real danger is not that computers will begin to think like men, but that men will begin to think like computers.” -Sydney J. Harris
Kay Pentecost.
Hari Mailvaganam: In all the 15+ years I have been in software development, I have not seen a more common-sense software development startegy as the Agile Software Development process. We have been using Agile with RUP on larger projects. Most of our clients and development partners have bought into the agile process - expecially clients, when they see greater continous feedback in the development chain. Development partners are particularly interested in the "change management" process. Best wishes on you next projects - e-mail me if you have any questions or would like to discuss.
David Larsson: (Tietoentator DevCon) I agree with everything you have written. I am a XP fan!
Jacques De Schryver: (self employed)
Lee Collins: (jSierra Enterprises)
Paul Holser.
Abdullah Kauchali: (iSanusi Systems Architects (South Africa)) Software development, like many "life" projects is about managing complexity. The Agile Manifesto is about braving complexity. A couple of weeks ago, I with a group of friends completed a 5-day backpacking trail through the Fish River Canyon in Namibia. As rookies to this daunting trail, we sought advice from a group that had done the same trail 5 times and who were starting the trail at the same time. They asked us what our "strategy" was. Our reply: shrugging shoulders and saying "taking it a day at a time?". Silently smiling, they assumed impending doom! The experienced group had even planned exactly where they would camp each night! We hadn't thought further than the first night. The Fish River Canyon trail is beautiful, dynamic, ruthless and unforgiving. Planning anything to the "T" is futile. Tempratures can plummet or soar depending on several factors. Carry too much, and you may suffer under your burden. Carry too little, you suffer at the hands of the elements. Any-which-way, you can easily make a beautiful hike into a sordid experience. We took it a day at a time. When it rained, we made a makeshit tent with whatever we had. It kept us dry. The contraption was dismantled the next morning. No one carried anything superfluous. We stuck in as a team and made the most of what we had. We moved lightly and swiftly, taking it a day at a time. A boulder at a time. A river crossing at a time. But we never lost sight of the awesome beauty of the Canyon nor lost track of the precious map leading us to our eventual destination at Ai Ais hot springs. We made it before the other group and in "one piece". Us the rookies. Us without our strategy - without our cut T's and dotted I's. Us the Agile Manifesto boulder hoppers!
David Taylor: (Telnet Media Ltd) Our small team of dedicated individuals lives and breathes agile software developement. The strength of our products is based in our ability to change and follow customer needs. We keep adding features but the code actually ends up smaller and faster everytime as the developers become increasingly skilled and extend their creativity. The freedom to dream up code powers the team along, and leaves regular progroids in the dust.
jean-paul assouvie: I am a french developer ever struggling to have software made in the best way for the best usage. And so happy to join AgileAlliance.
Sander M. Nagtegaal: I work in the Internet Industry, and I have found that agile methods are unavoidable when it comes to building web apps within a certain deadline. Web software is in a continual prototyping process - user feedback and design demands are much more prevalent than in their traditional counterparts. As a result of this dependence on emotion (because that is what it is), web functionality can hardly be planned for, deadlines are neglected, budgets are overestimated and results do not fit the needs of a client: this sounds like an average Internet project. To protect from this, we must embrace adaptivity over predictivity!
Edward Averill: (Wooly Loach Productions) At last, an approach that matches my experience in software development! If only we had this ten years ago...
John Mirk: (Ericsson Datacom) What a breath of fresh air! After having seen a thriving software development team (once known as "Advanced Computer Communications -- ACC") taken over by a large process-oriented corporation, it is a great pleasure to see a manifesto which is a compilation of the things I enjoy most about software development.
Rusmin Noer: This is what I am already agreed for a long time.
Aruna Dissanayake: (Virtusa Corporation)
Dr. Pierre Castori: (SynSpace SA) Looks like minds are gently starting to change... This is good news!
Jorge Teixeira: (SINFIC, SA)
Satish Babu: (InApp) I believe.
Jason Swartz: (Black Rock Software) This is a wonderful step forward for our field of software engineering, bravo to the authors. I've been promoting the use of lengthy, up-front requirements analysis for software development projects for years, even as a dot-commer, and spent too much effort holding design meetings, perfecting the specs, and persuading others to actually read them. Now I can dismount my high horse and get some work done!
Robert Olson: (Benfield Blanch) I have always believed in the concepts in this manifesto over the objections of many consultants and auditors. The proof is in the results and the happy users, not in the amount of documentation you produce.
Dave Rooney: (Mayford Technologies) I have, more or less, worked according to the principles of the Agile Manifesto for my entire professional career. It is the times that I could not follow the principles that my work (and the projects) suffered.
Jose Quinones: (Dot Com Savant) So different it's scary.
LTC Bill Robinson: (US Army) Although, we haven't called it Agile we have been using the principles of agile sw development for several years in developing a personnel system for the Army. We have delivered and continue to deliver a great system to our 4000+ users. I'm glad there is now a name for the approach we use for development. The establishment usually refers to our team as the "rogue" developers and they think our success is accidental.
Geraldo Xexéo: (Computing and System Engineering Department/UFRJ) I've been involved with software development in real life and software engineering in academics for more than 10 years and the Agile Manifesto is just what was missing.
Rekha Raghu: (Motorola) I couldnt agree more. Agile Development is the future of software development!
Tony Kehoe: (CTO - Deutsche Bank AG) At long last an approach most of us have known all along (and would have preferred to practice) as the optimum approach to delivering to our customers! It complements the demands and ever changing world of Investment Banking. The customers (Traders) prefer the transparent and dynamic interaction and of course most importantly they get what they want.
Frank Niklas Ruland: (Business Engineers) Sic! Taking the next step :-)
Larry Kuhn: I have had great success in projects that incorprated agile methods. I introduce my clients to these precepts at every opportunity
Marco Pazzanese: (Agilengineering)
Arisio Costa: (A&S Consultoria e Treinamentos - Brazil) I couldnt agree more. Agile Development principles are very good orientation for the software development personnel and processes
Stan Malyshev: (XP Consulting, Inc.)
Ashay Salunke: (SuperSolutions Corporation) The most practical software development methodology.
Shashi Rao: (TAJ Technologies, Inc.) I sincerely endorse the Agile Manifesto, simply for the following reasons: - Change in software development is inevitable. Rather than avoiding, we should plan for it. - Software Development cycles are getting smaller and need constant management of expectations. Incremental reviews of the deliverable in the form of a prototype or preview is essential. - Ongoing emphasis on quality improvement is a given.
Marcos Antonio Rodrigues da Silva: (Escola Politécnica da Universidade de São Paulo - Polytechnic School of the University of Sao Paulo ) My doctorate thesis focuses the software production.
Jay Turpin: (Intel Corporation) I have nothing meaningful to add that hasn't been more eloquently stated by others on the list. Thanks to Kent, Ron, Alistair, Jim and all the others that have illuminated a better way.
Viktor Levine.
Chris Day: (Pinky Ltd)

<< Previous  Index  Next >>