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: 17 Feb to 07 Mar 2010
Vitas Povilaitis.
rashid: (http://www.skrbl.com) And for the check book managers out there, "delivery over control".
Parker Lord: I have been involved with projects using Agile for quiet some time and it has worked much better than the more structured methodologies. The important thing to keep in mind is the first part of the statement, in that there is still value in the items on the right, specially to business people!
Robert Boelter: (dba NoZZZs) Agile principals are founded on achieving productivity through collaboration. They are applied through trust-based relationships that lead to ownership and accomplishment based on an understanding of business value.
V. Ravi Shankar: (Castlerock Research) Working with Agile methodologies for over 1 and half year.
Agustín Gutiérrez: (Netlabs)
Ene Querney: (Evolve Again Consulting Group)
Navinderjit Singh: (Genpact)
Jool Atkins CITP, FBCS: (Matrix FortyTwo) As an IT Training Professional, I believe that Agile Projects meet the needs of users more effectively and quicker than traditional project management. I hope that Agile PMs are also more receptive to the benefit of IT Training's involvement.
Guy Saville: (SA Home Loans) Based on many years of project mgt and software development managerial experience, I fully endorse and practise this wise and powerful manifesto. Use it, and you will realise and release the full potential of your people.
Mark Bandillo.
Carol Tikerperi: (Trinidad Consulting) Planting UX work to Agile development.
Robert Colee: (Dlobal Communications Group)
Neil: (Metasystems ERP Software) The principles that Agile Manifesto is following are must for all businesses to be successful.These principles let people make confident and cost-efficient business decisions. You guys are doing a great Job. Keep up the good work.
Neil: (Call Center Consultants) Agility is what drives one’s success. These principles are not proposed Silver Bullets but a pragmatic and functional set of practices that will completely metamorphose your organization into a successful one. Great work. All the best....Cheers
Ranvir Singh Mourya: I second these thoughts as instead of giving value to processes we should give more value to technical, behavioral and functional aspect of project. Because at the end it doesn’t matter how much document, how much process you prepared or followed, only matter is that your creation fulfill the requirement and satisfy the end user. If you are a developer/Story writer/Builder, you have to do things as per your customer not as per the process you have set to get your customer satisfaction.
Touko Vainio-Kaila.
James Hammond: (CMACE)
Rezwanul Huda.
Emilia Ellen Breton: (http://blog.scrumpen.com/)
Sif E. Elharti: One needs good principals for better productivity...
Jason Millaway: (Prairie Packaging/Pactiv Corp)
Terson Junior: (Iplanrio)
Tim Wingfield.
Guðlaugur Egilsson.
Iqbal Shaikh.
Alberto Patino: (http://knowledgefrontier.blogspot.com) David Braund: I believe agile methods are good throughout a project but they are especially good at the front end of a project. Many projects fail, particularly large ones in the public sector (and many in the public sector are very large) because in the rush to procurement, requirements are not fully discussed and understood by all the parties involved. Agile methods can allow most of the 'baby-stuff' mistakes to be spotted and avoided early on.
Stefan Wagner: (Bayer Pty Ltd) We intentionally do not offer fixed-price project proposals, as they are deemed outdated and inferior to an adaptive, iterative approach, yielding a much better quality outcome for the client. With the adaptive planning approach clients see their application system grow and mature, giving them a better feeling of control and confidence. The iterative approach demands a much higher level of project & development interaction from client staff, allowing them continued input. Specifications become living documents, rather than an inflexible commitment as a result of the scope lock-in, being part of the fixed-price proposal. The main issue with fixed prices proposals is that any change in requirements and circumstances results in a costly change request, which eventually makes the project considerably more expensive than it has to be. Further, the iterative approach also prepares and embraces change, which allows for earlier stage releases of project iterations.
Lars Enevold.
Yang Xiao: (BBC R&D) Agile Software Development is the only way forward. Software development is a design process rather than a construction process.
Rob Sherwood.
Steven Fram: (Caring.com) Scrum and Agile have revolutionized my work at start-ups, including at BabyCenter and Caring.com. As a founder of Caring.com, Scrum/Agile were required elements of our culture/process literally from Day 1.
F.J. Oberkamp: The agile methodology is the only reasonable concept to define the exact needs and expectations of the stakeholders/shareholders allowing for the delivery of a functional and useful end product. It also provides a direct communications flow that handles issues revolving around "expectation management". It is an evolved processes set that aptly illustrates the elimination of the old story of the 8 elements involved of what the customer actually wanted. Agile, if properly utilized, virtually eliminates the issues of the human interface to technology being so difficult for the average human to deal with. If the initial homework to define the true needs of the actual end users has been performed correctly, agile will deliver an appropriate product without all the "techno speak" of many final products. Instead of focusing on squeezing a client into a predefined "box", the method concentrates on using development tools and procedures to deliver a final product that will be used to its fullest extent because it makes sense to the humans. Software, applications and systems are only as good as the functions they provide to the humans and the flexibility and scalability they provide for the future. With the use of the agile methodology, all the parties have an equal understanding of what is required and what is possible. With proper management of the methodology, this will come as close to assuring success and a mutually beneficial delivery as is possible. Always remember that the end result is only as good as the input and assessment thereof.
Sibonelo: (University of KwaZulu Natal) Khoo BoonHo: (Motorola Technology Penang) Trusting and empowering the TEAM to do the right thing is the key to successful software projects.
Glenn Murray: (Conn3cted) Conn3cted strongly support the agile manifesto and apply its principles throughout our business.
Kevin Bolam: As a student i am taught the difference between Agile methodologies and others. And as a consiquence seen (although in a smiulated enviroment) that Agile is the best process in which to deliver quality software to a customer quickly and efficiantly
Roy F. Donasco: Agile for most people who have not experienced it is just a buzz word. To me it's a mindset and software development lifestyle that encourages team work, communication, flexibility, and adaptability to business changes.
Nitin More: (Oracle Financial Software Services Ltd.) adopted agile methodology since past 3 years.
HuiningLiu: (test) Agile give us a good way to deal with the work. I am focus on the agile test more.
mark lacey: (afekt media)
Adam Porad.
Thomas Lore: (http://zonorus.marlboro.edu/~tlore/)
Srinivas Sirigina: (SSI Inc) Agile is a great paradigm shift in software development. I agree that most of the requirements are written in the very beginning of project and are never updated 100%. I am all for skipping the detailed requirements and go with brief use cases, mind maps and collaboration with business users.
Lance Kind: (http://LancerKind.com) I've been doing this since Kent Beck got his hands on me in 1999. The manifesto can be applied to your life well beyond software development. I've applied this to writing fiction, and I'm trying to figure out how this can be applied to government. This philosophy makes so much sense that since I've learned it, I've never wanted to do waterfall again. So I've been coaching developers and organizations about how to do this. (In an official consulting capacity or not.) Now I might as well make it official by signing the document. Plus saying you've signed a manifesto is cool! ;-) ==>Lancer---
Tim Podolske, CSM: (American Family Insurance) Quite a paradox. Simple, yet complex.
Armistral: (News Corporation) Independent of any specific methodology the manifesto does a great job of defining some practical ways to do great work, especially by empowering teams and team members to do their best work (actually writing good code) rather than getting lost in non-essentials and distractions. 9 years on this document still stands above any other singular philosophy I can find in terms of clarify, brevity and common sense. Best Regards, Armistral
Nathan Frost: (GiantSparrow) The Agile Manifesto is the most concise -- yet complete -- definition of effective development philosophy I've seen. Truly a call to arms.
Dax Miller: (The VGM Group, Inc) History proves that advancement in software development and engineering is imminent. As we improve, we change our processes and workflow patterns to match the technical curve of our respective industry. One thing that does not change is the importance of Communication. The technical experts behind the processes and tools, as well as the customer/client and ultimate consumer that drives change with demand, feedback and suggestion. The Agile Manifesto keeps our perception of the future aligned with the fundamental truth of business...Communication.

<< Previous Index Next >>

Signatures Received: 17 Feb to 07 Mar 2010
Vitas Povilaitis. rashid: (http://www.skrbl.com) And for the check book managers out there, "delivery over control". Parker Lord: I have been involved with projects using Agile for quiet some time and it has worked much better than the more structured methodologies. The important thing to keep in mind is the first part of the statement, in that there is still value in the items on the right, specially to business people! Robert Boelter: (dba NoZZZs) Agile principals are founded on achieving productivity through collaboration. They are applied through trust-based relationships that lead to ownership and accomplishment based on an understanding of business value. V. Ravi Shankar: (Castlerock Research) Working with Agile methodologies for over 1 and half year. Agustín Gutiérrez: (Netlabs) Ene Querney: (Evolve Again Consulting Group) Navinderjit Singh: (Genpact) Jool Atkins CITP, FBCS: (Matrix FortyTwo) As an IT Training Professional, I believe that Agile Projects meet the needs of users more effectively and quicker than traditional project management. I hope that Agile PMs are also more receptive to the benefit of IT Training's involvement. Guy Saville: (SA Home Loans) Based on many years of project mgt and software development managerial experience, I fully endorse and practise this wise and powerful manifesto. Use it, and you will realise and release the full potential of your people. Mark Bandillo. Carol Tikerperi: (Trinidad Consulting) Planting UX work to Agile development. Robert Colee: (Dlobal Communications Group) Neil: (Metasystems ERP Software) The principles that Agile Manifesto is following are must for all businesses to be successful.These principles let people make confident and cost-efficient business decisions. You guys are doing a great Job. Keep up the good work. Neil: (Call Center Consultants) Agility is what drives one’s success. These principles are not proposed Silver Bullets but a pragmatic and functional set of practices that will completely metamorphose your organization into a successful one. Great work. All the best....Cheers Ranvir Singh Mourya: I second these thoughts as instead of giving value to processes we should give more value to technical, behavioral and functional aspect of project. Because at the end it doesn’t matter how much document, how much process you prepared or followed, only matter is that your creation fulfill the requirement and satisfy the end user. If you are a developer/Story writer/Builder, you have to do things as per your customer not as per the process you have set to get your customer satisfaction. Touko Vainio-Kaila. James Hammond: (CMACE) Rezwanul Huda. Emilia Ellen Breton: (http://blog.scrumpen.com/) Sif E. Elharti: One needs good principals for better productivity... Jason Millaway: (Prairie Packaging/Pactiv Corp) Terson Junior: (Iplanrio) Tim Wingfield. Guðlaugur Egilsson. Iqbal Shaikh. Alberto Patino: (http://knowledgefrontier.blogspot.com)	David Braund: I believe agile methods are good throughout a project but they are especially good at the front end of a project. Many projects fail, particularly large ones in the public sector (and many in the public sector are very large) because in the rush to procurement, requirements are not fully discussed and understood by all the parties involved. Agile methods can allow most of the 'baby-stuff' mistakes to be spotted and avoided early on. Stefan Wagner: (Bayer Pty Ltd) We intentionally do not offer fixed-price project proposals, as they are deemed outdated and inferior to an adaptive, iterative approach, yielding a much better quality outcome for the client. With the adaptive planning approach clients see their application system grow and mature, giving them a better feeling of control and confidence. The iterative approach demands a much higher level of project & development interaction from client staff, allowing them continued input. Specifications become living documents, rather than an inflexible commitment as a result of the scope lock-in, being part of the fixed-price proposal. The main issue with fixed prices proposals is that any change in requirements and circumstances results in a costly change request, which eventually makes the project considerably more expensive than it has to be. Further, the iterative approach also prepares and embraces change, which allows for earlier stage releases of project iterations. Lars Enevold. Yang Xiao: (BBC R&D) Agile Software Development is the only way forward. Software development is a design process rather than a construction process. Rob Sherwood. Steven Fram: (Caring.com) Scrum and Agile have revolutionized my work at start-ups, including at BabyCenter and Caring.com. As a founder of Caring.com, Scrum/Agile were required elements of our culture/process literally from Day 1. F.J. Oberkamp: The agile methodology is the only reasonable concept to define the exact needs and expectations of the stakeholders/shareholders allowing for the delivery of a functional and useful end product. It also provides a direct communications flow that handles issues revolving around "expectation management". It is an evolved processes set that aptly illustrates the elimination of the old story of the 8 elements involved of what the customer actually wanted. Agile, if properly utilized, virtually eliminates the issues of the human interface to technology being so difficult for the average human to deal with. If the initial homework to define the true needs of the actual end users has been performed correctly, agile will deliver an appropriate product without all the "techno speak" of many final products. Instead of focusing on squeezing a client into a predefined "box", the method concentrates on using development tools and procedures to deliver a final product that will be used to its fullest extent because it makes sense to the humans. Software, applications and systems are only as good as the functions they provide to the humans and the flexibility and scalability they provide for the future. With the use of the agile methodology, all the parties have an equal understanding of what is required and what is possible. With proper management of the methodology, this will come as close to assuring success and a mutually beneficial delivery as is possible. Always remember that the end result is only as good as the input and assessment thereof. Sibonelo: (University of KwaZulu Natal)	Khoo BoonHo: (Motorola Technology Penang) Trusting and empowering the TEAM to do the right thing is the key to successful software projects. Glenn Murray: (Conn3cted) Conn3cted strongly support the agile manifesto and apply its principles throughout our business. Kevin Bolam: As a student i am taught the difference between Agile methodologies and others. And as a consiquence seen (although in a smiulated enviroment) that Agile is the best process in which to deliver quality software to a customer quickly and efficiantly Roy F. Donasco: Agile for most people who have not experienced it is just a buzz word. To me it's a mindset and software development lifestyle that encourages team work, communication, flexibility, and adaptability to business changes. Nitin More: (Oracle Financial Software Services Ltd.) adopted agile methodology since past 3 years. HuiningLiu: (test) Agile give us a good way to deal with the work. I am focus on the agile test more. mark lacey: (afekt media) Adam Porad. Thomas Lore: (http://zonorus.marlboro.edu/~tlore/) Srinivas Sirigina: (SSI Inc) Agile is a great paradigm shift in software development. I agree that most of the requirements are written in the very beginning of project and are never updated 100%. I am all for skipping the detailed requirements and go with brief use cases, mind maps and collaboration with business users. Lance Kind: (http://LancerKind.com) I've been doing this since Kent Beck got his hands on me in 1999. The manifesto can be applied to your life well beyond software development. I've applied this to writing fiction, and I'm trying to figure out how this can be applied to government. This philosophy makes so much sense that since I've learned it, I've never wanted to do waterfall again. So I've been coaching developers and organizations about how to do this. (In an official consulting capacity or not.) Now I might as well make it official by signing the document. Plus saying you've signed a manifesto is cool! ;-) ==>Lancer--- Tim Podolske, CSM: (American Family Insurance) Quite a paradox. Simple, yet complex. Armistral: (News Corporation) Independent of any specific methodology the manifesto does a great job of defining some practical ways to do great work, especially by empowering teams and team members to do their best work (actually writing good code) rather than getting lost in non-essentials and distractions. 9 years on this document still stands above any other singular philosophy I can find in terms of clarify, brevity and common sense. Best Regards, Armistral Nathan Frost: (GiantSparrow) The Agile Manifesto is the most concise -- yet complete -- definition of effective development philosophy I've seen. Truly a call to arms. Dax Miller: (The VGM Group, Inc) History proves that advancement in software development and engineering is imminent. As we improve, we change our processes and workflow patterns to match the technical curve of our respective industry. One thing that does not change is the importance of Communication. The technical experts behind the processes and tools, as well as the customer/client and ultimate consumer that drives change with demand, feedback and suggestion. The Agile Manifesto keeps our perception of the future aligned with the fundamental truth of business...Communication.