{"id":446,"date":"2017-08-05T12:30:41","date_gmt":"2017-08-05T07:00:41","guid":{"rendered":"http:\/\/innoroo.com\/blog\/?p=446"},"modified":"2017-11-30T17:39:19","modified_gmt":"2017-11-30T12:09:19","slug":"extreme-programming-glossary","status":"publish","type":"post","link":"https:\/\/innoroo.com\/blog\/2017\/08\/05\/extreme-programming-glossary\/","title":{"rendered":"Extreme Programming | Glossary"},"content":{"rendered":"<p><span style=\"color: #3366ff;\"><strong>Definition<\/strong><\/span><\/p>\n<p><b>Extreme programming<\/b> (<b>XP<\/b>) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. It is a type of Agile Software Development, which advocates frequent &#8220;releases&#8221; in short development cycles. It is intended to improve productivity, and introduce checkpoints at which new customer requirements can be adopted.<\/p>\n<p><span style=\"color: #3366ff;\"><strong>Origin<\/strong><\/span><\/p>\n<p>Extreme programming was created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project. Beck became the C3 project leader in March 1996, and began to refine its&#8217; development methodology, eventually writing a book about it. In October 1999, \u201cExtreme Programming Explained\u201d was published.<\/p>\n<p><span style=\"color: #3366ff;\"><strong>Pros<\/strong> <\/span><\/p>\n<ul>\n<li>Extreme Programming aims at bringing about efficiency in the coding process and providing customers with maximum value<\/li>\n<li>It stresses importance to individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan<\/li>\n<li>Extreme Programming trims unproductive activities to reduce costs and frustration of everyone involved<\/li>\n<\/ul>\n<p><strong><span style=\"color: #3366ff;\">Cons<\/span> <\/strong><\/p>\n<ul>\n<li>Extreme Programming is challenging to adopt completely and it becomes challenging to enforce culture change.<\/li>\n<\/ul>\n<p><span style=\"color: #3366ff;\"><strong>Further Reading<\/strong> <\/span><\/p>\n<div class=\"_Q1n\" role=\"heading\">\n<ul>\n<li class=\"kno-ecr-pt kno-fb-ctx _sdf\">&#8220;Extreme Programming Explained&#8221; by Kent Beck<\/li>\n<li class=\"kno-ecr-pt kno-fb-ctx _sdf\"><span id=\"productTitle\" class=\"a-size-large\">&#8220;eXtreme Programming in Action: Practical Experiences from Real World Projects&#8221; by Martin Lippert.<br \/>\n<\/span><\/li>\n<\/ul>\n<p>Know more about Extreme Programming by visiting our <a href=\"http:\/\/innoroo.com\">website.<\/a><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Definition Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. It is a type of Agile Software Development, which advocates frequent &#8220;releases&#8221; in short development cycles. It is intended to improve productivity, and introduce checkpoints at which new customer requirements can be adopted. [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":516,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[102],"tags":[17,103,111,106,113,70,71,65,66,107,67,119,109,105,18,19,112,3,72,108,75,59,58,110,69,30,68,64,120],"class_list":["post-446","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-glossary","tag-agile","tag-agile-team","tag-backlog","tag-blog","tag-bugs","tag-cd","tag-ci","tag-continuous-delivery","tag-continuous-integration","tag-definition","tag-devops","tag-extreme-programming","tag-further-reading","tag-glossary","tag-innoroo","tag-innovation-roots","tag-items","tag-kanban","tag-less","tag-origin","tag-pm","tag-safe","tag-scrum","tag-software-development","tag-suite","tag-team","tag-tools","tag-webinar","tag-xp"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2017\/08\/03.png?fit=750%2C410&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8Rui8-7c","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/comments?post=446"}],"version-history":[{"count":8,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/446\/revisions"}],"predecessor-version":[{"id":2209,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/446\/revisions\/2209"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media\/516"}],"wp:attachment":[{"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media?parent=446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/categories?post=446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/tags?post=446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}