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: 10 Dec to 22 Mar 2004|
|Craig Martin: (Freelance Software Architect) It's a simple framework of workable technology to help practitioners get the job done: better, faster, cheaper - the mantra of current-day Software Development.|
Matthew Heusser: (Priority Health)
David Masover: The manifesto supports itself, too, at least in two respects: It works without having comprehensive documentation, and it is very simple.
Ananth Balasundaram: This is great stuff.
Kevin Dooley: (ASU Software Factory) The ASU Software Factory is a new entity providing professional software development support to ASU researchers. The Software Factory follows the agile manifesto as its operating philosophy, and conducts rigorous research on agile software engineering.
Patrick Steyaert: (ExMeX)
Steve Fulton: (Mattel Toys) The entire Agile Manifesto and all the Agile princiles apply to the work we perform every day. We are a highly mobile and agile workgroup dedicated to created the best possible web sites for Mattel branded toys. We did not even know there wasa nameforthe kind of work we do, until I found Larmann's Agile Abnd Iterative Development book. Now it is my bible.
Benoit Godbout: (Amadeus International Inc.) In software development, artefacts (models plans, code etc.) should always be at service of the comprehension and not at the expense of those who produce them. To often individual are slave delivering artefact to the process and not the client, equilibrium is hard to attain. Agile Software Development Manifesto is the most significant initiative I have seen in this field, yet.
Arun Bharadwaj: I work for a major IT MNC and have spent a few years in software engineering domain. Of late, I have been a bit weary of the 'heavy' processes that are rolled out as organization standards (my role requires me to do that) based on de-facto industry standard models whose ideas germinated about 25-30 years ago. The world has moved a great distance since then (although in many aspects it has been standing almost still, but that's another story altogether!) but our (software developers') methods and tools have not kept up with the changes. Mind you I am not deprecating them at all. They made a great deal of sense when they were conceived. They have served their purpose and today we need an approach which I find manifest in ideas on your site. I think the executable model (aka Agile MDA) is a great idea. This is my first time on this site. The white paper on Agile MDA on OMG site led me here. And I am glad it did that.
Matt Wickham: (ProRules) We have incorporated the Agile Manifesto into projects over the last two years in the Business Process Management software field. The principles behind the manifesto were critical to the succesful implementation of many projects in this rapidly changing field. The challenge has been in providing structure demanded by the situation and in adapting principles necessary to the application and customer environment. The founders and leaders in the principles are to be thanked for the continuing evolution of these principles.
Tom Marquis: (Geo911 Inc)
Ray Massey: Glad to find a group of people supporting a development methodology which has worked for me for years but has traditionally gone against the grain. Ray Massey, GIS Analyst/Programmer, Brisbane, Australia.
Lloyd Alan Fletcher: (Institute of Physics Publishing)
Aniket R Bhatt: I support the Agile Manifesto
Wim Codenie: (Belgium)
Rahul Chitale: (Microsoft) Agile metholodogies represent the continuing evolution and finally a credible way to 'do' software after getting over the shock that there's more to software development than simply engineering it.
Viktor H. Levi: (BoyutSis Ltd. Sti.)
Terje Bjørgum: (Bekk Consulting AS)
|Damon Carr: (Monetaire) We have developed a variant Agile method that has (we think) unique characteristics when compared to the other popular methods (which we still respect immensely). We are very strong believers in the Agile Manifesto. We wish 'Agile Software Engineering' practices were more a norm in our profession instead of the 'code and fix' environments that dominate today. The few companies like ours, that embrace the Agile Manifesto, use an Agile Method, and do proper Software Engineering (in an Agile way) are left to reap the tremendous rewards, while almost every other project fails (in terms of meeting budgets and timeframes – see the Standish Group’s studies).
I know these ideas work in practice as we were just named one of the top three software firms in Europe in our 'space' (see: http://www.monetaire.com/about/pr9222003.asp). We did this against competitors that were usually better funded, with larger development teams. We did what many said was impossible. They were seeped in a tradition of bloated waterfall processes and project failures. We did the impossible by being Agile, having great people, and enjoying our weekends.
Perhaps the days of the ‘cowboy’ programmer will never end. I can certainly see its place for a single person and an idea. However, for global, multi-million dollar systems, companies today rarely succeed and when they do it is far too often by the Herculean efforts of a few talented ‘cowboys’ who almost kill themselves in the process of 100 hour weeks (and destroyed relationships).
How is our Agile process unique? Email me and I will be happy to share what we have developed (email@example.com).
Damon Carr, CTO
David Lillie: (formerly of Rockwell Software) I am a Development Manager who has used Agile Development techniques in a M$ .Net environment for the past 2 years. Use of open source technology - namely NAnt, Draco, NUnit, and NDoc made this a practical thing to do. Results proved the advantage of Agile compared to the Waterfall model.
Adail Muniz Retamal: (Heptagon Tecnologia da Informação Ltda) Brazil is Agile!
Yousuf Ahmed: The stress on the human factor is what makes this great. I would prefer 'Teams' over 'Individuals' though.
James Parker: (BestWebTechs.Net) I had been using this method by nature for years. It came natrualy after being Internet Information Systems Admin and liaison between IS and Dev groups at the worlds largest software reseller. After deploying my fifth distributed application in two years I was told that I should start “creating a thorough documentation/design/requirements agreement with the customer before any code”. This failed repeatedly to produce by deadline and satisfied nothing. I am returning to my former method patterns of build, use, update, test, document, collect. This life cycle involves the customer at all stages, and requires them to only decide on my fee before I start. It is a patern that fits the Manifesto and has Made several industry leaders good, although maybe not so well documented, applications that are used by thousands of clients daily. The other method has produced vapor ware and a windows service that may never be used by the customer even though it meets every requirement listed and re-listed, and has all the pre-documented business entities and rules. This experiance, along with Abstract State Machines have helped me find a new vision. "Development has not started until customer uses the prototype we built together."
Prescila Amalraj: (IEEE) I stumbled on this site while reading an online book at the Computer Society web site... I am glad I did.
Tom Geyzen: (de dienstenfabriek) What we do in our company stretches beyond the development of software (and I mean this in the most positive way) but the agile manifesto still applies and is a great help to the inner working of our company Keep up the good work guys, this is definitely the way to go ! Tom
Giuliano Morais: (Smarnet Brasil) This is not only "on more path", this is the correct path.
|Peter van der Voorn: I would like to write it in blazing letters across the sky - "The customer value is in the software!". Having been personally involved in IT projects/programmes that generated volumous amounts of documentation with little software to show for it I fully endorse the values of the Agile Alliance
Peter van der Voorn
Software Requirements Analyst|
Simon Baker: (think-box) Being agile injects the fun back into software development and, in my experience, is the most effective way of delivering the right software at the right time.
Luis Camara Manoel: (Novell, Inc.) I support this manifesto for eliminating processes where processes were not needed, taking communication where doors had typically been closed, taking innovative ideas where they can flourish, taking change where it can improve upon our work.
Paul Scofield: For years I have been using the term "Agile" when describing my systems requirements. It's only now that I find others support this idea! Agility is THE pre-requisite of not just software development, but of all effective business systems.
William Craun: (Financialware, Inc.)
Brian Kiser: (Kentucky State Government) I'd like to see Agile implementated where I work. It seems that everyone here, even those who profess to dislike heavyweight methodologies, seem to push more and more for "process" and documentation over the core things that really matter, like producing good software. It's very discouraging to someone who's been out in the field producing good software for many years.
Don Fleck: (Getronics)
Rafael Vacas: (Sinergia Consulting, A Coruña, Spain) Thank you Agile Manifesto. Thank you for putting down in words the truth about software development.
Eric Kramer: (Wendy's International)
Aaron Lewis: (Axiom Shift, LLC) With our community hosting software, which has morphed over time based upon customer requirements, the people we answer to and communicate with during development are our clients. We've been following the Agile method for years, consulting with our clients from the moment development starts to the day code is pushed. The result of following the Agile principles in every aspect of our business has resulted in satisfied customers and better software.
Barry Forrest: It's about time that a better way of doing things was established. I'm not anti-documentation, but it should develop alongside the key deliverables, with input from both the technical and user communities. More customer collaboration over requirements and contracts is essential, we provide solutions to address customer needs, the customer needs to participate all through the development and delivery process. However, resistance from legal, contractual and purchasing departments will need to be overcome before we can move forward, and that will only happen with a move away from the confrontational management styles that have developed over the past decade.
Kaleem Mohammed: Agile Manifesto captures the vital issues of software development in a much better way than any other software process.Certainly uncovers better ways of developing software.
Niclas Lindberg: (Nillsoft)
Mike Stockdale: (Syterra Software Inc.)
Edward Daniel: (SalePlane Ltd.) I have never been more enthusiastic about the art of software design and engineering as now having benefitted greatly from the works of many leading thinkers represented here who share their knowledge for the benefit of others. Well done and thank you. Ed
Iain Stubbs: (Synoecy)
Cyrinus I Joseph: (Cyrox Networks Inc.) Information Security Management and Testing
Timothy Cook: (Open Paradigms,LLC) Results are what matters most.
|<< Previous||Index||Next >>|