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.

 

Signatures Received: 27 Mar to 10 Apr 2010
Sujeet: (Infosys technologies ltd) Indeed, i think that Agile testing will replace the mode of testing in the conventional ways in near future. Dynamic industry needs dynamic tools to encounter the changing demands, there agile testing fits in well.
Anand Joshi: I have been working on Agile projects using Extreme Programming model for past 2 years. I would like to be updated on latest happenings on Agile methodology.
Malyadri Vallapuneni: Actively practicing scrum since 2007, in various projects and releases.
Mark Thompson-Kolar: (University of Michigan School of Information)
Caroline Hynes.
Jerry Chadwick: I have worked in agile shops for the better part of a decade. Recently, I became involved in a project for a very large, Fortune 100 company that has a long history of serial/waterfall process. They very much prefer "processes and tools" over "individuals and interactions." We just went through a three month, intense planning session that culminated in a week-long intense (15 hour days) high-level design and project-planning session. These massive documents they will present to the board of directors for the company for approval and funding. We are trying to introduce the agile process to this company, but it is very difficult. They are very steeped in waterfall and process. It's very frustrating, but it's a great reminder of why I'm in love with agile. If you're investigating agile, go for it! If you're not, you'd better plan to, or you will fail. Gartner Group says, if you don't do agile, you will die. Happy coding!
David Alfaro.
Celso Martins: (http://celsoavmartins.blogspot.com/)
Ubaid Khan: (Syntel Inc) Agile and Scrum is a very powerfull process working with. Bussiness benefits, high quality, fast deliverys. That's the way I want to work!
Lakshmi S Huttada: (IBM India Pvt Ltd) After working on 2 releases under the Agile planning, I now understand better the power of Agile. It sure helps the changing conditions of software development and helps the interaction between teams. Builds a confident and responsible team. And as I always say, Agile is Accelerating Growth in Leadership Excellence!
Raj Mudhar: (http://rajile.com)
Ramón Araujo: I have been years chasing "The perfect software development flow". This "simple" manifesto summarizes and fullfills all my expectations.
Saul Scanziani: (Wheel)
Yogesh Sajanikar.
hossam fawzallah fares: (ITI)
Dr. John N. Kalaras: (Quality Training Institute) I wholeheartedly endorse it. It's one of the best and most effective ways to design systems. I strongly recommend it to any project manager in both, IT and non-IT endeavors.
Pramod R Kininge.
Bino Manjasseril: (Flagstar Bank)
Edwin Jacques: The information technology industry is lumbering forward, though it is still dogged by the software development life cycle practices of yesteryear. Because IT is so critical to so many, it's easy for IT professionals to become arrogant, and disregard the customers' needs. However, the greatest success of our customers and ourselves will come from close collaboration on requirements and responding to change quickly. As we continue to elevate the level of abstraction in our science, making something a customer can interact with quickly is paramount to providing clarity and concreteness to our dialogue. The Agile movement is gaining critical mass, but we have quite a way to go. No matter the state of the economy, the most agile amongst us will survive and even thrive. Thank you to the authors of the Agile Manifesto, for giving words to the heartfelt desires of customer-driven developers. I get it, and I will do all I can to help others to get it too.
Rob Watson: (Webidextrous) I've been a fan and advocate of Agile methods and practices in software development and project management since 2005. All my projects implement just enough Agile best practices to get things done.
Toch de Leon: (IraVan SoftWares) Adaptive programming practice is really important if software engineers are to succeed in the trends of fast changing times. Polymorphic requirements needs polymorphic solutions from the foresight of the greatest minds collaborating to deliver excellent software intelligence.
Roger Cass: (RJ Cass, LLC)
Krzysztof Kosacki.
Anthony D'Silva: (Nike Inc.)
Andreas Görtzen: That's the way.
Frank Rios: (Protean IT Management, LLC) As a former software developer and architect, these are the principal's that always come naturally, but are driven out when you enter the "traditional" work-force using "traditional" project management. As a Certified ScrumMaster, these are the principal's I live by. As a Project Management Professional, I encourage, mentor, and coach PMP's in their transition to Agile and "deprogramming".
Claudio Merino: (diDigital.cl) interaction design <3 agile manifesto
Chunxing Shen: (http://CactusSoft.com/ITUtopia/) As a computer science practitioner, my goal is to providing to my customer the service of enjoyable experience with maximum ROI. Discovering and enhancing the optimal methodology should be my continuous approach and strive.
Lizette Rincon: (http://cr.linkedin.com/in/lizetterincon)
M. Scott Ford: (Corgibytes, LLC)
Parvez: (MicroPlace Inc) I strongly believe in Agile development and have worked with Extreme Programming. Passionate about its principals of continuous integration, re-factoring, simplicity and being flexible.
Wouter Dewanckel: (pmScrum) Since the beginning of 2008, I practise Scrum: It just works.
Adam Asch.
Linda Boggs.
Kyle Arjuna Crawford de Leon: (IraVanSoft) In developing softwares, we consider 2 beneficiaries, one is technology advancement and the other is support for the client who hopes to benefit from the technology at hand. If we lean on benefitting the client, Agile software development methodology get merit, developers get the freedom to be human again, but hey, somebody's got to fund that scenario. If you are a big company or organization, there are pros and cons, the company gets to keep the client and developers for keeping them happy, but they get to pay for the accomodation of adjustment and being flexible to keep up with the standards of agile. On the other hand, if you are a Garage one man Developer, the hits are on you, you extend flexibility in the expense of your own pocket just to keep your client for making them happy. Does that mean Agile is not for the one-man developer? I guess its a matter of priorities and investment. But nonetheless, Agile Methodology is client based and is very down to earth. It makes Software Development much faster and highle effective for incorporating the Development Team and Client Collaboration.
Mathieu Mazarin: (contractor at the CDC) It begins with people and ends with people, Our way gets muddied by losing site of this.
Ian Bush: (Ian Bush Consulting) As a Scrum practitioner for over four years, I believe in all four of the tenets presented here. Customer collaboration is tantamount to success in all projects and with Agile and Scrum it is even more important. Ian Bush, PMP
Ako Kaman.
Ehsan Valizadeh: (Tabriz Oil Refining Company)
Lee Fox.
Erik Fors-Andrée: (http://definitionofdone.blogspot.com)
Rick Marshall: (Zenucom Pty Ltd) I've been working this way for 30 years and would not swap it for other techniques. The tools I build all support this as the correct way to build software. There is no doubt in my mind that this is the only successful way to build large complex systems: small manageable pieces using these principles. One successful piece at a time.
Christophe Deniaud: I just truly believe in this way of working.
Victor Corrales: (http://www.corrales.org) I fully recogize and embrance the self-evident principles of building Software contained in this manifesto
Andy Delaney: (Mitsui Sumitomo)
James Stephenson: (Stephenson Consulting and Western International University) I have been doing this for years and didn't even realize it. I teach Software Engineering courses and Agile Methodologies are a key piece to our puzzle.
Jonathan Hammond.
Jürgen Strobel: (secure.at) I used to blame the problems with old fashioned, heavy processes on myself and my coworkers. The Agile Manifesto has helped me reevaluate my base values for much better results and satisfaction.
Ruchir Garg: (McAfee Inc.)
Alex Basyuk: (http://ua.linkedin.com/in/oleksandrbasyuk)

<< Previous  Index  Next >>