{"id":366,"date":"2008-05-15T00:35:02","date_gmt":"2008-05-15T04:35:02","guid":{"rendered":"http:\/\/judykat.com\/ken\/?p=366"},"modified":"2012-03-31T20:48:31","modified_gmt":"2012-04-01T00:48:31","slug":"fail-fast","status":"publish","type":"post","link":"https:\/\/judykat.com\/ken-judy\/fail-fast\/","title":{"rendered":"Fail fast"},"content":{"rendered":"<p><a href='http:\/\/flickr.com\/photos\/aperte\/948080386\/'><img decoding=\"async\" data-attachment-id=\"186\" data-permalink=\"https:\/\/judykat.com\/ken-judy\/focus-and-variety\/blurcoaster-by-kjudy\/\" data-orig-file=\"https:\/\/judykat.com\/ken-judy\/wp-content\/uploads\/2007\/09\/blurcoaster.png\" data-orig-size=\"250,167\" data-comments-opened=\"1\" data-image-meta=\"[]\" data-image-title=\"BlurCoaster by Kjudy\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/judykat.com\/ken-judy\/wp-content\/uploads\/2007\/09\/blurcoaster.png\" src=\"http:\/\/farm2.static.flickr.com\/1332\/948080386_67d0d1c261_m.jpg\" alt=\"Panic Button by aperte on flickr\" title=\"Panic Button by aperte on flickr\" class=\"alignright size-full wp-image-186\" \/><\/a>Fail fast is a technique for improving the quality of software:<\/p>\n<blockquote><p>&#8220;failing immediately and visibly&#8221; sounds like it would make your software more fragile, but it actually makes it more robust. Bugs are easier to find and fix, so fewer go into production. &#8212;<a href=\"http:\/\/martinfowler.com\/ieeeSoftware\/failFast.pdf\"> Jim Shore<\/a><\/p><\/blockquote>\n<p>Scrum aspires to a fail fast approach to building software.<\/p>\n<p>It describes practices that surface problems:<\/p>\n<ul>\n<li>a backlog prioritized by the product owner and estimated by the team (accountability)<\/li>\n<li>short iterations<\/li>\n<li>frequent retrospection<\/li>\n<li>a role dedicated to removing impediments<\/li>\n<\/ul>\n<p>It champions values that motivate individuals to address problems:<\/p>\n<ul>\n<li>delivering business value<\/li>\n<li>collaborating with customers<\/li>\n<li>empowering teams<\/li>\n<li>building quality in<\/li>\n<li>continuous improvement<\/li>\n<li>courage and honesty (a refusal to hide risk)<\/li>\n<\/ul>\n<p>Possessing these values and practices, an organization is less likely to overlook or tolerate dysfunction when it materially affects the setting and achieving of project goals. <\/p>\n<ol>\n<li>risks are identified before they become problems<\/li>\n<li>simple problems are detected and resolved quickly<\/li>\n<li>thorny problems are mitigated<\/li>\n<li>catastrophic problems are aired to all concerned parties (informed consent)<\/li>\n<\/ol>\n<p>Cases #1-3 increase a project&#8217;s chance of creating value.<\/p>\n<p>Case #4 compels an organization to cancel a doomed project.<\/p>\n<p>All four cases represent a better outcome for the business. Assuming that business offers value to the world, that&#8217;s better for our end users, our reputation, and our society.<\/p>\n<p>Immediate and visible failure. Much preferable to hidden, prolonged and inevitable failure.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Fail fast is a technique for improving the quality of software: &#8220;failing immediately and visibly&#8221; sounds like it would make your software more fragile, but it actually makes it more robust. Bugs are easier to find and fix, so fewer &hellip; <a href=\"https:\/\/judykat.com\/ken-judy\/fail-fast\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":2459,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"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":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8],"tags":[19,45,133,43,44,878],"class_list":["post-366","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scrum","tag-agile-software-development","tag-failure","tag-product-owner","tag-quality","tag-risk","tag-scrum"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/judykat.com\/ken-judy\/wp-content\/uploads\/2011\/02\/948080386_67d0d1c261_m.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/posts\/366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/comments?post=366"}],"version-history":[{"count":0,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/posts\/366\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/media\/2459"}],"wp:attachment":[{"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/media?parent=366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/categories?post=366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/judykat.com\/ken-judy\/wp-json\/wp\/v2\/tags?post=366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}