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: 04 Oct to 10 Nov 2003
Tim Fox.
Rob Westgeest: (Agidem) Many people claim know good ways to write good software, on time, within budget. Most of them are plain wrong. I think you've made some important points and i like the way you put it.
Håkon T Sønderland: (Antares Gruppen AS) While no silver bullet, I believe that agile software development is the way forward. It would be good to be able to enjoy programming and not writing meaningless document for once!
Ola Mellgren: (ADI Limited) I'm very postive about these steps towards a manifesto you people are taking.
Charwick: (http://charwick.com) Re-culturizing IT shops mired in heavyweight processes is hard work, but it's worth it. Enforcing agile values has a snowball effect that quickly becomes infectious.
Brad Grant: (Maritz Global Technology Services)
Serif Selcuk: (Softek Software)
Jaap Zwart: (http://jzwart.nl) We do Agile with a smile....
Mahfuz Yousif: Go on keep the good work
JOSE MARIA: I'm agreed with the point of view of agile methods, it was necessary a bit of variety in the sw process development, like you can select a method that better adapt to your organization. Thanks.
Mike Kendall: (The DSW Group) Adaptation is a key for success, whether it is evolution or software. Agile embraces this core……plus I never did like “rules”.
Strijevskiy V.S..
Martin Ellemann Olesen.
Gale Stafford: Working with these principles makes all the difference in the world. I'm putting these up on my cube wall, to remember to keep all things in perspective. rock on, gale
Peter Schrier: (TriCAT Agileon)
Gurudev P Rao: (Netkraft) Extreme Programming Model when used with proper design and when implemented on modern platforms like .Net shall make life easy for both the customer and the developers..
Meir Cohen: (ITAssist)
Kevin Orrman-Rossiter: (Australian Unity)
Cohan Sujay Carlos: (Floranta - Once Upon A .Com) Working software, diagrams on wall, pencil sketches, just about anything NOW over building up potential on borrowed time for getting it right when we begin.
Mark Hanna: (West Marine, Inc.) Bravo! I've been in business application development and project management for 15 years, and I've seldom been impressed with the available project management or software development treatments that computer professionals are held accountable to. They just don't make sense in the business world. Your manifesto struck a chord in me, such that I am printing it out to share with my development staff and executive management as well. I applaud your efforts!
Bill Lattimer: (Microsoft Corporation) I support the Agile Software Development Manifesto as expressed in the foundation principles of the Microsoft Solutions Framework.
Javid Jamae: (Jamae Consulting) Good stuff..
Mark Graybill: (EXB Solutions) I've studied human nature for a couple of decades, and the implications and affects human nature has on software engineering for many years. The Agile Manifesto is right-on when it comes to what should be valued on software engineering/development projects. Software is engineered/developed entirely in the conceptual realm of the human mind without the benefits of physical science that other engineering endeavors have. Therefore, the conceptual integrity of the software product throughout development is much more critical than any other engineering endeavor. The way to ensure conceptual integrity is focusing on people and human nature - just what Agile does. Electrical engineering has "gone Agile", only they didn't know it. They can design, develop, manufacture, and test electronic components before it even leaves the desk of the engineer. Therefore, why is so much of the industry moving toward bigger and heavier phased processes - as if they are making it more like other engineering endeavors, when those endeavors mostly have already abandoned the idea? www.Mark.Graybill.com
Larry Bernstein: (Stevens Insitute of Technology) May the process fit the problem, may the development documents be read, may the software be easy to use and may the software neither crash nor hang.
Aslak Hellesoy: (ThoughtWorks)
Terrence Radl: I Support the Agile Manifesto!
Lobster: (TMaxine) We go further We are developing software AND through that, deveveloping an understanding of the solution Keep the Mind Agile and the language FLUID
Antonio Rosado: (WaveWeb)
Dipl. Inform. Dennis Conze: (conze {informatik}) Java & C++ Freelancer, Germany
Fiona Darroch: (University of Southern Queensland) Agile methodologies generally reflect my experiences of what constitutes effective system development methods.
Andy McNutt: (Level(3) Communications)
john graff: (Parlant Technology Inc.)
Mridul Gogoi.
Dennis L. Britton: (Quality Objectives) Inevitable and necessary.
Lucio Fialho: (Solucionar Informatica & Sistemas)
Pablo Daniel Cano: I fully support the Agile Manifesto. Let's enjoy programming!
Senthilnathan: (Hughes Software Systems)
Reddy Sanagala: (Sanagala & Associates, Inc.)
Alex Feingold: (Progma, Inc.)
Jaana Wayrynen: (Department of Computer and Systems Science, Royal Institute of Technology, Sweden)
Ken McClure: (Lumio) Careful, this could put Scott Adams out of business! Congratulations guys, for articulating what most of us have been thinking about for way too long. I'm starting to see a lot mnore job adverts daily which ask for experience in Agile methods, and I hope it's a sign that both managers and customers are seeing the benefit in this approach.
narasimharao vvr: (Gapvak) Want to know more
Nancy Van Schooenderwoert: (XP Embedded Co.) For years I've been collecting software development methods from various projects, teams, companies that really work. I continued to use and refine them. When I discovered XP, I was already doing most of its practices! My engineering background had made me a 'true believer' in BDUF and specs. Goodbye to all that!! There is no going back. I co-founded XP Embedded Co. so I'd never have to go back to the bad old ways, and so I can show others how to do embedded development extreme. Years of working with software developers who sat all day like monks in their cells, never communicating until too late... Being marooned on Death March projects, searching for a way out... Working for managers who view software developers as galley slaves... ...all fueled the idea that people-centered AGILE software development is the answer. I went from Art major in high school to Computer Engineering major in college, and the common thread is creativity. Agile methods will reach far beyond software development - this is the way to do complex, creative work of all kinds.
George Isabella: (TNS Media Intellegence/CMR) I have been programming for a long time and have always instinctively worked using the principles outlined in the manifesto. There have been times when I found myself burdened with management that was maniacal in their devotion to documents. Use cases became functional specs after 9 levels of review which were appended with Visio flow charts and graphs. The functional specs had to go through an incredible 14 reviews and were then converted to technical specs. The technical specs were subjected to another 9 levels of review. Then the “work” was assigned to be coded. After 6 months not one line of code or screen was done (although we did have storyboards that were pretty pictures). It was utter insanity. It is good to know that I am not alone.
Manoj Sankar: (NEST Technologies Inc) Based on my 12 years of software development and project management experince, to me Agile manifesto looks very pragmatic and promising. But in the case of a large product development with multiple geographically separated teams, how this can be applied is what I am experimenting now.
ranjit sandhu: (sra) RIGHT ON!!! not that this stuff isn't obvious to intelligent people :) and has been around in academiea for donkey's years, but i would like to DOUBLE RATIFY this manifesto (and i'm using my real name on the web!!! sacre bleu!)
Paul Garvey: In the relentless pursuit of software methodology perfection the agile processes is a means to that end.
Joseph Bergin: (Pace University)
Steve Hall: (IntraPower/Hotspot Global) I've been using agile principles for several years now with good results. There is a need to strike a balance between what goes down on paper (e.g. design, process, scope) and what remains "agile" to handle the moving target of the delivered application. Using open source is great in this model because we can swap a software component out without needing to revamp a mountain of associated overheads. Good stuff!
Umaro: 2 keep it short - IMHO agile is the future. thanks 4 this gift.

<< Previous  Index  Next >>