While already published all over the web, I thought it worthwhile to repost it here.<\/p>\n
We have come to value: <\/p>\n
Individuals and interactions over processes and tools.
\nWorking software over comprehensive documentation.
\nCustomer collaboration over contract negotiation.
\nResponding to change over following a plan.<\/p>\n
That is, while there is value in the items on the right, we value the items on the left more. And we follow these principles: <\/p>\n
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. <\/p>\n
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. <\/p>\n
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. <\/p>\n
Business people and developers must work together daily throughout the project. <\/p>\n
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. <\/p>\n
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. <\/p>\n
Working software is the primary measure of progress. <\/p>\n
Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely. <\/p>\n
Continuous attention to technical excellence and good design enhances agility. <\/p>\n
Simplicity – the art of maximizing the amount of work not done – is essential. <\/p>\n
The best architectures, requirements, and designs emerge from self-organizing teams. <\/p>\n
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<\/p>\n","protected":false},"excerpt":{"rendered":"
While already published all over the web, I thought it worthwhile to repost it here. 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 […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-321","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/posts\/321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/comments?post=321"}],"version-history":[{"count":0,"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/posts\/321\/revisions"}],"wp:attachment":[{"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/media?parent=321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/categories?post=321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/Pallieter.org\/www8\/wp-json\/wp\/v2\/tags?post=321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}