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: 04 Oct to 15 Oct 2005|
Michael Savedge: (Whirled Web)
Lian Liming: (Xiamen University, China) Agile is an efficient way to develop nowadays' huge and complex software to satisfy the keeping-changed customers' requirement.
Jim Dawkins: (http://www.jimdawkins.com) Believe it, Use it, Benefit from it.
Sean Patrick: (Monkey Head Software) AGILE Works! I was burned out on the processes many Government agencies enforced... Crash and Burn development methodologies...
Ashok Pai: Amazing Method
Solomon Thompson Jr: (Blue Collar Objects) Our company is built based upon Agile principles.
Richard Langlois P. Eng.: (Nokia) I see Agile as the result of the natural selection applied to the Software Development process. I strongly support the Agile Manifesto!
Daniel Morrison: ([i] Collective Idea) The Manifesto is radical because it works. It takes diving in and trying it to understand that there are better ways to develop software.
zulker: (BrainCabin) i am a happy agile
Pavel Szalbot: (http://www.lingeek.com)
John Orr: (http://radio.weblogs.com/0101170/)
Ritesh Rathore: (TATA) I support.
Christoph SIKULA: (Siemens Transportation Systems) The approach evolves at the right timing -- since getting rid of complicated development-processes and their vague value are discussed in these harsh economic times. Apart from this, i favour the matching of customer needs AND employees/creators day-2-day needs! The Vision is - more fun at developing better systems with less effort. Thank you!
Ignace Saenen: (10Colonies) Please keep pushing the ideas of XP and Agile programming, so that one day the debug hell of today transforms into a productive environment tomorrow! Great work guys!
Nayan Hajratwala: (Chikli Consulting LLC)
Riaan Snyders: (Private) In the world of software development it seems as if quality has taken a back seat to generating money. I think agile will put things back into perspective and put the focus back on quality and not quantity.
Imran Patel: (Valtech UK Ltd) Have a look at www.valtech.com
Alan Gater: (Deanwood Solutions)
Lance Rushing: (Lance Rushing)
Walter Neal: (Neal Project Management)
|Morten Jagd Christensen: (jCAPS) Experiencing that process driven software quality assurance is now done by grey haired men who 'used to be a programmer' (15 years ago) i find the Agile Manifesto refreshening and very much in line with my own thinking. I would like to advocate for automatic unit testing, preferably coverage based, as this is one very usefull and Agile way to guarantee the 'working code' codex.|
Keith Klundt: (EnvironMax, Inc.) I've seen agile principles in practice result in greater quantity and higher quality of working software, and in an increased level of trust and confidence between the customer and the development team.
Rufino Rabin: I've worked on med-large scale project for almost 6 years and had encountered a lot of software development practices both its flaws and advantages. Id like to get involved to learn and both share my experience on this manifesto. --- Raffy
Anssi Piirainen: (http://api.blogs.com/)
Matthew Fowle: (Voodoo Warez Technologies)
Narendra Naidu: I totally support the Agile Manifesto. I believe in all its tenets from the heart.
Luis Fraile: (Renacimiento Sistemas) Just try it and benefit from it as much as you can
Isra Maya: Working with humans and for humans is something that has been fogotten by some software developers, however you have promoted an important interaction among them.
Craig Jones: (Wells Fargo) I've always been a proponent of the Agile Manifesto principles even before they were listed here - simply because they make sense and strike the balance between the various project development considerations. I also think the AM works because it is centered on spiritual principles, which is something unfortunately you can't teach. An engineer who is just out to make a buck, or is too absorbed in creating their own archaic world of wizardry (rather than doing what's best for their customers and peers) won't "get" the manifesto or even bother to search for it. At the least it brings together those of us who lead with our hearts AND our heads.
Alexander Estupinan: (10:02 Software Engineering) Very helpful bunch of best practices..
Bradley Landis: (Idea Integration)
Momodou Sanyang: Based on my field experience, I concur with these values.
yuval Kossovsky: (YKnowledge Consulting Network, LLC)
Jaap Schreurs: (DVNdesign)
|Arthur Billingsley: Over the past 28 years of involvement in the computing and information technology business, much of my personal and professional success can be attributed to the adherence to the principles of the agile manifesto. While I was not aware of this articulation until this year, I support and validate these principles as integral perspectives to innovative and collaborative work. My professional work, has to date, been primarily in national defense information technology and adjunct teaching in academia. While I was aware of extreme programming initiatives, I had no awareness of the agile manifesto. In 1994, using DoD acquisition reform initiatives, I formed and led an Integrated Product Team, to collaborate as a team with the prime contractor, in reviewing and understanding the Mil-STD, Mil-SPEC project performance specifications. Since the initial performance requirements had changed since project initiation, the integrated project team (IPT) proposed and implemented changes to the performance specification. The project was then baselined and the integrated project team worked to deliver a commercially baselined unit within 18 months of rebaselining. The commercially baselined unit demonstrated superior operational performance against many requirements and met all requirements. We leveraged an open systems architecture (OSA) with commercially available components and reused software (ADA and C) from the previous development efforts. The principle, used at that time, to enable sweeping project changes to all elements of the project was “build a little, test a little.” The collaborative development of the rebaselined performance specification allowed the prime contractorto deliver units that met or exceeded project requirements while reducing overall acquisition costs. The principles of the agile manifesto are repeatable, manageable, understandable and effective. From my experience, these principle should be considered “best practices” for innovative and collaborative environments.|
Taco Tijsma: (Centric) I welcome the idea that our industry is less and less compared to the building industry and that our industry is done by professionals only. Respecting them and their skils is crucial.
Leon Katsnelson: (IBM)
Vikas Sood: (BirlaSoft)
John Broomfield: (Quality Management International, Inc.) Interacting individuals (including customers) who are working to a plan but responding to change to produce working software are engaged in a process!
Simon E Davis.
Paul Long: It just makes sense.
|<< Previous||Index||Next >>|