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: 20 Jul to 30 Jul 2010
Rob Fowler: Agile is a magnet for great thinking in our field.
Ümit Demir: (ASELSAN Inc.)
Anila KV: (Alcatel-Lucent) This is definitely the correct way forward & about time I joined this group.
Leo Romoff: (B2D Projetos e Sistemas)
Pradeep Yamujala: I worked with logistics domain and encountered many hurdles during development. These are mostly due to a gap while interpreting the customer stories by the developers. All of us heard customer voice at the beginning and at the ending. . Having big timescales will bring a gap with customer expectations and also having huge goals at shorter timescales will make software unproductive. Applying the Agile manifesto will definitely makes development is on track and at par with customer expectations.
Phaneendra Srishti: Trust Agile methodologies for better service management
Prasanna: One of the most advanced culture we are bringing to Software Development to help improve quality of software, quality of life and quality of humans in us, is by following the basic principles of agile manifesto.
Rémy SAISSY.
Fábio Luiz Nery de Miranda: (miranTI Tecnologia)
Gráinne Ní Dhuinnín.
Uzo Okorafor.
Nihad Abbasov: (X to Normal-A)
Carlo Pecchia: (http://carlopecchia.eu)
Rajat Bhalla: (VinSol) Coming from a background of Waterfall model and old school methodologies of managing software projects, I was offered new hope by Agile. And, I am trying to spread the light by sharing it with others in my organisation.
Doureradjou Chanemougame: Hello, I totally agree with the values you have highlighted, nowadays we have the tendency not to focus on essentials! These values are truly adequate to the current scenario where everything changes at a fast pace but strangely people stick to the values in the right side! Warm regards, Doureradjou Chanemougame
ivan de martino.
Manoj Kumar Rai: The changes are inevitable part of the software development cycle. And a flexible plan that can incorporate changes at any stage of a project will certainly provide edge over competitors. “Responding to change” (without spending too much time on re-planning) is the basic idea for which I am a big supporter of this methodology. Concept of the frequent releases keep both parties *truly* at the same page during life cycle and that avoids unexpected changes at dying end of a project. I have noticed another wonderful benefit of the Agile methodology (frequent releases) that it keep the team members motivated as they quick feedback on their hard work.
Aniruddha Ray.
Polina Petrishcheva. Marco Cecconi: As far as I know, there is no other feasible way of developing software. I've tried a lot of different methodologies - no matter what your particular methodology is officially called, all good, meaningful and sensible practical implementations will necessarily fall towards agile, because that's how the world works.
Gu Xuan: I highly agree the Manifesto of Agile. The traditional software development methodology makes the commitment and planning so hard especially for the projects with a lot of variance. Looking forward to the progress of the Agile methodology...
Valentin Malakhov: (hotelclub) I have always been a big supporter of Agile Approach since my first line of "commercial" code back in the 90s. Back then I somehow felt that the distinction between the agile and waterfal was purely correlated with the size of the project, when the latter would be used for the projects with large budget. Also being a BI/DWH specialist, rather than web or .NET, makes it harder to apply agile methods, though the 12 principals can easily be applied. We are currently working SCRUM and are very happy so far. Valentin
Ramses Paiva: (IT Consulting) Because people are more worthy than tools, processes and a bunch of paper.
Enrico Berardi: (TRS SpA)
Jack Soon: (House Siding)
Fred: (Home Improvement) I support the agial manifesto!
Polo: (Home Ideas) I believe Agile is the best way to go with software development and Agile Manifesto brings it forward to larger audience.
David Sachdev: (Innotac, Inc.) Agile Development is crucial in delivering to the customer the product that they want and need, rather then the product that they ask for. We as technical leaders need to employ the tenets of the Agile Manifesto, and work hard to educate others on proper Agile Development. http://www.translucent-development.com/drupal/agile_development_links
Ravinder Chauhan: (CSC Global Business Solutions)
Otavio Ferreira: (MIH SWAT) I've been successfully applying the values and principles listed by this manifesto for three years. It is especially useful for environments in which requirements change quickly and often. As a clear context example, there is the development of Web applications and Web services.
Calvin Madlock: (LACCD) Five years ago my past employer coined the phrase, “Changing the Game”, as an IT project theme. I would like to coin a theme for my current employer: “The Game has Changed”. The more I’ve researched facts regarding the Manifesto for Agile Software Development the more impressed I’ve become with the Agile process model in the evolution of software development. I find that the Agile Manifesto model is appropriate for the today's software engineering efforts. Libor Bus: (Eccam, Czech Republic) Great ideas to follow!
Tom: (Door reviews) I totally agree on the principles behind the Manifesto. Only one doubt about documentation: also working software needs essential documentation.
Ameet Shah: Agile Methodologies should be the only way to build software
Samuel Diniz Casimiro: (http://blogdosamueldiniz.blogspot.com/) Minha experiência me ensinou que bons desenvolvedores trabalhando em equipe, lado a lado, valorizando a livre comunicação sempre vão trabalhar melhor que qualquer equipe seja ela qual for, mas que estiver amarrada a processos muito formais produzindo documentação geralmente inútil. Backlog, diagrama de arquitetura e caso de uso: Precisa mais do que isso? O resto é boa comunicação e talento!
ravi: Everyone is happy as long as everyone excepts the agile manifesto.
mohsendokht: (pooya sanat behineh Co.) mohsendokht
Arjit Chatterjee: (RavenMyth Interactive Studios) Game Production is all about chasing uncertainty, knowing and believing in agile gives me the ability to foresee and react to changes comfortably. The more I understand agile the lighter, fun and more effective game production becomes for me. I hope to make this my second nature one day.
Denis Piazentin: (http://twitter.com/denisrmp)
David Weintraub: (Fulcrum Automation & Control Technologies) Fulcrum Controls was started in 2001 by three people. We where fortunate in that we were motivated to make software, if for know other reason than to survive as a business. Over time we were lucky enough to find most of the Manifesto's principles by need. So supporting this manifesto, that helps make software better is as it should be "a know brainer".
Nikhil More.
Ericson Rafael: (Private) I really agree with all of the proposals presented here and I’d like to say that all of my students will be called to read and adopt this manifesto. Thank you all.
Harpreet Sidhu: Doing what's actually needed satisfies customers and developers.
Emilio Gratton: I fully support the Agile approach and its ability to help developers to work beyond single tasks. My only doubt is about the word "individuals". I'd like to refer to the "users" instead. It's just because I'd like to tailor a development for a position instead for a specific person that, sooner or later, might change.
Govind Davis: (MCF Technology Solutions) We were living Agile long before we even knew what it was .. . so exciting to find there are a world of others thinking about value over paperwork.
Francesco Pezzino.
Igor Gordiichuk.
Zachary Crockett: (Hypergolic Motion, LLC)
Viyom Jain.
Marcus Winkler: (Heraeus Kulzer)

<< Previous Index Next >>

Signatures Received: 20 Jul to 30 Jul 2010
Rob Fowler: Agile is a magnet for great thinking in our field. Ümit Demir: (ASELSAN Inc.) Anila KV: (Alcatel-Lucent) This is definitely the correct way forward & about time I joined this group. Leo Romoff: (B2D Projetos e Sistemas) Pradeep Yamujala: I worked with logistics domain and encountered many hurdles during development. These are mostly due to a gap while interpreting the customer stories by the developers. All of us heard customer voice at the beginning and at the ending. . Having big timescales will bring a gap with customer expectations and also having huge goals at shorter timescales will make software unproductive. Applying the Agile manifesto will definitely makes development is on track and at par with customer expectations. Phaneendra Srishti: Trust Agile methodologies for better service management Prasanna: One of the most advanced culture we are bringing to Software Development to help improve quality of software, quality of life and quality of humans in us, is by following the basic principles of agile manifesto. Rémy SAISSY. Fábio Luiz Nery de Miranda: (miranTI Tecnologia) Gráinne Ní Dhuinnín. Uzo Okorafor. Nihad Abbasov: (X to Normal-A) Carlo Pecchia: (http://carlopecchia.eu) Rajat Bhalla: (VinSol) Coming from a background of Waterfall model and old school methodologies of managing software projects, I was offered new hope by Agile. And, I am trying to spread the light by sharing it with others in my organisation. Doureradjou Chanemougame: Hello, I totally agree with the values you have highlighted, nowadays we have the tendency not to focus on essentials! These values are truly adequate to the current scenario where everything changes at a fast pace but strangely people stick to the values in the right side! Warm regards, Doureradjou Chanemougame ivan de martino. Manoj Kumar Rai: The changes are inevitable part of the software development cycle. And a flexible plan that can incorporate changes at any stage of a project will certainly provide edge over competitors. “Responding to change” (without spending too much time on re-planning) is the basic idea for which I am a big supporter of this methodology. Concept of the frequent releases keep both parties truly at the same page during life cycle and that avoids unexpected changes at dying end of a project. I have noticed another wonderful benefit of the Agile methodology (frequent releases) that it keep the team members motivated as they quick feedback on their hard work. Aniruddha Ray. Polina Petrishcheva.	Marco Cecconi: As far as I know, there is no other feasible way of developing software. I've tried a lot of different methodologies - no matter what your particular methodology is officially called, all good, meaningful and sensible practical implementations will necessarily fall towards agile, because that's how the world works. Gu Xuan: I highly agree the Manifesto of Agile. The traditional software development methodology makes the commitment and planning so hard especially for the projects with a lot of variance. Looking forward to the progress of the Agile methodology... Valentin Malakhov: (hotelclub) I have always been a big supporter of Agile Approach since my first line of "commercial" code back in the 90s. Back then I somehow felt that the distinction between the agile and waterfal was purely correlated with the size of the project, when the latter would be used for the projects with large budget. Also being a BI/DWH specialist, rather than web or .NET, makes it harder to apply agile methods, though the 12 principals can easily be applied. We are currently working SCRUM and are very happy so far. Valentin Ramses Paiva: (IT Consulting) Because people are more worthy than tools, processes and a bunch of paper. Enrico Berardi: (TRS SpA) Jack Soon: (House Siding) Fred: (Home Improvement) I support the agial manifesto! Polo: (Home Ideas) I believe Agile is the best way to go with software development and Agile Manifesto brings it forward to larger audience. David Sachdev: (Innotac, Inc.) Agile Development is crucial in delivering to the customer the product that they want and need, rather then the product that they ask for. We as technical leaders need to employ the tenets of the Agile Manifesto, and work hard to educate others on proper Agile Development. http://www.translucent-development.com/drupal/agile_development_links Ravinder Chauhan: (CSC Global Business Solutions) Otavio Ferreira: (MIH SWAT) I've been successfully applying the values and principles listed by this manifesto for three years. It is especially useful for environments in which requirements change quickly and often. As a clear context example, there is the development of Web applications and Web services. Calvin Madlock: (LACCD) Five years ago my past employer coined the phrase, “Changing the Game”, as an IT project theme. I would like to coin a theme for my current employer: “The Game has Changed”. The more I’ve researched facts regarding the Manifesto for Agile Software Development the more impressed I’ve become with the Agile process model in the evolution of software development. I find that the Agile Manifesto model is appropriate for the today's software engineering efforts.	Libor Bus: (Eccam, Czech Republic) Great ideas to follow! Tom: (Door reviews) I totally agree on the principles behind the Manifesto. Only one doubt about documentation: also working software needs essential documentation. Ameet Shah: Agile Methodologies should be the only way to build software Samuel Diniz Casimiro: (http://blogdosamueldiniz.blogspot.com/) Minha experiência me ensinou que bons desenvolvedores trabalhando em equipe, lado a lado, valorizando a livre comunicação sempre vão trabalhar melhor que qualquer equipe seja ela qual for, mas que estiver amarrada a processos muito formais produzindo documentação geralmente inútil. Backlog, diagrama de arquitetura e caso de uso: Precisa mais do que isso? O resto é boa comunicação e talento! ravi: Everyone is happy as long as everyone excepts the agile manifesto. mohsendokht: (pooya sanat behineh Co.) mohsendokht Arjit Chatterjee: (RavenMyth Interactive Studios) Game Production is all about chasing uncertainty, knowing and believing in agile gives me the ability to foresee and react to changes comfortably. The more I understand agile the lighter, fun and more effective game production becomes for me. I hope to make this my second nature one day. Denis Piazentin: (http://twitter.com/denisrmp) David Weintraub: (Fulcrum Automation & Control Technologies) Fulcrum Controls was started in 2001 by three people. We where fortunate in that we were motivated to make software, if for know other reason than to survive as a business. Over time we were lucky enough to find most of the Manifesto's principles by need. So supporting this manifesto, that helps make software better is as it should be "a know brainer". Nikhil More. Ericson Rafael: (Private) I really agree with all of the proposals presented here and I’d like to say that all of my students will be called to read and adopt this manifesto. Thank you all. Harpreet Sidhu: Doing what's actually needed satisfies customers and developers. Emilio Gratton: I fully support the Agile approach and its ability to help developers to work beyond single tasks. My only doubt is about the word "individuals". I'd like to refer to the "users" instead. It's just because I'd like to tailor a development for a position instead for a specific person that, sooner or later, might change. Govind Davis: (MCF Technology Solutions) We were living Agile long before we even knew what it was .. . so exciting to find there are a world of others thinking about value over paperwork. Francesco Pezzino. Igor Gordiichuk. Zachary Crockett: (Hypergolic Motion, LLC) Viyom Jain. Marcus Winkler: (Heraeus Kulzer)