When our founding fathers completed the Constitution in 1787, they distributed it to each state for review and acceptance. Many states rejected it. Those that did were asked to provide proposed revisions, amendments etc. They got back over 150 proposed revisions. Through discussion, clarification and compromise, these were narrowed down to 10 and make up what we know today as the Bill of Rights which were amended to the Constitution in 1791.
In 2001, a small group of software luminaries set forth to radically change the face of software development. They encapsulated this new perspective in The Manifesto for Agile Software Development. 
Eight years later, after having applied the principles and values prescribed therein, these values have been tremendously successful at providing the software industry with similar benefits that Lean Manufacturing furnished for Toyota. Unfortunately, we’ve also learned that too many individuals and shops have given Agile Software Development a bad name by using it as a fig leaf to hide behind delivering crappy software and calling it agile, further setting back software engineering as a mature discipline.
As a result, our very own Bill of Rights has been born. The Manifesto for Software Craftsmanship is founded on the original Manifesto but raises the bar to eliminate any ambiguity around the expectations of professional software engineers to not only produce working software, but ensuring it is well designed. Not merely reactively responding to change, but strategically partnering with the business to proactively add value while building a community of professionals that can teach and learn from one another.
Do you believe in these values? Do you agree that as an industry we are still failing to add value and deliver high quality software? If so, I implore you to think about the values as a whole, and if you are so inclined, sign and commit to it: http://manifesto.softwarecraftsmanship.org/sign/new