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.
|Click here to add your name to the list of signatories.|
|Signatures Received: 19 Feb to 17 Mar 2003|
|Steve Konieczka: (SCM Labs, Inc.) We believe that the key to successful Agile software projects is the use of "effective" software configuration management. It must support constant integration, refactoring, and be 100% available in a way that's lighhtweight, low cost of use, and flexible.|
Bruce D. Kyle: (Concord Mfg) This is a breath of fresh air for developers and customers.
Hans Molenaar: (Niobion B.V.) Agility in software creation restates once again the importance of the primairy rule of software architecture and engineering: ...separation of concerns...
Michael Goode: (FEDEX)
Carl Mastyla: "Working software over comprehensive documentation" - you're damn right.
Nick Zdunic: (Strategic Systems) This is one of the most sensible things to come through in IT. To me this quantifies common sense - which no one ever does. It takes the EGO out of software development through the XP techniques and the principles have been something I've always felt but I've never felt such a unity as this, in that it reinforces my opinions on software development. It encourages me to grow and disregard the baggage of bulky methodologies and EGO centric developers and lets me get to the crux of the matter and produce good well crafted software that is easy to maintain. That's the important thing - THE CODE. I'm looking forward to growing with this movement - the positiveness I feel it is engendering has given me a new reason for being in the IT industry.
Mike Rowe, Ph.D. : (University of Wisconsin - Platteville)
Nick Jones: (LogicaCMG)
Jon Barnett: (Amity Solutions Pty Ltd) Managing software development without constraining the creativity of design.
Alexander Mamchur: To tell the truth (on SW development process), to follow that truth (in most natural manner) – that’s agile methods core!
Dan Pollitt: (IBM (UK)) I am part of a team practicing XP to deliver components to Enterprise-scale middleware products - acknowledging the different guises our customers appear in. I have also set up an XP special interest group to promote and coach the adoption of XP within the software lab - hoping to prove that lightweight methodologies can be adopted in a traditionally super-formal environment.
Michael Sherman: (Viewlocity) Executive Vice President and CTO for Viewlocity's supply chain management applications.
Darren Govoni: (metadapt)
Ryan Shriver: (Dominion Digital)
DURAND Emmanuel: (edurand.com)
|Jacob motola: (Security Services International) As an athlete agility drills were fundemental to the development and expression of athletic ability in the context of achieving success in a specific sport.
Agilie Software Development as interpreted from our manifesto, describes the fundementals necessary for the timely, fiscally responsible and successful development of applications for business and personal use.
ASD is a commonsensical approach to a complex and sensitive endeavor. It has a contextual appropriateness to the world and business environments we live and work in.
I look forward to the changes and refinements yet to come.|
Humberto Perez: (Microsoft Enterprise Services) Great idea about new direcctions of development. but is time to put business view into development process.
Dick Carlson: Agility, applied to every software engineering activity, has the potential of being what things should be in the first place – without the extra baggage.
Paolo Di Pietro: (Diviana)
Henrik Kniberg: (http://www.kniberg.com/henrik/) Over the past decade I have started several tech companies and had the opportunity to experiment with various development processes. During the past 1 - 2 years XP has been my favorite toy and so far it has worked very well, although I have not yet tried with large teams. However I think dogmatically sticking to any one methodology is counterproductive - in the end experience, common sense, and an open mind is what counts. I fully agree with the principals of the agile manifesto, and I especially like the fact that is presented as a set of principals rather than a methodology.
Ponnurangam: (Language Technology Research Centre)
Oliver Senti: (OMS Engineering) Thanks for your great job! It's very helpfull to me and my team. Kind regards from Switzerland. Oliver
Patrick Hohmeyer: A bridge on your map just wont make your car fly over the river.
Adriana Gasca [Mexico]: (NetApps Sa de CV) Que bueno que regresamos al placer de desarrollar software sin tantas distracciones y procesos innecesarios y latosos.
Matias Urroz: (Topystems)
Harold Meder: (NC Office of EMS) - I support the Agile Manifesto as a goal worth pursuing and act as a change agent towards achieving this goal within the organization while applying its precepts to my own activities.
Huet Landry: (Unisys / U.S. Customs) It's good to be able to reference established practices that are supported by the proponents of the CMM, but are less rigid than legacy practices. Our teams were approaching Agile practices, but did not know it until we found this site. Now we have some thing to fight off the bureaucrate who keep trying to shoehorn us into a waterfall methodology.
|Cornel Fota: (Semotus Systems Corp.) |
Miguel de Lucas: (Intesys)
Anko Tijman: (Van Meijel Automatisering) As being a professional tester, having worked in very BDUF organizations, I believe that being able to be agile in your development method is essential to deliver the maximum of quality to the customer.
Johanna Rothman: (Rothman Consulting Group, Inc.) Those of us who've been in the field a long time recognize these common-sense techniques are what works.
Ian Shimmings: A revelation! At last, all the feelings of frustration working within traditional methodologies and project management frameworks have just fallen into place. After years of trying to use many of these agile techniques in my own development teams and believing there had to be a better way I find there is and there are many others who think the same. I guess I must have just had my head in the sand all this time! Hearing rumours of 'other ways' and having time during long train journeys to a client I read Alistair Cockburn’s “Agile Software Development” and have since devoured every related book I can get my hands on. It has really rejuvenated my enthusiasm for this business!
Peter Vruggink: (LogicaCMG)
Steve Buzzard: (Anexinet Corp)
David Wible: Thank you for making an effort to use human beings in a human way. dw
Peter C. Ruth: (Adaptive Software Technologies) I have been a proponent and practitioner of much of what has come to be called Agile Software Development methodologies since 1972. I congratulate the founders and members of this movement for their leadership and courage in the search for "a better way" to build "the software of tomorrow".
Don Nelson: Agile approaches have always intrigued me. I'm an early adopter of ZTM (Zero Time to Market) and disposable software philosophies. I'm also a proponent of agile techniques while maintaining the robustness of an architecture-driven development process. In any successful methodology or approach to a problem, the primary requirement is initial organization - more so with agile techniques than any other. I would like to contribute by helping to identify additional team and organization attributes that need to be identified and channeled into useful, strategic actions. Hope I can help, Don Nelson firstname.lastname@example.org 303-816-9397
Ryan Geyser: (Bank Windhoek) Your methodology sounds great. It makes sense and sounds like this is the way development is conducted in any case, whatever formal methodology is being used. I can't wait to try it!
|<< Previous||Index||Next >>|