Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
The Manifesto for Software Craftsmanship Turns 5
Transcript of The Manifesto for Software Craftsmanship Turns 5
Not only working software,
but also well-crafted software
Not only responding to change,
but also steadily adding value
Not only individuals and interactions,
but also a community of professionals
Not only customer collaboration,
but also productive partnerships
That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
Raising the Bar
We humbly demonstrate our expertise by delivering quality software.
We do not inflate our abilities or claim expertise where we have none.
We continually master a variety of technologies and techniques.
We do not let unfamiliarity dissuade us from using the best tools.
We take responsibility for the correctness of our code by testing it thoroughly.
We do not tolerate preventable defects.
We estimate with diligence.
We do not let fear or pressure make us promise what we can’t deliver.
We always apply our best efforts to complete our work.
We do not make excuses.
We work at a sustainable pace.
We do not burn out.
We show respect for our customers and fellow craftsmen. We do not act unprofessionally or unethically.
We communicate our progress honestly and openly with our customers.
We do not conceal or embellish.
We partner with our customers to understand their business.
We do not propose solutions until we are sure we have found the right problem.
We embrace differences of opinion and personality.
We do not allow our current practice to impede improvement.
We prefer open source tools that we can inspect, evaluate, and improve.
We avoid proprietary products that lack transparency.
We teach anyone with a willingness to learn.
We do not hoard our knowledge or practices.
Responding to change over following a plan
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
That is, while there is value in the items on
the right, we value the items on the left more.
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Manifesto for Agile Software Development
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
Dec 13, 2008
2/9/09 - 2/24/09
Aug 27, 2008
Aug 7 2008
Software Craftsmanship Summit
The new left/right Side
12,000 signatories and counting
"Craftsmanship over Crap"
Maturing the Manifesto
...we have found something we value more than “working software.”
Are there things that we value more than those things on the left hand side?