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: 09 Mar to 20 Mar 2002
Muralidhar Gopalakrishna.
Vidar Gunstvedt: I have during the last 3-4 years discovered and promoted the principles behind the Agile Alliance as the ONLY workable way of developing and promoting software. I fully support you!
Björn Ek: (DSDM-Consortium Sweden) The Agile Manifesto is the perfect way to stress the basic issues that are the very foundation of methods like DSDM. THIS is the future of software-development.
Lance Walton: (http:// easyweb.easynet.co.uk/ ~lilliput/lance)
Piergiuliano Bossi: (Quinary) The value of agile principles goes well beyond the scope of being more effective, more productive or more efficient.
Srinivas Thouta.
Tim Breitkreutz: (Software Brewmasters)
ugo landini: All that heavy stuff is just cumbersome... do they think programmers are only pawns or what?
Daniel Stephan: (mobidata GmbH) Every developer should put this manifesto over his/her desk as a reminder.
Anuraag Awasthi: A happy employee means a happy customer. A happy employee exhudes team spirit and collaboration within the team, with the customer and the end users. Moreover, software is made for people and by people. This people focus has been missing in traditional approaches. An Agile approach understands this basic truth.
Salvatore Lentini: (Mandarin Software) I am an independent consultant in NYC, concentrating most of my software development in various trading systems in C++ and JAVA. I have read and enjoyed the documents concerning the Agile Manifesto. I agree with the manifesto but often find it difficult to work through the steps mentioned because of obvious reasons...people are inpredicable, business units don't want to spend money, many IT managers are from the old school of thought( mainframes, cobol, etc ). I guess you see where I am getteing at. But I hope to read more interesting articles on the Manifesto in the near future.
Bill Campbell.
Paul Allton.
Bill Barnett.
Mitch Amiano: It is said that life innovates by making many cheap mistakes, allowing the cost of individual failures to approach zero. The values reflected by the Agile Manifesto will have a similar effect. Prioritizing people, relationships, outcomes, and effectiveness can hardly be called "common sense" in an industry populated by introverted theorists and as yet dominated by cold war management styles. The Agile Manifesto deserves our recognition and support.
Jean-Hugues ROBERT.
Matt Scilipoti: (Possiamo Consulting LLC) Thank you for lighting the fire. Not only does it light the way a little, but the sparks get me up off my bum. The ideas you are sharing have brought a new level of energy to software development.
Georg Sehl: During several years in Software Quality Assurance I always have felt that there must be more about testing software than putting test cases and bugs on file, writing huge documents and tuning sophisticated processes. The agile approach points the way ahead.
ZJ Chen: (SRS2, Inc)
Joshua Reynolds: Me too.
Carrie Biles: (Aegis Software Inc.) Aegis Software Inc. supports and employs the Agile Software development methodology.
Justin Sampson.
Andrew Rosenfeld: The grassroots effort behind agile methods is quite impressive, and in time hopefully academia and management will see the agile perspective as a valid, respectable alternative. The existing agile processes have yet to evolve and mature... it should prove to be an interesting journey.
Jos Warmer: (Klasse Objecten) As co-author of the UML standard people usually think I love large and detailed models. The contrary is true, a model is only worth building if it directly helps to achieve the final goal: building a working system. With the emergence of MDA tools, it becomes possible to directly move from model to code. This "promotes" models from being merely documentation to becoming part of the delivered software, just like the source code.
Bo Leuf: (Leuf Consultancy) Author of The Wiki Way (Addison-Wesley 2001, with Ward Cunningham) and Peer to Peer (Addison-Wesley 2002), my focus has generally been on the communicative and collaborational aspects. Web site management and software development has long been aligned with the manifesto princples.
Tim Woodard: (Diamond Visionics Company) What's the alternative?
Jeff Grigg: “People are more important than process.”
Paul Clanton: (http://home.earthlink.net/~pclanton ) As an IT business management consultant, IT manager, software development manager and project manager, I have found the beliefs and principle of the Agile Alliance to be applicable for any IT related project. I am proud to support the manifesto and the principles behind them.
Rich McCabe: (Software Productivity Consortium) Here at the Consortium we've been supporting CMM/CMMI-related work and services for many years. Yet, even though our members perform the very large military/government projects that cannot do without the "heavy weight" methodologies, it has become obvious that many other member projects have a crying need for an agile approach, and we have been recommending it, as appropriate. Cockburn makes the case very well that there is a place for both light- and heavy-weight methodologies in this world, although agility is an important quality to consider on any project (and overall has not been receiving sufficient emphasis -- hopefully proponents of agile thinking can improve the situation).
Steven Vetzal: (Three Wise Men) Agile programming offers the best methodologies for web projects, where relevance is often measured in days and weeks, rather than years. Traditional top-heavy design can miss the mark, or create over-complicated systems that require too much time to build or require too much hardware to deploy.
Thomas Eichberger: (Thomas Eichberger GmbH)
Aaron Sansone: As a software developer and consultant, I have found that Agile development is the Mecca I have been searching for.
Peter Hansen: (Kaval Wireless Technologies Inc) Director of Software Engineering. I believe agile approaches (in our case XP) are revolutionizing software development. More important to me is that my team is making much more progress, producing higher quality code, and having more fun (less stress) than ever before with non-agile approaches.
Trond Wingard.
Charley Rego: (ZixIt)
Bryan Dollery: (Chaos Engineers) Way Cool
Marc Evers.
Fernando Femenim Santos: (Sinfic - Sistemas de Informação Industrial e Consultoria, SA)
Keith Landrus.
Ndehi Karonjo: (Solutions 2000) We have been practising alot of extreme programming but we did not know it was a methodology that had a name. We kinda stumbled into parts of it. The following has been particularly useful. - Bringing a senior Clients representative into the team. Working side by side with a client's rep allows fast decisions to be made, produces the best design and better acceptance by the other users. Its also a great way to make long lasting friends. - Paired Programming always produces better and more practical code. Conding standards are easier to keep when people are working together. - Courageous refactoring. If the code is bad then it should immediately be rewritten. I'd like to learn more on agile methodogies
Sri K Ganjam: (SemanticSpace Technologies Ltd) I always used to complain about changing requirements, with Agile methods(XP in my case)I found it easy to adapt myself to the changes and be more productive.
Simeon H.K. Fitch: (Mustard Seed Software)
Joe Rafter: (IBM Global Services) Clients consistently request functionality and features to be built via applications and systems using multiple technologies. The Agile Manifesto articulates our preferred behaviors to respond to our client's requests. Our solutions, as well as our behaviors, should reflect the spirit of the Agile Manifesto. The manifesto will be exhaulted when we as an industry deliver agile solutions and architectures with agile behaviors to fulfill our client's requests. I am reminded of the saying "the only thing that is constant is change". We should embrace this change with the Agile Manifesto.
David Draxten: Simply Wonderful!
John Brewer: (Jera Design) I've been using agile methods since early 1998, and XP for the past couple of years. These days I consult in the San Francisco Bay Area, helping companies adopt XP and other agile methods. I maintain the Extreme Programming FAQ, which can be found at: http:// www.jera.com/ techinfo/ xpfaq.html I helped found BayXP, the San Francisco Bay Area XP Users Group. (All users of agile methods are welcome, as are the agile-curious.) http:// www.jera.com/ bayxp/
John McManus: (SchlumbergerSema) I am interested in all aspects of agile design. As an international author in systems management I am also interested in furthering knowledge in systems engineering.
Tudor Girba: (home page) How would it be to be passionate about your work? How would it be to go to work and just play? Nice, I think. But how could you convince a manager to let you? Anyway, I think that this site is one of the steps in that direction.
Peter Hruschka: (Atlantic Systems Guild) The manifesto put in words what successful projects have experienced but could not explain. Following agile maximes succeeds over formalizing the process.
Kareem Qureshi: Yes I think that is one most efficient way of coding.
Oscar Espinoza: (EG&G Technical Services, Inc.) Providing excellent services to our customers and client base, while accelerating the quality of flexible code has never been better defined as in the agile programming techniques. IT is and will continue to be challenged by the global, economic and political requirements facing suppliers, venders and customers. Successful shops employ the "3F" practices (functional, fast, flexible) found within the agile programming techniques. IT implementations are successful when business strategies are achieved (customer satisfaction and increase of profit margins).

<< Previous  Index  Next >>