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: 20 Mar to 25 Apr 2003|
|Merv Hammer: (Software Sculptures) I am a developer working for a small Norwegian IT company. I am, however, in the process of founding a software company that seeks to achieve a number of things that I have found echoed in your principles of Agile Software Development.
I envisage that my small company will attempt to encapsulate the communitarian ethos of the the free and open source software communities, specialising in re-cycled code, teamwork and the development of a "development bio-rhythm"
which will be viewed as a kind of emergent property shared between the client and Software Sculptures where both contribute openly, freely and interpret the final sculptures continuously as it takes form. For this reason, I would like to try to stir up a trend of pricing software for the hours and creativity involved in its creation rather than for the code underneath. And of course, our code shall be open and available.
Thank you all for the encouragement you have afforded me. And with your permissions, i shall certainly intend to make use of the Agile Software Principles in the creation of a genuinely creative and transparent environment at Software Sculptures.|
V. Chandrasekhar: Amen!
John D. Peterson: (Barontown Software Services) I highly recommend Object Mentor's Extreme Programming Immersion Training - regardless of your methodological tendencies.
Frank S. Sampson: (Kipe and Associates, Inc.) People, not paper, makes the difference.
Shirley Shen: I hope to contribute as much as I can to the spread and prosperousness of the agile process together with others.
Luis Vasquez Kocchiu: To the future and beyond
J. Dave Sheremata: (IONA Technologies, PLC) Having been an XP zealot for a couple of years now, the Agile Manifesto is even more beautiful in that it is stated more simply than other contemporary development practices. Because it is concise and more refined, it is easier for the disciples of more rigid practices to begin to question and understand than the more elaborate web of XP or RUP. Cheers to evolution!
Donald Kretz: Over the years, I have wasted too much time producing reams of documentation that no one ever read, and building software that no one ever used. Customer interaction and prototyping has been the key to our recent success. This is the way to go!
Diogo Duarte: I liked this one "Simplicity--the art of maximizing the amount of work not done"
Bruno Navert: (Logient)
Brad Winslow: (Iris Graphics, Inc.)
Jonathan Logan: (Merant Corporation) Quality development and delivery requires an organizational and individual commitment to deep listening to the customers and to each other, to on going process improvement, an unending willingness and flexibility to learn & grow, and the full access to and use of only the best tools, resurces and practices. All the best of success! Jonathan
Heine: (The hospital of Holstebro i Denmark)
Paul Morris: It's about time we have an approach to software development that focuses on practical aspects rather than theories and academic wisdom.
Graham Menhennitt: (Menhennitt Consultants Pty. Ltd.)
roberto marinelli: (MTD Tecnologia) Do not automate bad operational processes
Uwe Kubosch: Hear, hear! Pragmatic programming is the only way programming can lead to prosperity and happiness. donV
|John Tangney: (JD Tangney & Assoc.) As a specialist in web-based applications, I cannot conceive of any viable alternative to an Agile process. For decades, we Software practioners have struggled with various Processes and Methodologies which purport to decrease defect rates and improve time to market. In almost all instances, those Processes and Methodologies impose artifical and unnatural constraints on all participants, stiffling whatever creative spirit we might bring to the defect and schedule problems. Simply put, Agile processes don't. Instead, they encourage what we do well and put in place safety nets to save us from those areas in which we [humans] don't do as well.|
Jared Smith: (White Hat) Thank God for this agile manifesto! A ray of light streaming out over the software industry. As a person who strives continually in an environment where people think these ideas are unworkable, I'm grateful to find a simple and clear place on the web to point people, adding context to my earnest appeal for user-centered software. Please note that software according to the agile principles is software in alignment with the great commandment to love our neighbor; other methods cause us to contend instead of search for the virtues of practical humility.
Javier Smaldone: (http://www.smaldone.com.ar)
John Wolter: (Wolter Works) The Agile Manifesto's values offer to any development an opportunistic dynamic interaction that extends not just to technical work but to the business side of any product. Agile gives freedom from perscriptive plans and processes that strangle taking dynamic advantage of emerging technical opportunities and changes. Agile Development is not anarchy, it, for each project, defines a flexible fair playing field through declaritive constraints where the best results can emerge. It is creativity with focus, process when needed, goals with exploration, collaboration with individual accomplishment, and constant evolutionary optimumization of results to meet project needs.
Patrick Parato: (Compression Software) I have been meaning to add my name to this list for a long time. Agile methodologies make developing kick-ass software fun again. Giving the customer the control they deserve, letting the programmer just do thier job, and building a strong team of people who work well together, just makes sense. How come other methodologies don't realize this!
Raymond Salzwedel: Liberating!
Bill Holloway: I'm proud to sign on to the manifesto. I view it as a monumental milepost in the history of software engineering.
Cliff Gregory, PhD: (AgilityWare) We as a company believe that the only means to make software effectively and on-time/on budget is using the agile processes.
Pat Beckham: (AgilityWare) This is proven process!
Steven Wright: (AgilityWare) We belive in Agile Process
Colin MacDonald: (WestOne Services) We have adopted the agile approach and have reaped the rewards of working closer with our customers. Our only issue is converting those devotes of the waterfall methodology to the benefits of agility.
Jean Morgan: (Wilhen Associates Limited) The Agile Manifesto - the direction towards which we should all be moving
Paula Thornton: (http://www.iknovate.com) Let's do it!
Ronny Tocaj: (RytKonsult)
Stefan Roock: (IT Workplace Solutions) Agile software development means customer orientation for software development.
Tom Godbold: Great work.
|Charles W. Stump II: After many years of software development in both product and project environments, I am convinced that Agile is the key to success. I am also convinced that Agile development and monolithic processes such as CMMI can coexist if people recognize the benifits of both. |
David Kavanagh: I'm glad others share the same values for software development. I almost thought documenting it went against "agile", but you did keep it brief and to the point! :-)
Jiri Cincura: (independent developer) Yes.
Rick Sline: (Custom Programming Solutions) Agile Development provides a much needed common sense approach.
Anthon Pang: (http://www.softwaredevelopment.ca) It is fear of the items on the left under adverse conditions that the items on the right have dominated traditional methods of developing software. Complementing these values are those from XP: communication, simplicity, feedback, and courage.
Louis Garrett: (DatabaseHelp.net) Thanks for formalizing a way out of Dilbert's world for teams who can successfully produce software without first writing a novel or demanding one from the customer. I was previously frustrated by serial processes and the uncertainty that the industry could invent lightweight alternatives. I can now be frustrated by the knowledge that strong alternatives exist, but they're not understood or embraced by my clients or coworkers. After suffering under the label "cowboy coder" for so long, it's nice to find respected voices who confirm that it's possible to build great software by quickly building good software that evolves toward greatness. I'll contribute these tired refrains to the group from my limited bag of tricks: "They won't know what they want until we show them something they don't want." "We can't expect them to drive up and order software like they would a burger and fries. It's easy to imagine a burger with either ketchup or mustard. It's hard to imagine robust software systems. Let's stop expecting wildly creative visions in the early stage when they're not likely or necessary."
F. Andy Seidl: (MyST Technology Partners) I became an ardent "agilist" (is there such a word?) about two years ago when I read Robert K. Weiler's opinion piece in Information Week (http://www.informationweek.com/830/30uwrw.htm).
Arun Kumar: (ADP) This addresses to a certain extent the important issue of alignment between IT and Business. As an IT community, we haven't earned the trust from Business that we could not only deliver but could also drive the business. Agile methodology is the way to go and this has the potential to solve the productivity paradox.
Juan Felipe Machado Guzman: (TES America) After a lot of tries with processes, I finally found a metodology for small groups, that guaranties quality and don't compromise delivery times. Thanks!!!
Eelco Hillenius: This is how it should be! In my experience though, it's still the commercial people selling projects to commercial people using commercial arguments (crap mostely) instead of realistic arguments. Dilbert's world is still in effect as long as the buying process does not change.
Joe Short: (AT&T Government Solutions) Agile engineering methodologies are a natural evolution from the current traditional framework approach. My hope is that we realize a concurrent transformation in the Configuration Management and Quality Assurance disciplines as well, resulting in transparent and complete product assurance that is woven into the product's lifecycle.
athinarayanan: I whole heartedly support the manifesto.
|<< Previous||Index||Next >>|