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: 15 Sep to 14 Oct 2004
Kyle Willkomm: (Accenture) Heavy process is usually driven by fear. Fear brings out the worst in people. Thank you for attempting to combat it in my industry. I hope some day they'll join us, And the office will live as one.
James Lawrence: (AnnoTech Software Consultants) We have been developing to an agile methodology long before it was put to paper. This has been part and parcel of Annotech's RAD application Development process. We have been educating our developers in the Agile methodology and are hoping to fully adopt and play a part in this Manefesto
Vraiment Tredway: Amen
Mustafa KUBILAY: I'm a PG student in METU Turkey and I'll do a master thesis with agile development
k suresh babu: I liked this simple and short description of the development process.
Jon Stahl: (Independent)
Shen, Shenghao: It is wonderful!
Santosh Kumar Sahoo: (Wipro Infotech) I am fully in agreement with the Agile values. But the risk here is to be able to build the customer confidence. After winning the confidence of the customer, rest becomes easier. Communication in addition to credibility will play a major role in winning customer's trust
Aniruddha Shahasane: (USF) Agile processes is the need for the present and certainly future.
Paul Marrington: (Askowl Pty Limited) The manifesto is a clear description of principles I have been working towards all my professional life.
Paul Warren: (The Sheffield College) Agile is the way forward, having used the methods for some years now and seeing what others have done, makes my decision of being a Agilest the right one.
Alexander Papanastassiou: (Alter Eco) This is all a matter of working for results in the real world rather than for compliance with rigid and artificial methodologies in Bureaucratistan. The excesses of the industrial age must be put behind us. It is time to accept the near-chaotic nature of our world. People are not machines and the software we build is ultimately designed to serve people...
Greg Balajewicz: (GMB Consulting Inc.)
Will Spurgeon: (Tech-It-Easy, Inc.)
Rodolfo de Paula: (http://rodolfodpk.tripod.com/index_en.html) I came from the ground : from DbaseII/CPM/Apple to Java/OO/Agile... After some hard projects trying to be ISO/CMM/RUP/etc well polished, I had discovered Agile Manifesto effort and now I have my faith in software development field back. Hey, ho, lets go !
Deepak.D.
Adventos LLC.
vijaygopal: (Translucent Softwares) WE are a startup company trying to analyze and adopt some standard process for our software development service as well as software product development.
Kolawole Ogunlana: (Compute-rite Systems Limited)
Regis Costa Maciel.
Vimal Gupta: (Oracle)
Antony Marcano: (testingReflections) Agility is first a state of mind, then a liberating a way of life...
Henrik Thomsen: (CONEXP) Long track record of building mission critical systems. Project manager on larger projects. Bachelor of Computer Science (De Montfort University) Datamatician. Laboratory technician. Experience within the following industries: - Defence - Pharmaceuticals - Laboratories - Health care
Niels Bech Nielsen: (logical)
Mike Kenny: (inzanix) I believe that Agile Software Development has been around for a long time, though not in any formalized state. In my experience many projects were delivered along the lines of eXtreme Programming methodologies with the significant difference that the actual projects were terminated on time but followed by many patches, enhancements, revisions, etc. In effect they followed the principal of 'deliver often and deliver late' rather than 'deliver often and deliver early' which adhering to Agile Software Development would have allowed.
Philippe Ombredanne: (nexB) I guess I should have signed years ago. Agility rocks. Been a fan of it since late 1999. Simple beats complex.
Glynn Jones.
Paul gaetani: (Kronos)
Curtis McMillin: (Tomahawk Consulting, Inc.)
Devendra Joshi: (Summit Information Technologies Ltd.) Changing customer requirements or even understanding them has always been a problem with software architects. Making customer an integrated part of development process makes agile development process worth following.
Markus Rohlof: That is, what we have done successfully for many years!
Raghava: (http://raghava.blogspot.com) 3 things 1. Version Control Software 2. Issue tracking Software 3. Build Generation and Scheduling Software Everything else is a "bloat". Hail Agile!!
NOEL C BRANZUELA: I am very interested and would like to really lear at the same time would like to share whatever I learn. Thanks
Alejandro Di Battista: (Lexmatica)
Christian Zagrodnick: (gocept)
Chris L. Cole: (Emination, Inc.)
Eduardo Pereira Habkost: (Conectiva S.A.)
Dr. James P. Davis: (University of South Carolina) I teach undergraduate and graduate course in hardware and software engineering, as well as carry out research, in the areas covered by the Mainfesto. The Manifesto represents an "organic" and "holistic" approach to the issues pertaining to project organization, application of project-related and artifact-centric methods, and the execution and subsequent tracking of effectiveness of the project team in meeting both artifact-related requirements and project-related objectives.
Paul Hathaway: (ANSTO Bragg Institute) There are those of us who are engineers and scientists first, and keen software developers second. To keep focus on the project goals, with the customer and team in an agile environment, is vital to our success and satisfaction that the work has been done well. This Manifesto is a guiding light.
Michael Schader: (Yellow House Associates, LLC) Recently I've seen a number of backlash articles that attempt to impugn XP and other lightweight methodologies by focusing on pitfalls in particular situations. They're missing the point. The Agile basics are fundamentally impossible to argue with -- who's opposed to working software or customer collaboration?
Silvia Lozano: (Avansoft S.A.) We need to learn about adaptative software process to improvement our productivity
Branimir Dolicki: (http://branimir.com)
Nigel Thorne: (http://www.nigelthorne.com)
Arun: (SRC Software) What i like most about this is that it demands nothing that does not come natural to a programmer who love his or her work . It is on the whole a very natural and intuitive process .
Azhar: (4 Brothers) I Strongly support Agile Development methodology due to its fast, and quality steps in Software developement.
Navin Samuel: (Zensar Technologies Inc) I subscibe 100% to the philosophy of Agile development. But I also realize that "Processes & Tools", "Comprehensive Documentation", "Contract Negotiation" & "Following a Plan" are absolutely necessary for success in the longer run. The only way to bring about a collaboration among these factors is by automating as much as possible the non value adding activities involved in these processes. We at Zensar are working towards the same. Our Solution BluePrint framework is a step in this direction.
Claudio Quagliaro.
Ilias Bartolini.
Hafeez Abdul: (ip3 Systems Ltd) I am a new to Agile and trying to implement 12 core practices of XP methodology at my work place.
Wes Johnson, PMP: (Roadrunner Project Management Consultants) I've been practicing this for years and now I know its name

<< Previous  Index  Next >>