Agile Manifesto Signatories

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: 12 Dec to 31 Dec 2009
Shalabh Malviya.
John R. Southern: (Softwerke)
Tadeusz Cichocki: (Dr Tadeusz Cichocki Konsulting) First, try to understand what you have got really to achieve as a result of your activities, and be sure that your understanding and the actual progress are always valid. Second, put "brain" before any standard found in your organization or any method chosen; change or adapt them if needed.
Silvia Boehm: -- Individuals and interactions over processes and tools, because the people make the software and they are going to use it. -- Working software over comprehensive documentation, because you mostly do not need any doc, if the software is intuitive enough and works. -- Customer collaboration over contract negotiation, because contracts feed lawyers, collaboration feeds the product. -- Responding to change over following a plan, because plans are only definitions of targets, and targets can always be adapted to real and actual needs.
Marcos Eduardo Soares Brigante: Actually there's no other thoughts that can express better the way I wish to develop software than these value itens from the agile manifesto. While each developer has endlessly points to evolve, with the manifesto we share the same starting point and the same compass which guide us along the evolving way. I truly believe in it, count with me.
Jakub Arnold.
Matheus Fernando da Costa: (Sistema Gestor)
Clive Crocker: (CMC Testing) It works
Prof. P.S. Lokhande: (PVPP College of Engineering) It's an disciplined project management process which gives complete ownership of responsibility to each and every individual working in the project group. Here the need of customer is kept at the center point.
MAZE Jean-Luc: (Conseil & MOI)
Kavan Puranik.
Ruben Cortes: As a newbie to programming I must tell all that a simple and strong start to any task is paramount to success. It is in this unity and harmony of matter in the subjective and objective worlds that we are flowing. The flow is sweet and simple. That is why I give you a KISS of joy and purpose. The coming wind of knowledge is useless without a kite to fly and enjoy its power. Thanks to all for your effort and love.
steve garippo.
Patrick Wilson-Welsh: I have seen this work, and worked to make this work, for 9 years. My endorsement is a personal one. This is the way software wants to be built.
Rahul Mohan.
Xi Yang: I Support the Agile Manifesto!
Xiaoyu. Vítor Figueiró.
Giuseppe Delledonne: (adfor)
Amit Gupte: (Acty Systems India Pvt. Ltd) We wish to benefit from using a more quantified approach across the entire implementation process. The main benefits of adopting such an approach include effective communication of the scope/requirements and better support for feedback and progress tracking. A great initiative here folks..
Babak Aghajani: (MM1 Consulting)
Juri Strumpflohner: (http://blog.js-development.com)
Steve Stevenson: (School of Computing, Clemson) As a computational science educator, I encourage the use of agile methods
Jorge Gamas.
JV MADHAVAN: (ROCKG MICRO TECH) Yes, in my, more than a decade, experience we always seen customers asking for changes in every part of the process. It would be good to have strong collaboration with customer to avoid last minute surprises. Agile (which embraces some level of documentation) could be a better alternative for current scenario.
Marco Balgera: (TelneXt srl)
Robert Else: (ELSEWARE) I believe software projects are primarily people projects. The technology is easy compared to the challenge of clear communication and productive interaction among the participants. If you get the people part right, the technology part usually turns out better than anyone expected. The Agile Manifesto supports this philosophy; I'm all for it.
Justin Rhinesmith: (http://www.justinrhinesmith.com) It has been my experience that these ideals, when followed, not only produce better software, but promote a more rewarding professional life as well.
Tim Heller: (Presidium Consulting & Development, LLC) I support the Agile Manifesto
Bruce Volpe.
Gabriel Rinaldi: (Gabriel Rinaldi)
Kihara Absolomon: (Movert Technologies) While its important to develop great applications, the process used should be simple enough to allow everyone on board to freely participate making everyone feel he/she is part of the team. The working environment should also be conducive enough for the developers and the clients to feel comfortable and confident that everyone is working together. These are the kind of principles being endorsed by agile that makes software development look more less than rocket science.
Dieter Hönigmann: (n22 e.U.) At the frontiers of truly innovative clinical applications, flexibility which comes along with agile software development is essential.
Vinicius Horewicz: (http://horewi.cz)
Veeraiah Katta.
Hatem Mahmoud: (http://www.expressionlab.com) Eduardo J. Zambrano: (Origos) The Agile Manifesto express perfectly the way I have been developing software successfully during the last 30 years. The main Origos product has been getting bigger and bigger and more complex every day, forcing me to look for standards and models to maintain the control of the development. I couldn't find what I was looking for, until I found the Agile Manifesto. Now I'm fully aware that this is the only real way to go.
Prashant Sharma: (Proteans Software Solutions) Agile works for me and I think it can work for anyone. Like any new process give it the time, effort and focus it deserve and Agile will make things better you, even though if it doesn't do wonders right-away. I would anyday recommend Individuals and Interactions over Processes and Tools and a Working software over piles of Documents.
Michael Furmaniuk: Light-weight methods, open communication with a view of the historical are all aspects of a process I value and try to instill in the environments I am in. I've been using Agile in one form or another for years and it's never disappointed me.
Mozart Brocchini: (Bridgeway Software) Commitment to the manifesto makes us remember to always stick with what is important to deliver quality software on time.
Brad Leiby: (Uncommon Solutions, Inc.) We have found over the years, often in hindsight, that successful projects are determined less by the quality of the original plan than by whether a plan existed at all and whether stakeholders were aware of it.Further, the level of adherence to the plan is less predictive of success than the authenticity of the consideration given to the original plan as time passes, and the disciplined application of the learning that comes from this tension (resulting from the disparity between the original plan and reality) in repeatedly formulating and committing to a revised plan. In other words, we've found through experience that the Agile Manifesto is "spot on."
Bruno Fontoura Costa: I do endorse the agile methodoly
Wojciech Kruszewski: (OXOS.pl)
Axelle Ziegler: (Ankama)
Sazzad Rafique: From my experiences for last five years, this is the simple and obvious way software development should be practiced.
Marcus Maute: That's the way!
Gary Vecchio, PMP: When your customer is faced with the challenges of an evolving threat and depends on mission-critical systems to neutralize those threats while minimizing casualties then you need a methodology that can meet those demands.
Krishna Prasad.
Ivo.
Luis Henrique Albinati Jr.: (Cyberlynxx)

<< Previous Index Next >>

Signatures Received: 12 Dec to 31 Dec 2009
Shalabh Malviya. John R. Southern: (Softwerke) Tadeusz Cichocki: (Dr Tadeusz Cichocki Konsulting) First, try to understand what you have got really to achieve as a result of your activities, and be sure that your understanding and the actual progress are always valid. Second, put "brain" before any standard found in your organization or any method chosen; change or adapt them if needed. Silvia Boehm: -- Individuals and interactions over processes and tools, because the people make the software and they are going to use it. -- Working software over comprehensive documentation, because you mostly do not need any doc, if the software is intuitive enough and works. -- Customer collaboration over contract negotiation, because contracts feed lawyers, collaboration feeds the product. -- Responding to change over following a plan, because plans are only definitions of targets, and targets can always be adapted to real and actual needs. Marcos Eduardo Soares Brigante: Actually there's no other thoughts that can express better the way I wish to develop software than these value itens from the agile manifesto. While each developer has endlessly points to evolve, with the manifesto we share the same starting point and the same compass which guide us along the evolving way. I truly believe in it, count with me. Jakub Arnold. Matheus Fernando da Costa: (Sistema Gestor) Clive Crocker: (CMC Testing) It works Prof. P.S. Lokhande: (PVPP College of Engineering) It's an disciplined project management process which gives complete ownership of responsibility to each and every individual working in the project group. Here the need of customer is kept at the center point. MAZE Jean-Luc: (Conseil & MOI) Kavan Puranik. Ruben Cortes: As a newbie to programming I must tell all that a simple and strong start to any task is paramount to success. It is in this unity and harmony of matter in the subjective and objective worlds that we are flowing. The flow is sweet and simple. That is why I give you a KISS of joy and purpose. The coming wind of knowledge is useless without a kite to fly and enjoy its power. Thanks to all for your effort and love. steve garippo. Patrick Wilson-Welsh: I have seen this work, and worked to make this work, for 9 years. My endorsement is a personal one. This is the way software wants to be built. Rahul Mohan. Xi Yang: I Support the Agile Manifesto! Xiaoyu.	Vítor Figueiró. Giuseppe Delledonne: (adfor) Amit Gupte: (Acty Systems India Pvt. Ltd) We wish to benefit from using a more quantified approach across the entire implementation process. The main benefits of adopting such an approach include effective communication of the scope/requirements and better support for feedback and progress tracking. A great initiative here folks.. Babak Aghajani: (MM1 Consulting) Juri Strumpflohner: (http://blog.js-development.com) Steve Stevenson: (School of Computing, Clemson) As a computational science educator, I encourage the use of agile methods Jorge Gamas. JV MADHAVAN: (ROCKG MICRO TECH) Yes, in my, more than a decade, experience we always seen customers asking for changes in every part of the process. It would be good to have strong collaboration with customer to avoid last minute surprises. Agile (which embraces some level of documentation) could be a better alternative for current scenario. Marco Balgera: (TelneXt srl) Robert Else: (ELSEWARE) I believe software projects are primarily people projects. The technology is easy compared to the challenge of clear communication and productive interaction among the participants. If you get the people part right, the technology part usually turns out better than anyone expected. The Agile Manifesto supports this philosophy; I'm all for it. Justin Rhinesmith: (http://www.justinrhinesmith.com) It has been my experience that these ideals, when followed, not only produce better software, but promote a more rewarding professional life as well. Tim Heller: (Presidium Consulting & Development, LLC) I support the Agile Manifesto Bruce Volpe. Gabriel Rinaldi: (Gabriel Rinaldi) Kihara Absolomon: (Movert Technologies) While its important to develop great applications, the process used should be simple enough to allow everyone on board to freely participate making everyone feel he/she is part of the team. The working environment should also be conducive enough for the developers and the clients to feel comfortable and confident that everyone is working together. These are the kind of principles being endorsed by agile that makes software development look more less than rocket science. Dieter Hönigmann: (n22 e.U.) At the frontiers of truly innovative clinical applications, flexibility which comes along with agile software development is essential. Vinicius Horewicz: (http://horewi.cz) Veeraiah Katta. Hatem Mahmoud: (http://www.expressionlab.com)	Eduardo J. Zambrano: (Origos) The Agile Manifesto express perfectly the way I have been developing software successfully during the last 30 years. The main Origos product has been getting bigger and bigger and more complex every day, forcing me to look for standards and models to maintain the control of the development. I couldn't find what I was looking for, until I found the Agile Manifesto. Now I'm fully aware that this is the only real way to go. Prashant Sharma: (Proteans Software Solutions) Agile works for me and I think it can work for anyone. Like any new process give it the time, effort and focus it deserve and Agile will make things better you, even though if it doesn't do wonders right-away. I would anyday recommend Individuals and Interactions over Processes and Tools and a Working software over piles of Documents. Michael Furmaniuk: Light-weight methods, open communication with a view of the historical are all aspects of a process I value and try to instill in the environments I am in. I've been using Agile in one form or another for years and it's never disappointed me. Mozart Brocchini: (Bridgeway Software) Commitment to the manifesto makes us remember to always stick with what is important to deliver quality software on time. Brad Leiby: (Uncommon Solutions, Inc.) We have found over the years, often in hindsight, that successful projects are determined less by the quality of the original plan than by whether a plan existed at all and whether stakeholders were aware of it.Further, the level of adherence to the plan is less predictive of success than the authenticity of the consideration given to the original plan as time passes, and the disciplined application of the learning that comes from this tension (resulting from the disparity between the original plan and reality) in repeatedly formulating and committing to a revised plan. In other words, we've found through experience that the Agile Manifesto is "spot on." Bruno Fontoura Costa: I do endorse the agile methodoly Wojciech Kruszewski: (OXOS.pl) Axelle Ziegler: (Ankama) Sazzad Rafique: From my experiences for last five years, this is the simple and obvious way software development should be practiced. Marcus Maute: That's the way! Gary Vecchio, PMP: When your customer is faced with the challenges of an evolving threat and depends on mission-critical systems to neutralize those threats while minimizing casualties then you need a methodology that can meet those demands. Krishna Prasad. Ivo. Luis Henrique Albinati Jr.: (Cyberlynxx)