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:
That is, while there is value in the items on the right, we value the items on the left more.
|Signatures Received: 17 Apr to 01 May 2002
|David Mitchelhill: Having developed sophisticated software throughout the chaotic dotcom period, the utilization of Agile Software Development has allowed me to build highly motivated teams, deliver sophisticated systems on time and on budget, and provide a level of development security never before delivered. As CTO of vivid studios, Modem Media and Modulant, ASD has been the cornerstone of development success.
Jorge DeFlon: (NetApplications) We love developing and at least a development method recognises people as the main and most important piece.
Robert Morgan: I get blank stares when I caution about processes which mandate a strict requirements-driven delivery. Building for as-yet unimagined requirements, and relaxing some of the constraints in the conception-specification-build process, allows for faster realisation of solutions, assuming that your team is capable of understanding and delivering the flexibility of implementation to accomodate it.
Hubert Smits: (Vision Consultants ltd.) Very much interested in implementing agile principles in large scale projects and processes.
Nick Jones: Software is about delivering useful services to people. Words like "useful", "services" and "people" being the important ones.
Janet E. Danforth, CPF: (Facilitator4hire, Inc.) Whether we are talking about DSDM, Extreme Programming or Crystal Methods, the common link is collaboration, the hard "soft stuff." Excellent collaboration does not happen by accident or by wishing it so. The real value in collaboration comes by design, and is usually focused by someone with facilitation skills. Some Agile approaches formally recognize the need for preparing the environment with enhanced core competencies in facilitation and collaboration. Their results speak for themselves. The teams we are working with in Europe and the US consistently reinforce that "individuals and interactions" make or break projects.
Nabeel Mukhtar: Just want to be a part of a great team.
Lasse Junget: (Alm. Brand A/S, Denmark)
Andrew J. Toth: (http://www.andrewtoth.com) "When you do the common things in life in an uncommon way, you will command the attention of the world." - George Washington Carver (1864-1943)
Prof. Mario Gerson M. Magno Junior: (UNISUL - SC - Brazil) MCT - MCSE - MCSD - MCDBA
Matteo Centro: (altEra e-business solutions) Small companies facing big OOP projects can't afford "traditional" approaches. We find Agile Software Development very similar to what we tried to develop in the last year and we expect to integrate our methodology with Agile Software Development in the next months to be more efficient and produce even better results. Thank you.
Udo Christ: (TW Systems)
Joe Combs: (Convergys) After working in a processs laden environment, agility reminds me why I entered the field in the first place
|Faisal Mahmood: (Eneris Solutions) I am sure that the agile manisfesto has all the necessary ingredients, customer orientation, reduced software process complexity and effectice interaction, required for a successful and lighweight methodology. Yet it doesn't resist any changes which is a feature not often found in common methodologies.
Bård Magnus Dale: I love this stuff!
Kaare E. Christiansen.
Stian Lavik: I totally agree on the principles behind the Manifesto, and I think the agile way represents a change of paradigms, due to its values and perspecitves.
Eirik André Hesthamar: Agile Methodologies is a step in the right direction.
Andreas Guther: (guther.de/andreas)
Serge Vanasse: (Cordiem LLC)
Dafydd Rees: (www.dafydd.net) I'm particularly keen on test-driven development, and the importance of learning by doing.
Sudi Bindiganavile: (Thomson Scientific) I certainly agree and support the Agile Manifesto, in particular Responding to change over following a plan. Instead of changing the plan, plan for the change and we will be better off. The second important manifesto that I support and have used is individuals and interactions over processes and tools. One thing I have noticed with my team by using these manifesto, they are charged up and motivated amidst all the bumpy rides.
Kirill Kalishev: (http://www.kirillkalishev.com) I am a programmer who does XP, writes things on XP in Russian and holds (hopefully) interesting seminars on agile development.
grazia dassano: (sanpaoloimi)
Sheba Anne George: (Acusis Software)
Roger Browne: (Everything Eiffel)
Simon Chatfield: (The Chatfield Group, Inc.) In working on hundreds of projects for many different clients, I have found that the architect's ability to be adaptive to change during the development process is key to success. As developers we need to embrace the ever changing requirements of our clients and build solutions that allow for those changes.
George Pauly: (Ring Associates, LLC) Interaction is a process. Software is documentation. Collaboration is a covenantal relationship. This too shall pass.
Will Rau: (Concur Technologies) I especially like Alistair Cockburn's focus on the human factors that make Agile Development work.
A. Banyini: I FOUND THE AGILE CONCEPT GREAT. IT WAS APPLIED BY A CONTRACTOR IN A PUBLIC ORGANISATION WHERE MOST PEOPLE DID NOT HAVE IT NOR PROJECT CONCEPT. AS A MANAGER OF THIS PUBLIC ORGANISATION, I NOW BELIEVE THE CONTRACTOR FOLLOWED THE MANIFESTO TO BOOK
|Alex Iskold: (Information Laboratory, Inc) I am attracted to agile methods because they embody insights of complex natural systems. Systems are not engineered, they evolve. Programming is the dialog between engineer and the software. It is an art form, where through the process of continious refinement a beautiful and correct software emerges.
dan flies: (http://www.mrs.umn.edu/~fliesd)
Lillian Zelinski: (SAIC)
Don Richardson: (Richardson Technologies)
Thomas Wrensch: (University of the Pacific) I have used some of these techniques in Smalltalk projects, and found them to be very effective. Now, as a teacher, I need to find a way to expose my students to Agile programming. I believe this alliance will be a boon to enlighted teachers.
Dave Hoover: (Red Squirrel Design) I am just beginning my journey with Agile Software Development but I have already been profoundly impacted by what I have learned. I am currently adopting XP practices into my development work and beginning to research how certain post-modern theories of family therapy might be integrated into agile methodologies.
J. B. Rainsberger: (Diaspar Software Services) I support the Agile Alliance and its manifesto primarily because people are so highly-valued. In my opinion, it is critical never to lose sight of the human elements in software development. The manifesto clearly expresses that all participants in a software project are valued above all else. I commit to advancing this cause in my own work, along side (at least in spirit) the pioneers of the Agile Alliance.
Balachandran Natarajan: (Washington University) All the things that I think I missed when I used to work as a consultant. As a Research Associate, I get to do most of the Agile development's manifesto and there seems to be better results.
Sumeet Parmar: (Developers At Large Inc) The gravest mistake is to take a certain paradigm or philosophy and try to force it onto something that needs better understanding. That's what is wrong with the present software development situation. The majority simply took the pages out of traditional engineering practices as a guidebook to software development while completely neglecting to acknowledge the true nature of software. Agile Manifesto will hopefully mend some of those mistakes and pave the way for a more profitable industry.
Wouter van Oortmerssen: (http://wouter.fov120.com)
Steffen Gemkow: (ObjectFab GmbH)
Tony Azar: (BIG ) We have actually applied agile software development in some of the projects where cost was not an issue. However we have always went with the design/engineering approach where cost was tight. I believe that clients should understand this concept and help developers not worry about time frames and man/day costs and all the contractual crap that comes along.
David Beshore: (Enerspace Tech)